15:58:59 #startmeeting Tor Browser 10.5 Roadmapping 15:58:59 Meeting started Thu Nov 19 15:58:59 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:58:59 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:10 hi 15:59:31 http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/TB-roadmap-planning-keep 15:59:45 or https://pad.riseup.net/p/TB-roadmap-planning-keep 16:00:18 i started sketching our general focus at the bottom of the pad 16:00:36 for what I think we can accomplish between now and ~March 2021 16:00:41 hi! 16:00:52 o/ 16:01:02 i guess we need to add steven's think, too? 16:01:07 *thing 16:01:17 last week we stopped at s58 issues 16:01:18 * antonela added steven's on ux roadmap somehow 16:01:20 right 16:01:23 it's supposed to start in january 16:01:25 iirc 16:01:43 i think March 2021 is a good target for 10.5 becuase we need to start transitioning to the the next esr after that 16:01:55 (hopefully only macOS and Windows, at that point) 16:02:25 GeKo: yes, steven's thing should be February and March, roughly 16:02:49 but i'm not including any of that in 10.5, except HOM 16:03:34 acat: i'll send you the details of this side project we'll be working on 16:04:00 ok 16:05:49 should we continue with s58 now? 16:06:02 and follow the pad... 16:06:18 I'm including that for covering the final pieces of it 16:06:28 like the remaining automation and testing 16:06:40 which are still not complete 16:08:38 how does the rappor and seedin hsts cache thing get onto our current roadmap? 16:08:44 *seeding 16:09:04 that is the Steven thing 16:09:11 aha 16:09:26 sponsor xx 16:09:46 i added it as crew project 16:09:47 yeah. i guess we will have a sponsor number associated with this 16:09:51 we still do not have a number for that sponsor 16:10:02 CREWS project 16:10:22 whatever that is :) 16:10:23 Collaborative ResistancE to Web Surveillance (CREWS) is the name of the project 16:10:30 thanks 16:12:32 that's rappor only? or seeding HSTS cache too? 16:12:46 Okay, at the bottom of the pad is a rough set of goals for 10.5 16:12:50 acat: both 16:13:06 (see email) 16:13:41 thx 16:13:59 i think this fills our plate well enough for the next ~5 months 16:14:03 so, if 10.5 is now due in march instead of june 16:14:18 the roadmap will likely be more than enough for us 16:14:36 I felt including all of this plus an ESR transitoin was a lot for 10.5 16:14:47 do any of you disagree? 16:15:18 i think the driving factor for 10.5 was sponsor 30 16:15:49 i am not sure whether we get to do all the things for that until march 16:15:53 but maybe we do 16:16:40 that is the .5 release has usually been the release were we include our own big new features 16:17:38 i think the transition onto the next esr/rr needs to take priority over S30, if they conflict 16:17:50 i'm somewhat anxious now that im not going to be here for stable, i was expecting 10.5 for june 16:17:51 BUT 16:18:09 and arriving at June with a pile of S30 patches and a transition on 91 is a lot of changes 16:18:34 for june we can have multiples 10.5.x :) 16:18:59 there is a minimum work of s30 that really needs to happen 16:19:27 i'm also okay with delaying S30 in stable until 11 16:19:47 and 11 could be in August 16:19:55 that would be fine 16:19:57 if S30 is stable then 16:20:04 so 16:20:18 91.0 will be out 7/13 16:20:30 and we need to get away from 78 until 10/05 16:20:46 so i doubt tor browser 11 will be out in august 16:20:47 I would love to have the roadmap reflected in https://gitlab.torproject.org/groups/tpo/applications/-/boards each month 16:21:04 unless we think we'll be away from esr for all platforms by then 16:21:06 GeKo: oh. i misread the table. hrm. 16:21:07 sysrqb: yes, i think we talked about splitting s30, some of this work can happen for 10.5, other for 11 16:21:23 okay, i don't know what numbers I was looking at 16:21:39 mozilla changed them!1!! 16:21:45 over night 16:22:09 okay, let's back up and start this conversation again :) 16:22:23 in general, i am fine if we think 10.5 shall get out in march 16:22:39 but it will be quite tight with things on our roadmap alone 16:23:30 or the proposed roadmap that is 16:24:01 right, i agree 16:24:09 me too 16:25:16 okay, let's say Linux is moved onto rapid release for 10.5 stable, and macOS and Windows remain on ESR 16:26:06 we can essentially start the transition onto 90/91 in Nightly as early as we want 16:26:20 but stablizing 10.5 in June is still reasonable 16:26:55 and then we have July and August for stablizing 11 on 91esr 16:27:09 * antonela :) 16:27:33 i think it's reasonable 16:27:42 and 11 is released in September 16:29:00 yep 16:29:53 okay, good. 16:30:36 ok, this is the overview of the goals in the roadmap until next year. 16:30:54 can we have something more specific for this year where we can see and follow this roadmap 16:31:37 yes, we can break these down into specific tickets 16:31:44 you mean the remaining 4-5 weeks? 16:32:11 yes 16:32:14 until dec 23rd 16:32:25 at least 16:33:59 Sponsor 58 (as described above) 16:33:59 Move nightly builds into TPO infrastructure 16:33:59 Stabilize Android Rapid Release processes 16:34:00 Sponsor 30 (as described above) 16:34:11 (part of S30) 16:34:32 those are our primary focus for the next month 16:35:01 we'll find or open the specific tickets that we'll work on in this time 16:35:57 plus investigating "Enable HTTPS-Only Mode" 16:36:01 Sponsor 58 (as described above) is https://gitlab.torproject.org/groups/tpo/-/milestones/11 16:36:06 is a question 16:36:37 the action we had from last week was to close tickets or remove them from s58 if that will not happen 16:37:19 antonela: yes, remainder of tor-browser#33656 and tor-browser#33660 16:37:25 ah, no tor 16:37:35 Obj 1.2 16:37:35 Automatic patch rebasing 16:37:35 Rebase failure notifications 16:37:35 Obj 2.4 - Audit tickets by the end of November 16:37:35 Finish/close audit tickets 16:37:37 Fix broken Android unit tests 16:37:40 Obj 2.3 16:37:42 Implement Android integration tests 16:37:45 that is what is missing 16:37:55 gotcha 16:37:58 tpo/applications/tor-browser#33656 tpo/applications/tor-browser#33660 16:38:21 hrm. okay, anyway.... 16:38:44 we do not have the bot here 16:39:16 yeah, seems not 16:39:46 acat: are there any items you want to work on that aren't included in the list at the bottom of the pad? 16:39:50 yes, #33661 needs to be closed 16:40:36 GeKo: same for you ^ 16:40:58 even though we don't know how much time you'll have for this 16:41:06 what does "at the bottom" mean? you mena "Current Roadmap"? 16:41:08 sysrqb: i think we should be good with those 16:41:10 *mean 16:41:26 GeKo: yes, and "reach goals" 16:41:27 line 95 and beyond 16:41:42 yeah 16:41:50 i think we should discuss at some point whether all the reach goals are really important 16:41:53 I bolded the items we'll focus on for the remainder of this year 16:41:57 i am not convinced yet 16:42:07 but i think the current roadmap is a good start 16:42:16 and how much capacity. Geko: you have mostly s61, not sure how much time you will spend with the stuff from this roadmap 16:42:32 like i agree those are the items we should tackle now and in the near future 16:42:51 and if we have capacity for more then we can discuss what else to pick 16:43:29 yes 16:43:44 it's mostly s61 for me 16:44:08 i won't be able to pick up any shiny features 16:44:17 and likely no s30 work 16:44:35 yes, i was thinking acat was going to focus on s30 16:44:51 i suspect keeping the release train running, including rebase review etc. will consume most of my time 16:45:02 + doing other maintenance stuff 16:45:22 yes 16:45:39 + helping with the actual releases 16:46:47 okay, i'll really find some time and organize these tickets today/tomorrow 16:47:18 matt 16:47:23 and we'll know what we need to work on 16:47:28 antonela 16:47:46 sysrqb: maybe we can start doing this during our sync today 16:47:47 one thing we need to make sure is that both browsers should get updated in jan when the eoy campaign ends 16:47:53 i'll open that ticket so we dont forget 16:48:03 thanks antonela: can you put a due date on it? 16:48:05 antonela: yes please 16:48:08 thanks! 16:48:18 gaba: sounds good 16:48:23 yes yes 16:50:36 okay, anything else we should discuss? 16:51:08 I will add goals and overview for roadmap to the wiki page 16:51:19 thanks gaba 16:51:29 actually, it is here: https://gitlab.torproject.org/tpo/applications/team/-/wikis/home 16:52:03 looks great! 16:52:25 (I'll clarify "RAPPOR") 16:52:44 (i don't want people getting the wrong idea about that) 16:53:31 10.5, best Tor Browser ever :) 16:53:36 can we scope the ux work there? 16:53:53 not now 16:54:01 but sometime next week :) 16:54:14 yes 16:54:25 tuesday? 16:54:29 sounds good 16:54:35 the crews project is sponsor 103 ! 16:54:40 ! 16:54:50 exciting! 16:55:14 so it's sponsor xxx actually ;) 16:55:22 instead of sponsor xx 16:55:24 antonela: acat 1500 on Tuesday? 16:55:33 GeKo: heh 16:56:01 sysrqb: ok for me 16:56:11 wfm 16:56:15 great 16:56:58 * gaba added a label for s103 so we can start tagging tickets 16:58:01 kickoff will be in jan so no rush... 16:58:39 yeah, but i want to make sure that i understand what is going on to onboard duncan on it 16:59:03 yep 16:59:05 heh 16:59:17 i forgot to add tor browser performance improvements to the wishlist 16:59:39 ha 16:59:49 what does that include? :) 16:59:50 like (ab)-using some kind of tracking protection 16:59:55 ah 16:59:57 dropping the bomb at the last minute 17:00:01 no, no 17:00:08 you can still add it on the wishlist :) 17:00:13 it would be in Reach Goals anyway at most 17:00:21 yes 17:00:51 okay, i'm going to close this meeting 17:00:52 so we can pick that discussion up later once we want to pick someting out of that basket 17:01:05 sounds good 17:01:11 thanks everyone! 17:01:14 if you say "tor browser performance improvements" nobody will complain! 17:01:16 haha 17:01:18 thanksss! 17:01:24 i know :) 17:01:26 heh :) #truth 17:01:29 #endmeeting