19:01:02 #startmeeting tor-browser 19:01:02 Meeting started Mon Feb 20 19:01:02 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:01:06 hi all! 19:01:12 hi everyone! 19:01:17 hi! 19:01:25 i am sure you missed last week's tor browser meeting 19:01:33 we are back on track 19:01:42 i guess i can get started today 19:02:05 i was afk last week and worked a bit on various things the week before 19:02:15 mainly doing email and tor browser spec update 19:02:25 alas i did not finish the last item 19:03:04 today i dug out of my backlog and looked at two patches #20761 and #21308 19:03:28 i looked as well at the upcoming esr45 fixups and filed #20514 19:03:31 err 19:03:35 #21514 19:04:19 this week i plan to finally finish the spec update, continue reviewing esr52 features and 19:04:33 try to get selfrando builds for the alpha running (64bit linux) 19:04:49 i hope to polish my mingw-w64 related patches for esr52 as well 19:04:53 that's it for me 19:05:04 oh, and if there is anything i should look at let me know 19:05:18 i might have missed something while goiong over my backlog 19:05:27 that's finally it :) 19:07:20 A quick comment on #21514: if it is possible to do so, we should ask the Mozilla patch author why they removed that code. 19:07:55 we could it seemed to be just some clean-up to me, though 19:08:09 (maybe they only did it to make backporting the sec fix easier but it isn’t clear) 19:08:14 OK 19:08:59 * mcs can go next 19:09:13 Over the past two weeks, Kathy and I did some research for #21267 and created a patch for #21268. 19:09:20 We created an additional patch for #21201. 19:09:25 We reviewed arthuredelstein’s patches for #21308 and #21309. 19:09:33 We built Tor Browser using RBM and posted a few issues to #17379. 19:09:39 We did some research for #21431 and #21445. 19:09:53 Then we worked on #19048. So far we have finished looking at bug lists and developer docs for Firefox 46 - 48. 19:09:59 This week we plan to continue working on #19408 (we still need to post our Firefox 48 findings to the ticket and we need to review the changes made in Firefox 49-52). 19:10:06 That’s all for us. 19:10:39 Oh, and GeKo: confirming our conclusions in #21431 would be helpful. 19:10:46 (or disagreeing :) 19:10:56 yeah, i'll look at it 19:11:00 thx 19:11:34 mcs: we don't use the maintenance service for updates, right? 19:11:51 https://hg.mozilla.org/releases/mozilla-esr45/rev/0a22becb23cd might be worth looking at 19:11:53 correct, we do not 19:11:58 OK; will do. 19:12:14 i rebased the patch and i did not get any conflicts 19:12:37 so i am optimistic. should be no buig deal but being certain in that regard would be good 19:13:22 We will let you know our opinion after we look at it. 19:14:56 who is next? 19:15:04 * boklm can go next 19:15:20 I fixed a few issues and made some improvements on #17379 following feedback from mcs and Kathy 19:15:34 I worked on #20426, and have been able to reproduce builds for Linux and OSX. On the Windows bundle there is still a small diff in tor.exe that I have not yet been able to fix. 19:15:58 This week I'm planning to fix some issues on #17379 in the OSX and Windows builds, try to make the Windows build reproducible, and try to integrate FPCentral in our testsuite. 19:16:08 That's it for me. 19:17:46 boklm: there is still the settings test that is failing 19:17:53 could you please fix that one 19:18:01 ok, I will fix that 19:18:12 iirc it is just getting rid of the fonts related prefd 19:18:15 *prefs 19:20:21 * arthuredelstein can go 19:20:29 Since last time I posted patches for #21308, #21309, #20959. 19:20:57 Argh, that's the wrong one. 19:20:59 #20905 19:21:32 I opened #21394 and investigated it a little. 19:21:48 I met with the Mozilla uplift team (week before last) and helped to prioritize anti-fingerprinting tickets. 19:21:57 I met with the Mozilla uplift team (week before last) and helped to prioritize anti-fingerprinting tickets. 19:22:03 I also opened #21448 but it turns out I was wholly ignorant about our build flags so I will update that ticket with what I have learned from GeKo and boklm. :P 19:22:14 I also started working on #21340 and I have a patch for #20905 that I think I can post soon. 19:23:17 This week I will continue to work on #20680 and children. 19:23:30 That's it for me. 19:24:11 arthuredelstein: sounds good. could you have a look at #21514. iirc you rebased the patches back then and might be most familiar with it 19:25:07 sure, will do 19:25:32 thanks 19:25:39 who else is here for the meeting? 19:27:23 alright, dicussion time then i think 19:27:51 one item i have is asking around whether we as a team want to have an encrypted mailing list or not 19:28:07 dgoulet has been working on setting things up and was asking 19:28:37 my current take is that we don't need it right now but if others disagree i am fine with getting one list going 19:29:15 What would the purpose of the list be? Security notification for Tor Browser issues? 19:29:58 (context for net team: we use it to securely communicate between us for little-t tor security issues) 19:31:22 mcs: could be one purpose 19:32:23 I think so far it works okay for us to not have such a list since we can use encrypted email as needed. I guess the list would ensure that everyone is included in discussions. 19:32:51 Maybe we should wait and see how well it works for the network team first. 19:33:08 we could do that, sure 19:33:34 do we have anything else up for discussion? 19:34:54 okay, thanks all then and *baf* 19:34:58 #endmeeting