14:59:04 #startmeeting Tor Browser Weekly Meeting 2022-10-31 14:59:05 Meeting started Mon Oct 31 14:59:04 2022 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:10 good morning all 14:59:20 and or good evening 14:59:26 the pad as usual: https://pad.riseup.net/p/tor-tbb-keep 15:00:27 hello 15:01:40 o/ 15:02:31 so 12.0a4 didn't get make it out last week for a few reasons 15:03:01 this is the first (to my knowledge) release where we don't have *any* locals in common with the prevoius release, so make incrementals failed 15:03:03 Good evening 15:03:25 and secondly the website changes aren't ready for us anyway so no big deal 15:03:26 richard: oh cool, that's a nice edge case 15:04:15 rather than complicate the build process with a one-off (well two-off if you count 11.5 -> 12.0) hack we'll instead just not have incrementals for the localization migration 15:04:41 which does mean bigger downloads but odds are they are going to be big for 11.5 to 12.0 anyway so seems like a reasonable trade-off to me (thanks boklm) 15:05:39 dan_b: I posted the mterials from hackerone to the ticket in the description 15:05:56 ooooh looking 15:06:14 aaah as an edit, that's why i didnt get an email 15:06:16 awesome thanks 15:06:21 removing from my needs help list 🙂 15:06:30 sorry should have @'d you 15:06:40 well that's top of my list this week 🙂 15:07:41 last week i did abit of ticket shuffling, so if you are short on tickets, ~Next and ~Sponsor 131 should be the query to use 15:08:21 ( https://gitlab.torproject.org/groups/tpo/applications/-/boards?label_name[]=Next&label_name[]=Sponsor%20131 ) 15:09:23 cool! 15:09:41 i don't think there's anything else on my end but looks like PieroV has some bolded items 15:10:09 richard: yeah, I've a few things actually 15:10:35 1. are we planning a 11.5.7? I had an idea to avoid losing user's setting for the locale 15:10:55 At the moment, our builds set the locale as a preference in 000-tor-browser.js. 15:11:16 We could write a patch for the 11.5 series that sets it as a user preference 15:11:44 In this way 12.0 will set the lang pref to empty in 000-tor-browser.js, but the previous pref will remain in user's pref.js 15:12:04 But we'll need to write a small patch and release a 11.5.7 15:12:32 I def think it's worth the effort it to avoid confusing users 15:12:53 we can hash out scheduling/details in the release meeting later 15:13:13 I'll create a ticket for it, then. If we hack it also in 12.0a3 and let it update to 12.0a4 we can preview if it works 15:13:21 But works for me to discuss outside the meeting 15:13:42 (today possibly, or after I come back from the reproducible builds event) 15:13:52 that'll prolly help and catch a lot but dont forget infrequent users who might not hit every point release. not saying we need even more effort for them, just remember some might not be in the flow. that said, this sounds like a great idea for our more active users 15:14:08 👍 15:14:26 +1 15:14:43 slight tangent, but I think that another benefit we haven't said is that with no massiv elist of locales 15:14:52 we can build incrementals from more previous releases 15:15:06 richard: yes, that was my original plan 15:15:09 Hmm, yes, that is a good point 15:15:28 and probably work w/ metrics to figure out what that rolling window should be 15:15:29 It should work, but we'll need to modify projects/browser/build to create an ad-hoc preference for that 15:15:29 I know quite a lot of users who don't hit every release 15:16:11 So, we'll need to build all the locales, even though then they will be moved to the multi-lingual channel 15:16:48 i'm not sure i'm following 15:16:55 Doable, but less easy than the previous idea and needs more work (but not mutually exclusive) 15:17:01 richard: np, I think we can discuss later 15:17:07 kk 15:17:19 2. I've gone through a series of Moz help pages for tor-browser#40899 15:17:34 And I think that there are some issues that we could disable already for 12.0/hide them from the preferences page 15:18:01 Another thing we don't need to go through now, but possibly worth to create a few tickets for 12.0a5 15:18:20 ooh ok 15:18:32 (I'm still finishing to update the list though) 15:19:47 excellent 15:20:52 oh one more thing 15:20:57 3. I'll need help for the WASI sandbox, I think I could open a MR with the feature still disabled when we finish with 12.0a4 15:21:13 But definitely low priority/12.5 15:21:41 i'll be recording our the state of the onion this week, if you haven't already please add anything you think shoudld be covered to the pad: https://pad.riseup.net/p/applications-state-of-the-onion 15:21:47 (and that was my last item from the pad, but I'll have another question later) 15:23:05 ok y'all, i don't have anything else 15:23:41 it should be a quiet week with holidays and boklm+pierov at the reproducibility build conference 15:23:42 richard: what's the schedule for the next alpha? 15:24:01 to be figured out between now and the release meeting 15:24:13 PieroV^ 15:24:44 Okay. According to the calendar it's in 2.5 hours, right? 15:24:56 yeah 1800 UTC 15:25:29 (Europe is out of daylight saving time now, so some confusion with regards to UTC is to be expected from me ^^;) 15:25:45 BTW, are we keeping this time also next week when USA/CA) changes DST? 15:25:57 ma1: yes, that's TPO policy 15:25:57 oh geez. I think in canada we change next week. not bad enough we all change times, it's so much better when we do it out of sync? 15:26:08 yeah this time of year is always a shit show 15:26:13 ma1: my understanding is that Tor Project policy uses UTC, without regard to DST 15:26:21 Jeremy_Rand_36C3[m]: correct 15:26:22 ^that 15:27:06 * Jeremy_Rand_36C3[m] likes that policy, wishes everyone did it that way 15:27:11 obviously his doesn't necessarily work if you have irl obligations that don't care about UTC 15:27:18 yes, I understand it. I was wondering wether shifting one time earlier worked for everyone (it surely does for me) 15:27:26 so if anyone's inconvenienced we can move it 15:27:29 s/one time/one hour/ 15:27:33 Jeremy_Rand_36C3[m]: I'd wish dst wasn't a thing :( 15:27:51 PieroV: Agreed, DST needs to be nuked from orbit 15:27:55 otherwise assume meetings are stlil the same tie (UTC) :) 15:27:57 Indeed. The problem is not DST or not, it is the change. 15:28:21 huh, nextcloud has shifted all my meetings so they are an hour wrong 15:28:36 but i suspect that means this meeting will be 7am for me next week instead of 8am 15:28:39 -_-; 15:29:04 moving it to later isn't very feasible, unless we go to #tor-meeting2 15:29:12 no worries 15:29:18 Because there's network health meeting here after us 15:29:36 especially first week i ll just pretend times havent changed 😄 15:29:59 but yeah, 7 is manageable, i'm more of a morning person 🙂 15:30:08 ok 15:30:20 then we'll keep this meeting when it is :p 15:30:47 anything else? 15:31:30 going once 15:31:35 Nothing here 15:31:38 twice 15:31:44 and thrice 15:31:48 bang 15:31:54 alright have a good week y'all 15:32:04 Thanks! You too 15:32:04 pierov, boklm: enjoy your confernece :) 15:32:05 thanks, you too 15:32:10 thanks :) 15:32:11 #endmeeting