15:02:30 #startmeeting Tor Browser Weekly Meeting 2023-07-17 15:02:30 Meeting started Mon Jul 17 15:02:30 2023 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:30 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:02:42 sorry starting a bit late this morning, lost track of time! 15:02:46 the pad: https://pad.riseup.net/p/tor-tbb-keep 15:03:06 please take this time to update/cleanup your gitlab boards, update the afk calendar, and pet your cats and or dogs 15:04:52 should i create a issue for myself for hte firefox-android 115.2.0 rebase? 15:05:37 I didn't consider a new one, since it's basically still part of the initial rebase 15:05:50 i don't think it's necessary 15:06:26 last week i've created and even assigned some s131 issues for the 13.0 release cycle 15:07:00 fortunately henry-x is afk this week so that gives me time to hunt down UX re the about:tor refresh we have planned in the tor-browser 13.0 release cycle 15:07:44 i've also created our 13 issue audit tickets for the all the rapid-releases since 102 15:08:09 so you can also start expecting periodic audit issues being assigned to you from now until 13.0 stabilizes 15:09:21 PieroV: can we get an update from you re: the status of 115-based deskop 15:09:29 and then dan_b the same re Android? 15:09:56 I think we should start doing nightly builds of 115 desktop asap 15:10:16 what is it you need? 15:10:19 The tor-browser.git repository has been ready for a while now, and we started adding new patches 15:10:34 I think tor-browser-build.git is also ready, for the desktop part 15:11:21 As I wrote last week, I think it'd be more useful to have updated desktop-only builds than keep doing stale builds for both desktop and Android 15:11:53 The build part for Android should arrive soon, too. At that point we could build it even though we have bootstrap problems 15:12:00 richard: what was it you want me to do for android? review logs of 102->115 and look for things to flag for more inbestigation? 15:12:17 I think bootstrap has absolute priority 15:12:29 dan_b: oh no no, just a status update for now for the meeting 15:12:29 We're half-way between 115.0 and 115.1 15:12:51 I'm doing the first pass of issue audits and then farming out deeper investigation as appropriate over the coming weeks 15:13:21 ah ok: I think I have a 115.2 rebase ready but am redoing the build steps and updating hte wiki so anyone else can, once complete and builds I'll push (the build dates changed so maven failed to 'find' GV) 15:13:28 This week I'll be looking at onboarding 15:14:03 I realized I'm less sure about using the TB html version, since that I assume is hooked into the executable launcher, but we need to trigger the android-tor-service or what ever it's called 15:14:17 cus android process management 15:14:29 so i Might be looking into just figuring out how to resurface that ASAP 15:15:05 unless Pierov you have any ideas how to make the desktop html/js flow then control that 15:15:19 dan_b: I think we'll have to hijack the flow in any case 15:15:35 also yes 15:15:40 the onboarding flow you mean? 15:15:52 yep 15:15:55 Yes 15:16:03 so that's what I'm up to 🙂 15:16:25 my intuition is that to hook up the tor-android-service to the existing desktop/html flow will be a pita and require a lot of plumbing 15:16:36 me too 15:16:47 but on the other hand i have no idea what hooking into the new onborading flow is so 15:17:03 well we'll kinda need to either way to trigger either I think 15:17:10 yolo go with whichever seems easiest and we can re-asses later 15:18:14 i think I'd be happy with a not-quite fully-functional initial alpha release so long as bootstrapping works at a minimum 15:18:26 will aim for that 15:18:40 richard: what's your idea re 13.0a1? 15:18:48 We discussed a little bit last week 15:19:31 let's plan on a desktop-only 13.0a1 release 15:19:46 We'll need to rebase again 15:19:46 and then plan on pinning up a 13.0a2 for both once android is ready 15:19:58 spinning up* 15:20:15 Outside Moz's cycle, if we manage to do it before August 1? 15:20:19 assuming we get bootstrapping working before 115.1-esr at the end of the monh 15:22:49 so yes outside of Moz's cycle if it makes sense 15:23:01 like if we get boostrapping working this week after 13.0a1 we should spin up a 13.0a2 15:23:17 If outside Moz cycle, maybe Android-only? 15:23:22 but if it's like a day or two ahead of a esr update then we wait and stay on the regularly scheduled train 15:23:46 ma1: I'd like to get my torbutton changes shipped asap 15:23:57 So having an additional build for desktop would be good 15:23:59 good idea 15:24:14 yeah i'm inclined ot think more desktop alphas is more good given all of the refactoring happening :D 15:24:31 Keep in mind we don't have many alphas at all 15:24:39 also I suspect we will get lots of bug reports about dark regression corners from a1 15:24:46 ^we're quickly creeping up on september somehow 15:25:06 regarding few alphas 15:29:09 ok, does anyone else have discussion topics for today? 15:29:35 if so let's try to be brief and end early so we can prep ourselves for the next android interview 15:29:44 smart 15:29:45 nothing from me; AFK things have kept me pretty busy the past week (and probably will continue to do so for the remainder of this week) 15:30:05 I'm good too 15:30:26 im good 15:30:33 I'm good too 15:30:34 Also good 15:31:11 ok then 15:31:15 have a goo week everyone o/ 15:31:23 good week >:[ i need a new keyboard 15:31:24 thanks! 15:31:25 Thanks! o/ 15:31:27 #endmeeting