18:00:20 #startmeeting tor browser 18:00:20 Meeting started Mon May 22 18:00:20 2017 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:23 monday == never end meetings days 18:00:35 yeah 18:00:38 hi all! 18:00:42 hi! 18:00:54 welcome to another round of the monday tor browser meeting 18:01:04 hi 18:01:11 hi! 18:01:16 who wants to go first today? 18:02:03 I can go. 18:02:11 Last week, Kathy and I responded in #22232. 18:02:17 We also worked some more on #21766 and created a revised patch. 18:02:24 And we investigated #22283 and discussed with GeKo how to proceed. 18:02:31 Also, we triaged #22298. 18:02:36 As I mentioned last week, due to other commitments, Kathy and I will be in and out of the office this week (so we will be less available). 18:02:41 We do plan to look at FTP downloads for #21766. 18:02:47 We will also create a patch for #22283 and help with code reviews. 18:02:52 Time permitting, we will look at other tbb-7.0-must tickets, probably starting with #21431. 18:03:02 That’s all for now. 18:04:10 mcs: do you know whether the fix for #21779 works? 18:04:19 i was a bit unsure how to test it tbh 18:04:33 as my old mac can't run esr52 18:04:57 Kathy and I will test it with 7.0a4 bits. 18:05:18 just to be safe i added the chmod change to the script that is regenerating the dmg's after signing 18:05:19 (bascially, install as an admin and then try to use from a non-admin account) 18:05:27 OK 18:05:51 so, if that does not work we need to look a bit deeper i guess. we'll see. 18:05:56 wh ois next? 18:06:00 *who is 18:06:51 * boklm can go 18:06:51 i gues i can go 18:06:56 go boklm! 18:07:11 This past week I published the new alpha, fixed #22194 and #22267, signed a tor-messenger release, and sent an email to linus to help with setup of rbm nightlies 18:07:28 This week I'm planning to work on #21982, try to help tjr with https://bugzilla.mozilla.org/1365047, and get back to the panopticlick setup 18:07:35 I'm also planning to be afk on thursday and friday. 18:07:41 That's it for me. 18:08:29 boklm: while looking at the test suite it might be good to have the osx one going as well 18:08:42 at least to check whether there is still PIE support etc. 18:08:45 yes, I will do that 18:09:03 i was actually wondering whether we could rip out our pie hack and do the right thing now in esr52 18:09:16 as the build system for libffi changed 18:09:24 might be worth testing if you have time for that 18:09:30 ah, yes 18:09:58 okay, here is my report 18:10:14 i was distracted by pre-SIF SIF and post-SIF stuff 18:10:56 it was a good experience and i think it was important that tor folks were there 18:11:20 i worked on #22320, #22324 and #16285 18:11:40 moreover i started with webgl2 review #16404 18:11:53 it seems there is plenty of new fingerprinting potential 18:12:29 so i'll probably argue for flipping the pref for now and work on normalizing stuff during the 7.5 alpha cycle 18:12:35 if we want to enable it 18:13:10 GeKo: Is a recording of your SIF talk online anywhere? 18:13:10 this week i'll focus on review and as many tickets tagged with tbb-7.0-must as possible 18:13:39 mcs: dunno, i think it was only streamed live? 18:13:48 OK. thx 18:14:03 that's it for me 18:14:10 * arthuredelstein can go 18:14:27 This week I worked on investigating and testing #21766, 18:14:37 I worked on #21762 18:14:55 and I opened a spinoff, #22327, and wrote a patch for it. 18:15:07 I met with the Tor uplift team 18:15:18 and I helped with reviewing https://bugzilla.mozilla.org/1333933 and more discussions are ongoing 18:15:28 This week as usual I will keep working on tbb-7.0-must tickets. 18:15:46 That's it for me. 18:16:03 #22324 ight interest you as the firefox patch is wrong it seems 18:16:06 *might 18:16:40 i think for now using the proper pref is okay for us 18:17:01 but i guess pege's idea is the better fix for upstream 18:18:03 who else is here for a status update? 18:18:24 tjr: are you with us today? 18:18:32 I am 18:18:44 But I don't have anything to report beyond working a little bit on more mingw patches 18:18:54 And commenting on a few bugs 18:18:55 GeKo: Sorry, what's the firefox patch for #22324? 18:19:37 tjr: i was wondering whether we could get 1331335 into esr52? 18:20:01 would mean one patch less for us and fixing build things on an esr series seems worthwhile to me 18:20:30 I'll file an uplift request 18:20:39 arthuredelstein: ah, sorry i meant #22320 18:20:47 tjr: thanks 18:21:23 discussion time i guess? 18:21:42 GeKo: Got it, thanks. I will look into it. 18:21:56 i only have one item on my list: mozilla does not move to jemalloc4 18:22:17 we might want to think about what that means for our memory allocator hardening ideas 18:22:44 Are they dropping jemalloc? 18:22:44 i guess we can keep what we have for now in the alpha series 18:23:11 no. just not moving to jemalloc4 18:23:28 Well, we are dropping jemalloc. But we're keeping mozjemalloc 18:23:40 Which is such an old fork and divergence from jemalloc it's not really worth calling jemalloc 18:23:53 yeah, that's what i meant 18:24:20 got it. thanks 18:24:47 arthuredelstein: https://groups.google.com/forum/?_escaped_fragment_=topic/mozilla.dev.platform/S8WA3oHB7mM#!topic/mozilla.dev.platform/S8WA3oHB7mM 18:24:54 for the arguments 18:25:01 thanks! 18:25:56 do we have other items worth talking about today? 18:26:15 I thought it might be useful to discuss our remaining tbb-7.0-must bugs 18:26:30 Here are the Priority High ones left: https://trac.torproject.org/projects/tor/query?priority=%5EHigh&owner=~tbb-team&status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~tbb-7.0-must&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&order=priority 18:26:37 (that aren't assigned) 18:27:01 Does anyone want to claim any of these? Should I work on them? 18:27:24 I can take #21341 (since I keep saying that Kathy and I plan to work on it) 18:27:33 ummm #21431 18:28:35 arthuredelstein: going over the list #22070 seems worthwhile 18:28:49 OK, cool. I guess the rest of the High priority ones up for grabs as we get to them :) 18:29:04 i think so 18:29:35 once anybody starts working on a ticket, first assign it to yourself 18:29:38 GeKo: Yes, I can look at #22070 a bit. I'm not aware of anything urgent but there is always room for improvement. 18:30:20 well, if we are fine and there are no font related surprises we can improve after the 7.0 release i guess 18:30:57 Yeah. I mean, there are definitely UX improvements to be had, but nothing for fingerprinting. 18:31:02 that I know of 18:31:21 okay. 18:33:35 anything else for today? 18:34:11 What is our code feeeze date for 7.0? Week of June 5? 18:34:48 Oh, and one week from today is the U.S. Memorial Day holiday 18:35:14 good point 18:35:22 let's have a meeting next tuesday then? 18:35:43 Tuesday works for us 18:35:47 then we can discuss code freeze and release date for 7.0 18:37:23 my current thinking is that we should aim for getting 7.0 out end of next week/early in the week thereafter 18:38:34 arthuredelstein: boklm: would tuesday next week work for the meeting for you as well? 18:38:45 if so, i'll send an email to tbb-dev later today 18:38:48 works for me 18:38:51 hmm, next tuesday might not work for me 18:39:34 hm. 18:40:05 wednesday seems a bit late. 18:40:55 boklm: are you around during the day or monday? 18:41:14 yes 18:41:38 okay. then let's sync then if needed and do the meeting on tuesday 18:41:39 actually I can probably make it on tuesday at the same time as today, but with a slow/unreliable connection 18:42:05 even better. i don't ant to have a meeting on holidays if we can avoid it 18:42:14 tuesday it is then, thanks 18:42:33 i guess that's it for today. thanks for coming all. *baf* 18:42:36 #endmeeting