18:59:27 #startmeeting Tor Browser meeting 02 November 2020 18:59:27 Meeting started Mon Nov 2 18:59:27 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:59:27 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:59:38 welcome everyone to November 18:59:39 Hello! 18:59:52 and the first Tor Browser meeting in that month 19:00:06 o/ 19:00:36 hi! 19:00:59 o/ 19:01:03 Pad (as usual): https://pad.riseup.net/p/tor-tbb-2020-keep 19:09:52 okay, let's see where we are 19:11:40 I guess i'll work on tpo/core/tor#40172 this week 19:12:18 maybe we can get nick to work on that instead? 19:12:19 i think the current assumption is that it's caused by something in our build env 19:12:34 idk 19:13:03 i can ask him if he can debug it 19:13:15 but i think our configuration is non-standard 19:13:32 so troubleshooting it in an rbm container may be "easier" 19:13:45 fair enough 19:14:12 the last good and first bad commit show the same configure output 19:14:23 which is a bit surprising... 19:15:14 well, nick was correct when he wrote "This is experimental and probably will break some platforms" 19:15:17 in the commit message 19:15:26 that what came to mind, yes :) 19:15:32 *that's 19:16:30 i'll try poking at this and hopefully it won't be too difficult 19:16:37 given we are only seeing this on one platform 19:17:03 and it isn't reproducible natively on a mac 19:17:32 hopefully it isn't a bug in the toolchain 19:19:52 otherwise, GeKo, i hope you had a nice/relaxing afk-experience 19:19:59 i'm going to try triaging our current tickets 19:20:05 this week, as well 19:20:09 i did. and i hope you will have so, soon, too 19:20:27 thanks, one of these days :) 19:20:49 i'm going to take one day this week, hopefully 19:20:58 and then maybe another next week 19:21:14 progress i guess? ;) 19:21:20 i'll chat with gaba about rescheduling her "Monday 9th November -> LET'S DO SYNC ON SPONSOR 58 WORK" 19:21:30 because i may not be available for it 19:21:39 small progress :) 19:22:10 yeah, we should not lose that sponsor out of sight. we are not done there, yet 19:22:18 i'd like to get a little more organized this week 19:22:52 yes, i want to have a plan for fixing/adding tests and rebasing patches 19:22:59 this month 19:23:27 but part of that meeting is triaging remaining tasks 19:23:35 and making sure we complete them 19:25:10 acat: instead of https_mode, can you start looking at running fenix tests in the testsuite? 19:25:21 i don't know what is needed for that 19:25:35 and it may require more work than we realize 19:25:38 sounds good 19:25:46 thanks 19:25:53 i suspect it will indeed require lot of work 19:26:06 i still remember boklm fighting with windows and macos tests 19:26:54 i believe there will be two parts, java/kotlin unit tests that can be run on linux 19:27:03 and then android tests that will require an emulator 19:27:14 acat: regarding tests. could you think about rebasing the tbb test changes in tor-browser 19:27:18 so i can review that piece? 19:27:28 the first part should not be too difficult, i hope 19:27:36 from what i recall looking at your changes it seemed to me we are close 19:27:51 GeKo: right, that's one is quite outdated 19:27:51 but it would be nice if we could get that piece off of our s58 plate, too 19:29:47 the last item we should discuss is our meeting time 19:29:58 i hear 1800 UTC could be okay for GeKo 19:30:12 and i saw the network team kept their meeting time at 1700 19:30:33 so we can move our meeting back to 1800 19:30:36 1900utc is better 19:30:46 but i guess i could make 1800utc work, too 19:31:04 ah ha okay 19:31:12 we used to follow utc time as that was easier for most folks 19:31:19 err 19:31:26 we used to move utc time i meant 19:31:34 yes 19:32:17 okay, if 1900 UTC is a better time for most people, then we can stay at this time until ~March 19:33:19 * sysrqb does not hear any objections 19:33:57 the time is now changed on the pad, it's official 19:34:34 okay, that's all I have for today's meeting 19:34:53 have a good week everyone 19:34:54 do you plan to look at the https-only mode like from this week onß 19:34:58 ? 19:35:09 ah, yes 19:35:10 i don't see it on the pad 19:35:15 that's on my plate 19:35:23 good 19:35:45 i'll talk with arthur about that and create a plan for desktop and android 19:35:56 fwiw @all feel free to throw things at me i am not sure how my torbrowser/s61 work balance will be 19:36:06 sysrqb: cool 19:36:07 we'll sort that out while we are going 19:36:16 s58 remaining items, will we discuss it during the release meeting? 19:36:16 but don't be shy :) 19:36:27 or can i draft a pad with what i find in gitlab :) 19:36:34 GeKo: thanks 19:36:41 antonela: we can discuss some during the release meeting 19:36:55 but now i remember gaba wanted a separate meeting for that 19:36:57 maybe next week 19:37:07 super, i dont need a dev roadmap, i just want to be sure that i have some of it in the ux backlog 19:37:18 sysrqb: i am still blocked with the remaining mozilla83 work on input from you 19:37:32 both comment- and rebase-wise :) 19:37:37 antonela: https://gitlab.torproject.org/groups/tpo/-/issues?milestone_title=Sponsor+58+-++Tor+Browser+Security%2C+Performance%2C+%26+Usability+Improvements 19:37:47 that should include most items 19:37:57 but i should triage that list 19:38:04 +label:UX 19:38:06 good stuff! 19:38:07 thanks 19:38:14 GeKo: yeah, that's at the time of my list for this today/tomorrow 19:38:22 didn't finish last week 19:38:47 *top of my list 19:39:37 thanks 19:40:04 k. thanks everyone 19:40:16 #endmeeting