18:29:29 #startmeeting Tor Browser Team Meeting, 04 November, 2019 18:29:29 Meeting started Mon Nov 4 18:29:29 2019 UTC. The chair is sysrqb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:29:29 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:29:33 yup 18:29:36 hello! 18:29:37 hello everyone 18:29:44 o/ 18:29:45 hi 18:29:52 hi 18:30:10 hi 18:30:19 hi 18:30:32 hi 18:31:09 hi 18:31:23 hi! 18:32:44 okay, last few updates are coming in now 18:33:39 ( antonela ping, just in case you're coming to the meeting, too) 18:34:06 okay, today is another fun release week 18:34:11 pospeselr: thanks for all your work on letterboxing. I will try to upstream your code when you make improvements :) 18:34:20 :) 18:34:26 +1 18:34:52 looks like there's recently been some upstream changes to RFPHelper.jsm that should probably be backported 18:35:03 we should have 9.0.1 coming out today/tomorrow, and 9.5a2 coming out ~1 day later 18:36:18 pospeselr: are they useful changes? or will they make backporting/upstreaming easier? 18:36:37 "useful" being funcational improvements 18:36:38 yeah looks like it's fixes for the findbar and devtools 18:36:47 ah, neat 18:37:10 pospeselr: they are backported 18:37:13 lol nevermind, yeah 18:37:16 and available in 9.5a2 18:37:23 i just learned about them because of gk's commit email 18:37:24 (at least that was my plan ;) ) 18:37:25 for them 18:37:25 anyway 18:37:48 but there might be moew 18:37:51 *more 18:38:55 okay, not many bold updates this week 18:39:36 boklm: thanks for quickly fixing the reproducibility issues on Android 18:40:19 you're welcome 18:40:21 pospeselr: can you pick this up and redo the .apks? 18:40:38 yeah, is there a build2 tag? 18:40:39 we need that to get the release finally signed and out 18:40:44 probably tomorrow 18:40:51 there is! :) 18:41:19 sysrqb: so, while talking release 18:41:21 while we're thanking boklm, thanks for fixing up my build_go_lib patch :) 18:41:24 Jeremy_Rand_Talos: i don't know which are the blockers for namecoin 18:41:44 Geko: build started 18:41:46 GeKo: yes? 18:41:47 thx 18:42:15 i wonder whether we should put out the alpha like within the next two days 18:42:20 too or not 18:42:46 alphas are precious in the sense that they help us testing stuff for the next stable 18:42:52 and for stuff we want to backport 18:43:23 so, everything that does not get into the upcoming alpha 18:43:32 but should tested in one first before hitting stable 18:43:38 needs to go in the next one 18:43:46 which is currently scheduled for dec 3 18:44:00 which means it would reach stable earliest in jan 2020 18:44:31 so, the question is whether we want to put something more into this alpha 18:44:32 sysrqb, yeah, so at some point we'll need to figure out which of those things are blockers. Doesn't necessarily have to be during this meeting, but I wanted to get that stuff on your radar since most of the critical work on my end is nearing completion 18:44:44 to have this already available in the dec 3 stable release 18:45:09 I think yes, there are some patches we should get into a alpha soon 18:45:28 we could plan another alpha in a couple mweeks, in between now and December 18:45:43 yes, that's one option 18:45:44 but that is a burden on our limited resources, too 18:45:52 yep 18:46:13 so i was pondering whether it would be helpful to delay the alpha release until, say, friday 18:46:20 other than EOY campaign, i'm nomre in favor of delaying 9.5a2 18:46:21 to get still stuff in 18:46:30 *i'm more 18:46:44 yeah 18:46:57 maybe we should talk to sstevenson about that 18:47:12 Jeremy_Rand_Talos: none of your points is a blocker for nightly 18:47:34 i would not want to delay 9.5a2 for long 18:47:44 but some days might not hurt much 18:48:00 but gives us more time to work on things like #32303 18:48:10 pili: yeah 18:48:14 err 18:48:15 yeah 18:48:18 :D 18:48:19 :) 18:48:38 pili: we should check with sstevenson about how important the alpha biuld is for EOY campaign 18:48:45 i think we can argue it's not too important 18:48:46 will do 18:48:49 compared with the stable 18:48:55 I would agree 18:49:00 but it's still money... 18:49:00 and I'll double check 18:49:09 or potential money 18:49:10 GeKo, ok great, sounds good. In that case, I should have a tor-browser-build patch for Namecoin for your consideration ready within the next week assuming nothing unexpected comes up 18:49:20 Jeremy_Rand_Talos: sounds good 18:49:21 we have some graphs showing a very small percentage of users on alpha 18:49:30 GeKo: yes, that's definietely true 18:49:49 sysrqb: I was just about to ask about percentage of users :) 18:49:54 https://metrics.torproject.org/webstats-tb-channel.html is the graph 18:50:13 i guess we should define some tickets we really think should go into the next alpha 18:50:43 and then build a path forward taking fundraising folks' opinion into account 18:50:49 * GeKo shuts up now 18:52:00 thanks GeKo, that was a good discussion point 18:52:59 sisbell: do we need a buster container for https-everywhere ? 18:53:36 I'm getting an error since we are using debian 18:53:56 I don't know of a way to mix containers in a build 18:54:15 I think we can keep it on stretch for now 18:54:46 I'd need some pointers on how to do this. I;ve checked in the code I have for review 18:55:01 please talk with boklm about that this week 18:55:12 sure 18:55:34 thanks 18:56:19 ok, so I've been talking to sstevenson and she's fine to wait for the alpha on Friday as long as the about:tor changes are released to the majority of users later today/tomorrow 18:56:32 sisbell: i also gave some feedback on #30552, can you pick up that ticket again this week? 18:56:44 pili: great, thanks 18:57:28 Yes. I made changes but I'll add some more comments about what those are. 18:57:41 thanks 18:58:07 Okay, GeKo already responded to my first discussion point 18:58:24 i don't think there's much more to discuss about #30429 and #31010 right now 18:59:07 sisbell: do you know if we need #31650? 18:59:17 _hc isn't around right now 18:59:26 but I'm not sure how we should prioritize that ticket 18:59:28 It looks like firefox is handling this. 18:59:36 But I think its a good idea to do anyway 19:00:11 okay, we can schedule it as a nice-to-have 19:00:14 Its a quick fix 19:00:25 but not a priority if there are other tickets that are more important for a release 19:00:31 okay, good 19:01:10 well, it seems we reached the end of updates and discussion points 19:01:29 should we talk about work outline for november? 19:01:32 does anyone want to bring up anything else in this meeting? 19:01:40 i.e. is everyone clear on what to work on? 19:01:54 yes, that was my next idea if no one had anything else 19:02:19 heh 19:03:17 https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~TorBrowserTeam201911&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&col=points&desc=1&order=id 19:03:29 we're at the beginning of another month 19:03:50 GeKo and pili moved tickets into 201911 19:04:22 we started marking ticket priorities for this month 19:04:52 we haven't touched all tickets yet 19:05:07 high priority tickets will be the most important tickets we should work on this month 19:05:28 I haven't given tickets any priority yet after our talk :) 19:05:29 and medium priority tickets will be the tickets we work on after the high priotiy tickets are completed 19:05:30 will do so later today or first thing tomorrow 19:05:37 pili: yep :) np 19:06:29 we'll be picking up S27 tickets again this month 19:06:52 hrm, i wonder what is the most useful way of explaining this 19:07:10 explaining what? 19:08:06 which tickets are most important this month, out of the list of 201911 tickets 19:08:43 but maybe that's not too important right now 19:08:58 i thought we'd have the prio thing for that? 19:09:00 we'll go through all the tickets and mark them with their priority 19:09:07 we will, but we don't right now 19:09:25 maybe saying this is enough? :) 19:10:06 okay, let's discuss this during next weeks meeting, after we update all the ticket priorities 19:10:19 everyone has their tasks for this week already 19:10:34 boklm: i think we need to re-focus on s9 work 19:10:45 does that make sense? 19:10:48 otherwise we risk the dependency for the user testing 19:10:51 sysrqb: yes 19:11:12 boklm: given the estimates you gave me today 19:11:39 it seems you should only work on the nightly updater from now on until it is ready 19:11:46 reviews are fair game 19:11:57 ok 19:12:00 (as long as they are not super-complicated) 19:12:09 and release related work, too 19:12:19 i try to comensate #32052 19:12:32 *compensate 19:12:45 by trying to get more help from mozilla folks if needed 19:12:54 it kind of sucks but here we are 19:13:01 ok, so I will focus on #18867 this week 19:13:06 so, please drop the fpcentral items as well 19:13:12 they are not important right now 19:13:16 (alas, again) 19:13:23 thanks 19:16:13 GeKo: do you think #32138 is a good use of acat's week? 19:17:28 i don't think so 19:17:38 maybe backporting #23719 is better? 19:17:40 i think making progress on s27 sounds like a better plan 19:18:08 you mean for 9.5a2? 19:18:15 yeah 19:18:22 that was my thought. 19:18:30 sounds good 19:18:49 should not be overly involved given that tjr provided some patches already 19:19:03 okay, acat can you work on #21952 and #23719 this week? 19:19:03 making sure that things don't explode is smart, though :) 19:19:22 yes, not-exploding is important 19:19:29 sure 19:19:33 thanks 19:19:56 acat: #23719 for wednesday would be neat 19:20:11 so, we have some time to build and sign the release etc. 19:20:33 pospeselr: before you dive further into letterboxing bugs. can you pick up one of the higher priority November tickets? 19:20:43 yeah i can do that 19:20:58 i'll let you know when the list is updated with priorities 19:21:01 thanks 19:21:16 i think it might be smart to start with the per-site security settings 19:21:25 because that one will take a while :) 19:21:33 that would be a good one 19:21:52 and oh look, it's already assigned to me :3 19:22:05 so-weird. 19:22:06 there you go! 19:22:11 are the letterboxing changes really close to done, or not close at all? 19:22:49 (I am just thinking that doing something to reduce confusion there would be good, but not if it is going to take a long time) 19:22:59 yeah, i was looking at "start work on exposing an option in about:preferences to toggle letter-boxing (#32325)" 19:23:08 and concerned with starting something new 19:23:17 sysrqb: ah, got it 19:23:22 #32220 is nearly done, i've a patch that's working now, but isn't *quite* perfect (it letterboxes on creation of new windows when it should just fit the whole screen) 19:23:25 if #32220 is close, then finishing it makes sense 19:23:40 i would expect to finish get it up for review with a fix today 19:23:53 but the other two are surely rabbit-holes 19:24:01 cool. tht sounds good 19:24:03 that 19:24:19 ok 19:24:28 i'll finish 32220 then move on to per-site 19:24:55 thanks 19:25:15 okay, any last questions/comments/concerns before i close this meeting? 19:25:34 <- is fine 19:25:38 nothing else from me 19:25:48 I'm good 19:25:53 okay, great, thakns everyone 19:25:57 have a good week! 19:26:02 #endmeeting