15:00:26 #startmeeting Tor Browser weekly meeting 26 April 2021 15:00:26 Meeting started Mon Apr 26 15:00:26 2021 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:34 welcome, welcome 15:01:00 o/ 15:01:02 o/ 15:01:09 Pad: https://pad.riseup.net/p/tor-tbb-keep 15:01:12 Hello! 15:01:17 hi 15:01:55 * Jeremy_Rand_Talos apologizes profusely for missing last week's meeting 15:02:04 hello! 15:02:06 o/ 15:02:42 hi! 15:06:09 okay, let's get started 15:06:10 boklm: did you see my ping in #tor-dev? 15:06:36 yes, I'm currently uploading my android build 15:06:38 o/ 15:06:43 great, thanks boklm 15:06:46 hi emmapeel ! 15:06:59 alo alo 15:07:27 i opened tor-browser#40420 for tracking that 15:08:06 hello matrix people 15:08:27 lol 15:09:02 _oftc-irc:matrix.org has joined the chat_ 15:09:31 heh 15:10:13 okay, we have three significant objectives over the next month 15:10:25 and i want to make sure everyone is aware of them 15:10:42 the final piece is the discussion topic, as well 15:11:00 (or, the first discussion topic) 15:11:29 1) Stablizing S30 quick-start in nightly/alpha 15:11:51 (not landed in nightly yet, but hopefully it will be next week) 15:12:04 2) Moz89 preparations 15:12:20 3) version 2 onion services deprecation 15:13:16 4) snowflake lands in stable? 15:13:16 1. is still in pospeselr / antonela / dunqan's hands 15:13:31 antonela: yes, but i'm less concerned about that 15:13:39 oki 15:13:45 but, yes, 4. snowflake in 10.5 stable :) 15:14:02 re 1. yes, can we upstream s30 patches to make it the next alpha? 15:14:20 * antonela which is on may the 4th if im not wrong 15:14:30 i wanted to talk about QA when adding new langs but maybe is just a ticket, not a point on the meeting 15:15:14 emmapeel: okay, i added an item on the meeting pad :) 15:15:28 i can ping you when we reach it 15:15:39 great, thanks! 15:16:08 antonela: i suspect may 4th is optimistic now 15:16:14 let's say may 7th 15:16:24 and that is probably too aggressive, too 15:16:27 but let's try 15:17:01 okey, we are planning an small round of feedback collection with that alpha 15:17:13 so we will plan with may 7th in mind 15:17:41 pospeselr: how do you feel for that date for wrapping the url stuff? 15:17:46 urlbar i mean 15:17:46 i'd like at least one nightly 15:18:05 so the patches should land before 4 May 15:18:23 well, exclusive folks already have the nightly :) 15:18:38 sounds good matt, i want to make sure pospeselr is fine with it 15:18:40 which urlbar fixes? moving the bootstrap status to separate thing in the urlbar? 15:18:53 or pruning out search suggestions, etc when offline? 15:18:58 the former 15:19:22 ok the former should be done this week 15:19:38 if we're lucky it may get done today 15:20:00 amazing like always pospeselr 15:20:17 great 15:20:31 sysrqb: fwiw the about:torconnect feature is fully functional, we're just tweaking the UX at this point 15:20:52 very exciting 15:21:14 indeed 15:21:18 should we start thinking about code review? 15:22:22 pospeselr: ^ that was for you :) 15:22:40 yeah, i think so after the urlbar fixes mentioned above 15:23:01 okay 15:23:17 i guess ping me when that's ready 15:23:24 the biggest concerning piece is over the changes needed to enable dark-mode, but we've had a round of informal review from tjr and sanketh so I'm feeling less paranoid over it now 15:23:53 yeah, i looked at the patch, too 15:24:04 i only sarcastically commented abut your commit message 15:24:12 aah right 15:24:25 okay, sounds good 15:25:06 alright, let's move on to: 2. Moz89 15:25:25 we haven't finished Moz88 yet, but mozilla isn't waiting for us 15:26:57 the next alpha release will depend on this Moz89 transition 15:27:22 hopefully now we have mre tooling in place, and this process should be faster 15:27:26 *more 15:28:16 aw, so we need to look through the 89 patches as well? 15:28:20 i'll be looking at the remaining Moz88 tickets this week, with pospeselr 15:28:39 pospeselr: they don't stop :) :( 15:29:09 unbelievable 15:29:57 i believe i've posted the short list of tickets we need to look at for moz88 15:30:03 thanks 15:30:32 if we're splitting this up i can go through and do the same for 89 while you dive into those, or i can dive and you can make the 89 short list 15:30:35 regarding 10.5a15, we may publish it despite non-matching builds - depending on the cause 15:30:44 but we'll know after this meeting 15:31:07 pospeselr: okay. we can talk about that 15:31:21 looking at the Moz89 tickets in't very high priority right now 15:31:28 we have 2-3 weeks for those now 15:31:42 ah ok, then i'll focus on the 88s 15:31:47 *isn't 15:31:49 thanks 15:32:20 okay. item #3, v2 onion service deprecation 15:32:47 we have two tickets: tor-browser#40415 tor-browser#40416 15:32:53 (thanks antonela ) 15:32:57 :) 15:33:02 feel free to go over them after the meeting 15:33:16 they dont have a final version, is an opening to see what we can do with the time we have 15:33:56 we have a very short timeline for these issues 15:34:09 so they are somehow getting completed in May, too 15:34:17 (thanks dunqan for your review there!) 15:34:24 no prob! 15:35:47 okay, #4. snowflake in 10.5 stable. 15:36:21 i discussed this with cohosh, and we are planning on leetting snowflake continue into 10.5 stable 15:36:31 we may get some last-minute patches in May 15:36:51 but, overall, we'll see what happens when it's available to move people 15:36:57 *more 15:38:18 okay, next item. 15:38:30 antonela: we can re-start the release meetings 15:38:40 maybe that is helpful as we get closer to 10.5 stable release 15:38:56 right 15:38:57 and we have a lot of activity in May 15:39:51 4 May at 1900 UTC? 15:40:04 gaba: ^ 15:40:30 hey 15:40:52 restarting the release meeting 15:41:16 ok, adding it to the calendar. should we send a mail to tor-projecT@ about it? 15:41:55 sure. i think it is more for internal coordination 15:42:03 but we can announce it on the mailing list 15:42:12 ok 15:42:36 should i send that or should you? 15:43:23 https://pad.riseup.net/p/tor-browser-release-meeting-keep <-- i will recover it 15:43:27 I can send a mail 15:43:28 thanks gaba 15:43:29 about it 15:43:33 thanks! 15:43:57 grat. 15:44:04 great 15:44:10 okay, emmapeel o/ 15:44:58 ey there! ok, first of all, thanks so much for getting on board with releasing tor browser in burmese. the alpha was very timely and worked very well, made translators feel support ed and made them work harder 15:45:25 now, the bad part was that the stable was just too quick for the feedback to make it to us in time 15:46:15 the whole process of review took longer than the week we had, i am not sure if it was really because of the situation in Myanmar, like, they are shooting people and there is no electricity, let alone internet, or it is just hard to get the input back 15:46:39 so, there were some changes that should have made it to the stable and didnt 15:46:56 (i know, they should open tickets but they just mail erinm and then she tell me etc) 15:47:42 then there was the windows installer thing. the translator was trying to report the problem for days and we didnt understood him. we (erinm and me) also didnt have a windows box to test the issue 15:48:35 so, i wonder, apart of giving more time for the input, if we could have a manual test suite when a new language is added, to make sure we dont run on this problems 15:49:05 yes, we should create a check-list (or similar) 15:49:16 for example, the lack of Burmese option on the windows installer could have been found out by us instead of a translator that has little internet an does not know how to report tickets 15:49:44 and when i say us i dont say me :D:D i mean, i do not know enough about windows 15:50:02 but then if somebody asks me, i can say 'it has been tested!' 15:50:30 i was more concerned with the localization in the browser, so i didn't test it on windows 15:50:45 but yes, we should've seen this earlier 15:51:15 i also think we need to give more time for feedback to reach us after we publish the alpha 15:51:24 there are not many OS-specific parts, but this installer is one of them that we missed 15:51:46 i thought we would get more feedback from the diaspora community 15:51:50 and one week would be enough 15:52:04 but that was a bad assumption 15:52:17 i think it is important to publish the alpha early, but maybe we hurried a little bit with the stable 15:52:24 yes 15:52:42 i thought publishing the stable was more important because of the current situation in the country 15:52:45 just saying this so people does not loose sleep with next language 15:52:54 but maybe that was not right 15:53:53 well, it is important, and maybe we can publish the stable anyway even with some errors, but the truth is that the contributors didnt had time to have their feedback. i am not talking directly with them, maybe that is another problem of loclab gatekeeping but the people is very scared at the moment 15:54:00 maybe another language will be different 15:54:42 okay, i understand 15:55:46 anyway it was great and it was pretty fast and it worked! so it is only those two little things i would change. unfortunately we may be in a similar situation with other languages soon :S 15:56:03 (of people wanting to use tor browser because their military is shooting at them) 15:56:17 yeah, i'll write a small retrospective on this sowe can improve the process next time 15:56:24 *so we 15:56:31 thakns for this feedback 15:56:47 thanks for supporting the whole Burmese localizatoin effort and being so quick! 15:57:03 i'm happy we can help people 15:57:08 anyway thats all from me. i will open a ticket about the hecklist tonight 15:57:15 thank you 15:57:17 (checklist 15:57:45 alrighty. that's everything for today 15:57:48 thanks everyone! 15:57:50 have a good week 15:57:53 o/ 15:57:55 #endmeeting