18:59:34 #startmeeting Tor Browser meeting 16 Nov 2020 18:59:34 Meeting started Mon Nov 16 18:59:34 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:59:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:59:54 o/ 19:00:35 o/ 19:00:51 I added a few things to the agenda for today 19:00:55 http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-tbb-2020-keep 19:01:06 * antonela waves 19:03:42 ooookay 19:03:56 i did not prep for this meeting as much as i planned 19:04:30 well, we can always move the triage discussion for next week and get a little more prepared 19:04:44 i added one topic about issue templates. I would like to add them to the repos 19:04:56 in line 52 i link to examples of it 19:06:25 nice 19:06:27 templates are great 19:06:30 +1 to add them! 19:06:47 if you have any comment/opinion abou tthem please add a comment to the issue 19:06:59 the issue is for all repos? 19:07:05 and if nobody complains then I will add them to the repos on the applications group 19:07:07 should we discuss the ones for tb specifically? 19:07:11 we can add them per repo 19:07:24 yes, i added it here to discuss the ones related to the applications group specifically 19:07:37 we can have a different template for the issues in TB than the other repos 19:08:56 any other thought? 19:08:58 do you have a draft for the TB ones? or do we want to iterate what is suggesting here? https://docs.gitlab.com/ee/user/project/description_templates.html 19:09:23 create an issue, propose a feature, join beta testing are great 19:09:24 i want to iterate from what im suggesting in the issue linked in the pad 19:09:40 https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/47 19:09:52 https://gitlab.torproject.org/gaba/sandbox/-/issues/new 19:10:13 documentation, bug report, feature request 19:10:20 oh i see, anarcat is having the same questions i did haha 19:10:35 cool, we can discuss TB ones there (in that ticket) 19:10:39 oh, nice, many templated 19:10:42 *tempaltes 19:12:16 ok, the next item i have is mostly that i just wanted to check if anybody is getting the feedback in google play 19:12:25 yes, I'd be very happy adding some of these 19:12:32 +1 19:12:40 will explore the options and comment in your ticket gaba 19:12:42 and I'd like one for transitioning onto the next firefox version 19:13:04 I looked at some of the google play comments 19:13:13 re gplay, i sadly read the user feedback, some of them yes 19:13:20 none of them were helpful 19:13:26 but i only looked at ~30 19:13:31 i asked arthur a point of contact in fenix to talk about this feedback 19:13:43 he gave me, so i have plans to email her this week 19:13:47 great 19:14:02 i'll not open issues in their repo 19:14:05 antonela: can you cc me? 19:14:07 i have not capacity to that 19:14:10 sysrqb: for sure 19:14:13 thx 19:14:29 but i want them to be aware of it as a source of incoming feedback 19:14:47 that's a good idea 19:15:21 lets see if it works 19:16:04 i assume they receive similar feedback on their apps 19:16:14 but we have some users who don't use firefox 19:16:24 so we may get some new feedback 19:16:29 they do actually, i've been lurking the repo last week and some things are already there 19:16:37 but you know, is about qty sometimes 19:16:39 lets see 19:17:11 we got some push from the omnibox in the last desktop update, but then people got used to it 19:18:06 yeah 19:19:39 ok 19:19:52 the last item in the agenda is to talk about triage issues in the application group 19:21:24 i think presenting a draft and then discussing it next week may be more productive 19:21:40 but if anyone has more they want to say about it, then we can discuss it now 19:22:07 from the sync we had earlier, i'll begin triagining tickets today 19:22:09 ok, let me add an issue to https://gitlab.torproject.org/tpo/applications/team and we discuss it there 19:22:32 i can do it on wednesday or friday 19:22:51 and we'll triage tickets three time each week, on monday/wednesday/friday 19:23:00 i can pick up the other option 19:23:12 whatever that is :) 19:23:15 3 times per week? 19:23:25 acat: GeKo i don't have a preference, so you can fight over it :) 19:23:41 antonela: yeah, just making sure we are keeping track of new tickets that are opened 19:23:45 haha, i keep my fighting for important stuff 19:23:45 isn't that too much given the current capacity? 19:24:05 * acat flips a coin 19:24:08 antonela: no, not if we only get 0 or 1 ticekt in that time 19:24:10 https://gitlab.torproject.org/tpo/applications/team/-/issues/1 19:24:17 oh i see 19:24:22 only new tickets 19:24:25 not old tickets 19:24:27 yeah 19:24:39 well, the old ones is still on my plate :) 19:24:41 mostly bug reporting then 19:24:48 GeKo: indeed 19:24:49 and it bubbls up slowly 19:24:52 we need to triage those tickets at some point (soon) 19:24:53 ok, i'll do wednesday :) 19:24:53 *bubbles 19:25:04 great, friday it is then 19:25:16 haha 19:25:20 but that's not (really) included in tihs triaging role 19:25:38 we can slowly chip away at them, as we have time 19:25:48 sysrqb: speaing of which i plan to get back to design document updating soon. i think i can make some progress in my spare time 19:25:51 and maybe we all grab two older tickets during our triaging, as well 19:25:52 *speaking 19:26:15 actually, i will prioritize that still higher than trigaing older tickets 19:26:25 GeKo: yeah, i put that on my plate a few weeks ago, and then it fell off again 19:26:31 the design doc 19:26:45 but that is something i would like to see updated before we move onto 10.5 19:26:50 ok, adding all this to the pad so we can start documenting it for the wiki... 19:26:54 oh, i actually triaged all tor browser tickets up to #11XXX 19:26:55 and, in particular, desktop rapid release 19:27:09 so, those, should be in better shape that those later 19:27:26 great 19:27:28 but, yeah, that whole thing will involve some effort 19:27:39 could you add an UX label to tickets that needs UX/UI help during your triage? That will help us to set up some priorities :) 19:27:46 we did triage a little during the gitlab migration, too 19:27:53 indeed! 19:27:57 but we didn't cover the remaining ~3000 19:28:18 antonela: yes we'll add that 19:28:37 the same if the ticket needs other teams work 19:28:47 we have labels for core and anti-censorship 19:29:14 sysrqb: excellent 19:29:16 ah, indeed, 19:29:23 "cCre" 19:29:30 *"Core" 19:29:35 I wouldn't guess that :) 19:29:50 haha 19:30:02 that is good to know 19:31:17 acat: can you add the github ticket onto android-components#34439? 19:32:05 ok, actually it's the geckoview one for now, so i'll do it with the one in tor-browser 19:32:29 ah, okay, yes please, thanks 19:33:14 okay 19:34:15 Tomorrow we're releasing 10.0.5 and 10.5a4 19:34:44 10.0.5 is already synced on the staging web server 19:34:59 does anyone want to create the blog post for that? 19:35:09 if not then I can easily do it 19:35:25 (we haven't been this prepared for a release in a long time) 19:35:36 so that is exciting 19:35:44 nice! 19:36:46 tomorrow's 10.0.5 is desktop-only 19:36:59 and we'll plan on releasing a stable for Android next week 19:37:36 if all goes well, this will prepare us for releasing stable desktop and android versions at the same time in the future 19:38:00 oh, and that reminds me 19:38:38 i've tried updating https://gitlab.torproject.org/tpo/applications/tor-browser/-/wikis/Release-Schedule 19:39:02 and, i started maintaining a calendar, as well 19:39:04 https://nc.torproject.net/apps/calendar/p/M9SGxmtCEr42xJyj 19:39:06 lovely 19:39:12 ahh, great 19:39:12 (that should be public) 19:39:58 this is a little more burden then I'd like, but i think it is worth seeing visually where all of these versions are on the calendar 19:40:04 and how they overlap with other events 19:40:13 afk/holidays/etc. 19:42:08 sysrqb: thanks, i think it's very useful 19:44:05 and that reminds me that GeKo acat, we should sync about how we squeeze an Android alpha into early January 19:44:21 yeah 19:44:47 i am around 19:45:01 I can ping you tomrrow around 1400 UTC if that is better than tonight 19:45:05 for some value of "around" 19:45:19 :) 19:45:31 :) 19:45:53 but, yes, we should generally think about how the TPI vacation for us should work 19:45:53 do we do roadmapping episode II this week? 19:46:13 antonela: yes, that is my plan 19:46:29 GeKo: yeah, i'd like to have a plan for a chemspill, as well 19:46:38 just in case :/ 19:46:58 * GeKo avoided the thing-that-must-not-be-named 19:47:08 lol 19:47:51 voldemort is not too bad, if you face it directly :) 19:48:08 weellllll 19:48:11 but, anyway, yeah 19:48:12 depends who you are 19:48:38 but more mundane things: tor-browser#40235 19:48:43 a new cycle begins 19:48:51 how do we distribute the work? 19:49:07 indeed 19:49:10 as "usual"? 19:49:20 i'm fine with keep the usual roles 19:49:30 ok, wfm too 19:49:39 but i can switch if someone wants to dive into the proxy audit stuff 19:49:46 i think we should eventually rotate 19:49:57 so we have enough shred knowledge 19:50:00 *shared 19:50:03 i prefer to get back on track time-wise first 19:50:13 but i feel like we're still..yeah 19:50:19 with proper alpha releases in time etc. 19:50:20 we're not quite on solid ground, yet 19:50:34 *on time 19:50:57 sounds good to me 19:51:47 GeKo: thanks for opening those tickets again 19:53:17 yeah 19:54:33 gaba: should we continnue adding the Sponsor 58 label on tickets? 19:54:47 i'm not sure when is the official end date 19:54:59 i know hte report is not due until January 19:55:11 (end of january?) 19:55:14 *the 19:55:26 the report is not due until january but we should start wrapping up 19:55:43 we should close the stuff that we have and close s58 19:55:50 okay 19:56:16 i noticed tor-browser#40235 has the label 19:56:20 and it is correct 19:56:38 but i'm not sure how long we can claim these transitions are part of S58 19:57:02 yeah, i was on the fence 19:57:07 maybe this is the final move that is part of S58? 19:57:11 i think it is better to remove the label 19:57:34 *shrugs* 19:57:51 let's not add anything else to s58 unless is part of the work that we are already finishing 19:58:24 okay, then we can delete the label on this new ticket 19:59:02 done 19:59:06 thanks 19:59:14 okay, we're at the hour mark 19:59:29 any last comments? 19:59:59 acat: based on our friday's review, i updated https://gitlab.torproject.org/tpo/anti-censorship/trac/-/issues/40004 20:00:00 alrighty, have a good week everyone 20:00:05 if anything else is missing, let me know! 20:00:14 antonela: thanks! 20:00:19 antonela: sneaking in before I close the meeting! 20:00:29 i was patiently waiting for 1 minute! 20:00:30 #endmeeting :)