17:59:37 #startmeeting Tor Browser Meeting 28 September 2020 17:59:37 Meeting started Mon Sep 28 17:59:37 2020 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:37 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:38 o/ 17:59:40 hello! 17:59:43 o/ 18:00:07 o. 18:00:12 o/ too 18:01:37 hello! 18:03:16 Congrats everyone on the Tor Browser 10 release last week 18:03:42 Overall it went smoothly without many serious issues 18:04:24 although I've mostly ignored the blog post since Thursday, so maybe I just don't know :) 18:04:32 ./o/ 18:04:46 but I think it went well, so thank you all 18:05:10 haha 18:05:40 I'm hoping we can release an alpha version of the new Android app near the near of this week 18:05:59 i think we should have most of the important pieces in place at that time 18:06:19 antonela: i've been debating if one of us should present it at the demo day 18:06:29 you should :) 18:06:40 but we don't have much time :) 18:06:42 +1 18:06:55 +9000, and prepare people to try it out when the alpha is ready 18:07:01 is good, you can just share your screen, lemme know, im sending an email later today 18:07:12 hmm 18:07:20 the timing is good 18:07:47 i'll think more about it and ping you 18:08:21 i really need to fix fenix#40040 18:08:34 but i hope we have a fix for that in the alpha, in any case 18:08:44 so it should be better by Wednesday, too 18:09:28 (being rate liited on the pad :/) 18:09:41 mikeperry, me too :( 18:09:58 ahf: for #34179, the security level isn't migrated because the Fenix code you're using doesn't have the security level implemented 18:10:21 sysrqb: so the UI is there but the prefs aren't? 18:10:23 ahf: there shouldn't be any migration needed for the security level, so I'm not too concerned about it 18:10:29 great 18:10:29 ahf: correct 18:10:36 yes, the pad is having issues, just breath there :) 18:10:42 heh 18:11:24 so if the name and type is the same i think that should be OK for the migration then, at least for the values i tried 18:11:30 heh, the pad was working well for me, but now it's automatically relaoding 18:12:02 the most important thing is that I tried some proxy script things with git but git-diff is sloooowwww when using grep and pickaxe options.. takes hours. have to go another way (probably just pre-make diff and DIY) 18:12:04 ahf: okay good. iirc, we didn't change any names for those data fields 18:12:15 so we should be good with the migration 18:12:17 fenix#40040 looks funky :o 18:12:30 ahf: i have some more data points in my head 18:12:42 i'll update the ticket after the meeting 18:12:49 it's weird 18:12:49 * antonela breath grr breathe 18:12:53 cool sysrqb! 18:13:04 antonela: :) 18:13:07 the biggest issue i think i found was the logo being the FF logo 18:13:08 lol 18:13:14 which is probably in the minor category 18:13:18 lol solid. i can handle that :) 18:13:23 yeah 18:14:06 mikeperry: okay 18:14:21 was that looking for specific symbol/function names? 18:15:41 TOPL doesn't use Tor in the library variant, right? 18:15:44 it's still as a process 18:15:47 correct 18:16:19 hm. 18:16:29 that is part of the weirdness, because it re-uses an existing process when one is still running 18:17:13 are you zapping the old process too hard so it cannot clean up after itself? 18:17:41 like how does things get terminated? from the platform or from TOPL or? 18:17:46 nope, not zapping hard enough 18:17:57 sysrqb: yeah and figuring out how to get sane context for those. git-diff -S or -G with pickaxe options are made for this, but on a repo as big as gecko-dev it takes hours per check 18:18:00 odd 18:18:28 ahf: the controller only sends a HALT command 18:18:40 ok, hm. 18:18:43 mikeperry: yeah 18:18:44 sysrqb: i wonder why we see that issue now 18:18:54 is that a tor nightly problem? 18:19:01 yep, that is the other weirdness 18:19:06 a toolchain one? 18:19:09 no, because i see it with 0.4.4.4-rc, as well 18:19:13 okay 18:19:25 because we did not change things in topl 18:19:28 this isn't a sudden upgrade from android 10 to 11 or something? it seems odd that this is different from elsewhere 18:19:32 it could be something in the new toolchain, but I am a little skeptical 18:19:35 since what we ship in 9.5.4 18:20:03 right 18:21:22 but this is one bug I have on my plate this week 18:22:02 maybe I am initializing TOPL differently than in fennec 18:22:07 but that isn't obvious 18:23:24 okay, regarding releasing an alpha version of this app 18:24:54 these are the current blockers I see: fenix#40060 tor-browser-build#40106 android-components#40006 fenix#40041 fenix#40040 tor-browser-build#40060 fenix#40026 18:25:42 I have the Network Settings issue nearly complete, so that should land either today or tomorrow 18:26:06 Security Level settings should follow closely behind that 18:26:16 so those should be ready by Wednesday 18:26:43 GeKo: you have tor-browser-build#40106 on your plate? 18:26:51 yes 18:26:58 great 18:27:21 fenix#40060 should be resolved (we'll see with today's nightly) 18:27:53 not sure if blockers, but if there's nothing more prioritary i could pick fenix#40061 and fenix#40058 18:29:25 i didn't look at tor-browser-build#40057 last week 18:29:35 so we may not have localization in the first alpha 18:29:44 acat: hrm 18:30:26 sysrqb: if you can solve the blocker for that bug 18:30:34 i can fix #40057 this week, too 18:33:06 acat: fenix#40054 is another nice-to-have but not very high priority 18:33:20 ah right 18:33:34 GeKo: okay, I'll try looking ath the l10n ticket early this week 18:34:21 acat: using Google as the default isn't the worst situation for this first alpha 18:35:00 but using ddg would obviously be better 18:35:21 ok, i'll pick that one too 18:35:23 but i'm not sure how we should prioritise those three tickets 18:35:55 sounds good 18:36:16 i think we should prioritise the default search engine higher than fenix#40058 18:36:40 because we don't recommend people install new addons, in any case 18:37:02 but all of these issues should be fixed before the stable release 18:37:09 yeah, i agree 18:38:24 another ticket you can look at is fenix#34406 18:38:36 i don't think i have time for that one this week 18:38:46 and it is at risk of missing 10.0 18:38:59 we could backport it from 10.5, if the patch is not too large 18:39:30 and I think it won't require many changes within a-c 18:39:47 i briefly looked at the code one or two weeks ago 18:40:27 what is left from the feature-parity goal with fennec-based tor browser? 18:41:02 i believe that is the only missing ticket 18:41:06 sysrqb: but fenix#34406 is just for design work? or you mean tor-browser#34377? 18:41:25 sysrqb: yeah, that was my feeling, too, good 18:41:27 acat: ah, yes, thanks 18:41:45 ok 18:41:55 we'll, i'll add it to the list :) 18:41:58 and i am willing to let this one slip, if we have a stable app with security level and network/bridge config 18:42:13 yup 18:42:25 but if we can finish it, then that would be better 18:42:52 acat: so, i think you should prioritize the bug fixes and the search engine 18:43:09 but if you have time for the onion indicator, the nplease try doing that too 18:43:20 good 18:43:25 acat: im happy to provide anything you need there 18:43:50 acat: this is the UI ticket for it https://gitlab.torproject.org/tpo/applications/fenix/-/issues/34406 18:44:35 antonala: thanks! 18:44:39 *antonela 18:44:50 (: 18:45:21 * sysrqb reloads the pad, again 18:45:47 i think the only other topic i have for this meeting is discussing Tor Browser 10.0.1 18:47:20 tor-browser#40140 torbutton#40013 tor-browser#40156 18:47:53 i think the last one is av related and not much we can do about 18:47:55 those are the tickets on my radar from the Tor Browser 10.0 milestone 18:48:08 what about tor-browser#40163? 18:48:32 it's not in the 10.0 milestone :) 18:49:02 tor-browser#40139 is fair game, too, i think 18:50:17 but that reminds me about disabling picture-in-picture 18:50:39 which we did and which landed 18:50:40 tor-browser#40147 18:50:56 was that investigated? 18:51:02 nope, disabled 18:51:19 it was not working in any case, just the icon was showing on hover 18:51:51 so it will have to be investigated and then fixed :) 18:52:07 ahtor-browser#40148 18:52:12 ah tor-browser#40148 18:52:22 i didn't see that land 18:52:24 thanks 18:53:23 i missed to add that one in the pad 18:53:29 *forgot 18:53:36 tor-browser#40163 tor-browser#40139 are possible 18:53:49 probably with a small preference for fixing the disk leak 18:54:25 i have some tickets to file for small pref updates we missed 18:54:52 but that should be easy to squeeze into 10.0.1, too 18:55:03 "easy" :) 18:55:07 but yes, sounds good 18:55:09 *flip* 18:55:12 done 18:55:34 when we are planning to release 0.1? 18:55:57 i left some comments here https://gitlab.torproject.org/tpo/applications/torbutton/-/merge_requests/20, i'd love to have isabela, ggus, alsmith review on it soonish 18:56:07 let's plan on 13 October 18:56:13 cool 18:56:17 we don't have a definite date 18:56:38 we will need to see some proofs of the l10n versions too 18:56:40 but that is a good target and that should give us some time for finish all of these tickets 18:56:51 could you attach them in the ticket acat? 18:57:03 sysrqb: sounds good for me! 18:58:09 we'll have nightlies soon after acat's done with the changes 18:58:12 (too) 18:58:13 antonela: yeah, will do 18:58:19 super, thanks folks! 18:58:59 * sysrqb reloads pad again 18:59:11 that's all I have for today, iirc 19:00:19 thank everyone 19:00:26 thanks! 19:00:33 thanks! 19:00:36 o/ 19:00:42 #endmeeting