14:58:39 #startmeeting Tor Browser Weekly Meeting 2023-10-10 14:58:39 Meeting started Tue Oct 10 14:58:39 2023 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:58:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:58:44 blessed date 14:58:54 https://pad.riseup.net/p/tor-tbb-keep 14:59:19 /o 15:03:27 !ping 15:03:40 hi 15:03:51 ok so I've been out for a week 15:04:17 where are we with 13.0? 15:04:30 The rel prep MRs are ready for review, changelogs included 15:04:33 just adding some asked for line height and android yec is ready for MR 15:04:49 We made the call not to release at the end of the week, and postpone to the beginning of this one 15:05:01 But then we also decided to have Android YEC in 13.0, to avoid doing a release every week 15:05:26 (13.0 this week, 13.0.1 next week to include YEC, 13.0.2 the week of 23 to update on 115.4.0esr) 15:06:22 Apart from YEC, I have an ongoing patch with Moz, but not a blocker, just a nice addition, but I can wait for later, since users might not like it that much 15:06:29 (we'll need to explain it) 15:06:37 And then a changelog review would be great :) 15:06:55 ok that all sounds encouraging 15:07:00 what is the Mozilla patch? 15:07:15 PieroV: last I looked at the changelog it had a bunch of duplicates 15:07:37 For the blog posts, I told donuts that I didn't expect it to be needed for today, but Wed or Thu (not great if it's Thu, but that's okay, we hope not to have fires over the weekend) 15:07:42 richard: can't tell 15:08:15 https://bugzilla.mozilla.org/show_bug.cgi?id=1849186 15:08:27 (probably they'll lift the confidentiality though) 15:08:59 * richard reading 15:09:29 ooh cool 15:09:37 ok good to see that fixed :) 15:09:43 I think we should add a UI element to turn it off though 15:10:02 hmm 15:10:05 But on by default 15:10:09 yeah fair 15:10:13 Anyway, not a blocker for 13.0 in my opinion 15:10:23 somewhere under privacy & security 15:10:41 well anyway 15:11:14 The MR for rel preparation is tor-browser-build!829 15:12:08 ok I'll prioritize reviewing that after this meeting 15:12:45 beyond that, my other major(?) task for this week is to build a schedule for goteburg meeting 15:13:35 if you haven't already, please have a look at the pad from the mail thread (or ping me for the link) if there are any sessions or discussion points that need to happen; 15:14:21 i'll do my best to build out a schedule and hopefully folks won't need to be in two places at once 15:14:31 apart from that ,i have nothing else for this meeting 15:14:47 so if anyone else has discussion points speak now! 15:15:23 I had a small one for last week 15:15:37 richard: i have issues ... i always have issues, but I meant goteburg ones - can we talk before I sleep 15:15:53 o/ 15:16:07 We have a MR that is good because it's a Moz backport, but doesn't apply to us because of our profile 15:16:12 I've got a first draft of the blog post and assets nearly ready, will begin pulling together the MR today 15:16:17 (sorry, just saw the ping now) 15:17:13 So, I'd close that MR (tor-browser!811), unless anyone thinks it's a good idea to keep it 15:17:23 But def low priority 15:18:06 thorin: yeah ping me after the meeting and we can chat :) 15:18:11 +1 for closing since it's not a PBM issue 15:18:50 lol speaking of unimportant mozilla backports, we should maybe backport the fix to tooltips not going away when firefox loses focus 15:18:56 eek, not PBM, but because we set that other pref 15:19:14 :3 15:19:16 22 YEARS!!! beats my FIVE YEARS 15:19:40 yeah i saw that in the news too 15:19:46 +1 for back porting that lol 15:20:06 What is PBM? 15:20:14 private browsing mode 15:20:19 Ah thanks 15:21:19 donuts: ack i'll review once it's up :) 15:21:34 ty richard 15:23:28 richard: actually there's also another MR that should go in 13.0 15:24:13 I created the TOR_PROVIDER env variable :) It can be tor or none. When it's none, the browser only configures the SOCKS port 15:24:46 It should be useful for system tor but also for Arti. It fixes a regression of my refactors 15:25:05 So, 13.0 would be great 15:25:33 (having it already in 13.0, I mean) 15:26:28 sounds good to me! 15:27:09 ok so obviously in terms of priorities any remaining/undiscovered 13.0 release blockers take priority 15:28:07 beyond that s96 (torconnect on Android, Arti in torbrowser, etc) should be our next priority 15:29:33 granted not *everyone's* working on s96 immediately, in which case ~13.0 Stable && ~Backlog issues are for you 15:29:53 as always ping me if that makes no sense 15:29:56 We currently have less than 40 open issues in ~13.0 stable \o/ 15:30:00 I had a couple MR's pushed to be ready for review late Thursday that I told dan_b about. I think they're pretty simple changes but dan_b what do you think about getting them into 13.0? 15:30:20 yeah planning on reviewing htem this morning once gitlab is rebooted 🙂 15:30:35 Cool! 15:30:35 should be no problem. And likewise you'll have a hot yec review coming your way shortly! 15:30:54 dan_b, clairehurst: unless they are trivial changes I'd rather not have *too* much more stuff in Android 15:31:25 one is a screenshot setting fix (missing listener or something i think) 15:31:27 we already have a number of UX tweaks and fixes i'm sure users and donuts are happy about but i don't want to press our luck there :) 15:31:39 ones a oneline help button fix 15:31:44 Should we rebase to have a clean Android branch too? Or too time consuming/risky? 15:31:57 awesome so no re-architecting the about:addons page :D 15:32:05 and the last is just remove customize home button? which i think doesnt work on android 15:32:14 PieroV: I think we can do that for the first 13.5 alpha 15:32:19 hahaha no 15:32:23 wfm 15:32:31 assuming you mean patch reordering etc 15:32:45 Apply the fixups/squashes 15:32:49 happy for you to continue removing things that don't work in TBA :) 15:32:49 ^ dan_b 15:33:01 ah it's all clairehurst! 15:33:09 i'm just reviewing 🙂 15:33:15 PieroV: ah yeah fixup+squsahing gets a greenlight from me 15:33:30 * happy for clairehurst to continue removing things that don't work in TBA 🙏 15:33:44 clairehurst: yeah i've got to say it's SO nice to have someone fixing/rounding off all the jagged edges 15:33:56 keep it up :) 15:34:05 oh actually that does remind me 15:34:26 we should just remove the entire settings UI :~p 15:34:41 * ma1 is triggered by the "rounding" word :) 15:34:57 * thorin has rounding bugs for ma1 15:35:10 dan_b: updating the API level for Android should be the next major Android priority so we don't fall over come Novemeber 15:35:11 thorin: if you remove ALL the UI you'll do us out of a job though :P 15:35:21 ma1: buffing out the jagged edges then :) 15:35:29 lol 15:35:38 richard: it was already done with the 115 update from moz 15:35:49 ma1: seriously, I do have newwin rounding bugs 15:35:50 dan_b: wasn't there an issue with one of the PTs? 15:35:59 the alert was generated on aug 11? a day before we uploaded the first 115 based 13.0 15:36:12 Yeah the 3 are #42156 #42157 #42158 dan_b richard 15:36:13 it just surfaced on the 18th of aug, cus google play console is cool like that 15:36:24 oh fun 15:36:26 richard: there's no more alert about it in play console on alpha 15:36:27 thorin, did I miss any gitlab mail or are they yet to be opened / CCed? 15:36:41 tor-browser#42156 tor-browser#42157 tor-browser#42158 15:36:48 beautiful 15:37:06 ma1: I am waiting for 13 release to confirm 15:38:13 ma1: not critical, LBing saves us 15:38:26 ack 15:39:04 ok then 15:39:26 if there are no further discussion points 15:39:31 have a good week everyone o/ 15:39:42 #endmeeting