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