14:59:17 #startmeeting Tor Brwoser Weekly Meeting 2024-02-26 14:59:17 Meeting started Mon Feb 26 14:59:17 2024 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:17 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:01:51 pad per usual -> https://pad.riseup.net/p/tor-tbb-keep 15:02:13 we've a pending rebuild of Tor Browser 13.5a5 due to a crash-on-launch on Android 15:02:43 we've already identified the cause (js minification gone wild) and we'll build a new build tag this afternoon/tongiht and plan to publish tomorrow 15:03:17 13.5a5 MB is being signed and should be available this afternoon/evening for testing tomorrow 15:03:25 ruihildt[m]^ 15:03:49 i appreciate your emojii whomever jsut put that in the pad 15:03:56 ^^; 15:05:02 people on the hiring comittee, we should have a quick sync later re stuff we need to get done this week 15:05:18 I'll probably be already afk 15:05:42 ack in that case i'll just send out an email :) 15:06:09 o/ 15:06:17 late but here 15:06:43 and finally from me, a gentle reminder to please provide estimates for your work allocations each week 15:06:45 (I'll be waiting on the email, as ever) 15:06:57 hi bellatchau o/ 15:08:13 and finally in tor-browser-build news, it seems we've had an enterprising volunteer (noisycoil) working on aarch64 linux cross-compilation and even has working cross-compiled aarch64 linux builds 15:08:36 \o/ 15:08:40 still early stages obviously but i thought folks might like to be aware :) 15:08:47 We also have other tor-browser-build news 15:08:56 The F-droid APKs are almost reproducible! 15:09:02 \o/ 15:09:05 (with our APKs I mean) 15:09:17 oh wow cool 15:09:25 However, we might want to modify a little bit our signing scripts 15:09:41 so as always if continue to be nice and welcoming to the volunteers :) 15:09:41 richard: yeah I saw there was a bunch of activity in GitLab about the arm64 work, super cool, though I haven't any time to look at it yet 15:09:54 richard: do you want me to assist in reviewing that work? 15:10:13 Because we sign an already signed build. It'd helped if we signed an unsigned build instead 15:10:27 tor-browser-build!920 for those following along at home 15:10:49 jeremy: if you have time and interest your review would be welcome I'ms ure :) 15:11:04 richard: interest definitely yes, time maybe :) 15:11:17 PieroV: that seems like it should be a relatively easy change 15:11:26 devils in the details i'm sure though 15:11:29 richard: I'm curious how much overlap there is between their approach and mine 15:11:56 iirc they are using a cross compiling gcc toolchain 15:12:07 so take from that what you will :) 15:12:16 It's always fun to talk to people who did something similar to what I did, it's a good way to cross-pollinate skill sets, so I will try very hard to make the time 15:12:18 ok 15:12:28 that is all from me this wek 15:12:41 does anyone else have any other topics to discuss? 15:13:03 That said, Namecoin has a new developer starting in the next day or two, and I'm in charge of reviewing her code, so not 100% sure how my time looks like 15:13:58 speaking to the hiring committee, are you planning for some UDP/SOCKS5 questions? re: https://bugzilla.mozilla.org/show_bug.cgi?id=1808692#c12 :) 15:15:20 ma1: the current strat is to tailor qs to the candidate, since we've a large breadth of potential areas of expertise we'd be happy with 15:15:48 and a large breadth of candidates atm 15:16:15 ack, wise. 15:17:34 Yeah agreed that that's a good strategy 15:20:26 alright, if there's nothing else 15:20:29 have a good week everyone o/ 15:20:32 #endmeeting