10:59:59 <richard> #startmeeting Tor Browser Weekly Meeting 2022-08-01
10:59:59 <MeetBot> Meeting started Mon Aug  1 10:59:59 2022 UTC.  The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot.
10:59:59 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
11:00:21 <richard> meeting pad per usual: https://pad.riseup.net/p/tor-tbb-keep
11:00:23 <Jeremy_Rand_36C3[m]> Hi!
11:00:29 <richard> o/
11:00:40 <PieroV> hello Jeremy!
11:00:49 <Jeremy_Rand_36C3[m]> Hey PieroV !
11:02:00 * Jeremy_Rand_36C3[m] had a 2nd consecutive negative COVID test, and will thus be cleared to exit isolation in a few hours
11:02:08 <PieroV> \o/
11:02:10 <Jeremy_Rand_36C3[m]> So for the next meeting I'll be back at my usual OFTC account
11:02:27 <Jeremy_Rand_36C3[m]> (Thanks to everyone who sent well-wishes :) )
11:07:17 <richard> ok then
11:08:31 <richard> it's a bit of the calm before the storm this morning
11:11:04 <richard> so the only bit of 'news' from me is that we're going to move the Tor Browser meeting later in the day (to be decided/negotiated) so our west of the atlantic people will be less sad
11:11:48 <PieroV> At the previous time?
11:11:52 * Jeremy_Rand_36C3[m] hopes this wasn't solely due to me complaining a little, but is appreciative anyway
11:12:18 <richard> PieroV: most likely but we'll see what works with the rest of the team
11:12:41 <PieroV> and also availability, unless we move to tor-meeting2
11:12:51 <PieroV> But I don't know if the bot is active there
11:12:57 <richard> I think it is
11:13:01 <PieroV> (channel availability, I meant)
11:13:14 <richard> yes yes
11:13:56 <richard> are there any other discussion topics that need to be addressed?
11:14:11 <PieroV> I'm rebasing to 102
11:14:24 <PieroV> So, do anyone has anything to say about this on this meeting?
11:14:47 <richard> had any major issues so far?
11:15:07 <PieroV> Yes, an annoying one
11:15:23 <PieroV> The tor-launcher stuff aren't being loaded
11:15:33 <Jeremy_Rand_36C3[m]> PieroV: curious how different the toolchain / build system / mozconfigs are between ESR91 and ESR102
11:15:50 <Jeremy_Rand_36C3[m]> (Mainly because that'll affect the ARM/POWER ports)
11:15:57 <PieroV> Jeremy_Rand_36C3[m]: we're updating to Clang 14.0.4, and cbindgen to 0.23.4 iirc
11:16:09 <PieroV> Oh, and nasm to the most recent version
11:16:16 <PieroV> But that's for Android, which is based on 102 as well
11:16:29 <PieroV> I haven't checked on desktop, yet
11:16:30 <Jeremy_Rand_36C3[m]> PieroV: do any of those things require mozconfig changes?  They sound relatively innocuous.
11:17:17 <PieroV> Jeremy_Rand_36C3[m]: nope. I think that usually we don't add versions to directories
11:18:04 <Jeremy_Rand_36C3[m]> PieroV: OK cool.  Hopefully everything will "just work" or almost so when boklm and/or I rebase it.
11:18:27 <PieroV> Jeremy_Rand_36C3[m]: hopefully yes, but boklm is afk these two weeks
11:19:02 <Jeremy_Rand_36C3[m]> PieroV: given that boklm is AFK, will someone else be handling the tor-browser-build changes for ESR102, or are those waiting for him to return?
11:19:23 <PieroV> Jeremy_Rand_36C3[m]: richard is best suited to answer you :)
11:19:53 <PieroV> I think I can handle them, if needed, as I have been working on Android
11:20:07 <PieroV> Of course, I'd be eager to get also boklm's review :)
11:21:02 <richard> hmm i wonder if any legacy systems tor-launcher depends on have been removed
11:21:12 <Jeremy_Rand_36C3[m]> Alright.  Either is probably fine for me; I'm going to be busy catching up from my COVID absence, and the next thing I do with ARM/POWER will probably be trying to fix the NSS linker errors in ppc64 BE.
11:21:47 <PieroV> richard: the thing is that that part is still based on function then customization of prototype
11:21:47 <Jeremy_Rand_36C3[m]> But I will ask on IRC if I need assistance from whoever ends up being assigned those tor-browser-build tasks the next 2 weeks.
11:22:42 <PieroV> So, it's a lot of legacy code. I wonder if I should just go back to the transition of tor-launcher
11:22:57 <richard> yeah my thoughts exactly
11:23:06 <richard> have you not had similar issue w/ torbutton?
11:23:32 <PieroV> No, only with tor-launcher things exposed through the Cc["..."] things
11:24:21 <PieroV> but it's failing on Cc["@torproject.org/torlauncher-protocol-service;1"].getService(Ci.nsISupports), which isn't a good sign
11:24:37 <PieroV> Cc succeeds, getService fails
11:24:56 <richard> *neat*
11:25:12 <richard> hmm
11:26:18 <richard> well
11:27:29 <richard> at this point i'd say try getting it working for some reasonable amount of time, and if that initially fails can you do some estimations for the effort required to just port/re-implement the required functionality
11:27:47 <PieroV> okay
11:28:04 <richard> i can't imagine there's *that* much funtionality left down there
11:28:12 <richard> i mean the tor daemon launch/management isn't exactly trivial
11:28:39 <richard> but it is probably more complicated than it needs to be
11:29:07 <richard> anyway, should we also have a little chat about android?
11:29:29 <richard> iirc there's a MR waiting for review that rebases alpha to 102 right?
11:30:02 <PieroV> Yes, there are 4
11:30:23 <PieroV> GeckoView (tor-browser.git), Android Components, Fenix and tor-browser-build
11:30:24 <richard> assuming that all works and we push out a 102 alpha, is there anything immediately pressing there?
11:30:49 <richard> we need to go back and do all the various audits back to firefox 90-something
11:31:00 <richard> and fix any issues that come up
11:31:13 <PieroV> richard: what if we did it with the desktop reviews?
11:31:38 <PieroV> So, use the 91 -> 102 both for desktop and Android
11:32:00 <richard> yeah i don't see why not
11:32:10 <richard> would also need to do the android specific components too which should be fine
11:32:34 <PieroV> Yes, there are many issues about that in the respective repositories
11:32:40 <PieroV> GitLab projects
11:32:43 <richard> mmhm
11:33:24 <PieroV> Once we get a 102 out, I think that we could start fixing issue and adding new features
11:34:12 <PieroV> Moz is already on 103 (and developing 104), so we might quickly check what changed in Android-specific things on 102 -> 103
11:34:23 <richard> i may be being over cautious, but I don't expect we'll be adding any new features to Android through the 12.0 release, I'd be happy if we got it audited and to where it should have been months ago :p
11:34:56 <richard> at the v least check for anything android-specific that needs to be backported
11:34:57 <PieroV> Not even Onion location?
11:35:34 <richard> oooh ok i stand corrected
11:35:44 <richard> that plus https-only mode
11:35:52 <PieroV> there are another couple
11:35:55 <PieroV> Or even more
11:36:01 <PieroV> Like the padlock on onion services
11:36:37 <richard> well let's see how the rest of the must-haves go
11:36:49 <richard> we'll have a better idea in a few months how that is going :p
11:37:13 <PieroV> The bootstrap issues (auto bootstrap to have TBA as a default browser on Android, at that point also quick connect, and see if we can fix the race that makes TBA appear like stuck in bootstrap)
11:38:32 <richard> yeah
11:39:22 <richard> ok if tehre's not anything else then I will call it
11:40:03 <richard> have a good week everyone!
11:40:10 <PieroV> Thanks! Same to everyone
11:40:28 <richard> #endmeeting