18:00:33 #startmeeting tor browser 18:00:33 Meeting started Mon Sep 12 18:00:33 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:40 hi everyone! 18:00:43 hi! 18:00:54 hi! 18:00:57 let's start with the status updates 18:01:04 who wants to go first today? 18:02:16 alright, then i'll start 18:03:13 last week i worked on #13893 (not really successfully), #20118, #19419, #20133 and preparation of the releases 18:03:50 while i was still fighting with the rebase for the alpha (we have some conflicts) mozilla told us that we have another week for the release 18:04:08 it's not clear yet whether we have to rebuild the firefox part 18:04:35 but at least we'll rebundle i guess to get the bundle up-to-date (changelog-wise etc.) 18:04:52 so, this week is another round release preparations on my agenda 18:05:25 oh it was #19417 i meant 18:05:39 * amoghbl1 just walked in 18:06:14 then i want to poke at #13893 again and will help with #20120 18:06:36 i am excited to have an os x user willing to help debugging the problem which is seemingly font related 18:06:59 then i hope to get back at updating the design doc as well 18:07:32 oh, i forgot karsten, boklm and i worked on the tor browser download and update graphs on sunday and posted the result to tor-dev 18:07:43 i guess this is stuff for the discussion part, though 18:07:47 that's it for me 18:08:30 GeKo: Let me know if there is anything you want Kathy and I to do to help track down the OSX crash(es) 18:08:46 * arthuredelstein can go 18:08:47 will do. 18:08:58 my current plan is in my last commit 18:09:04 we'll see how good that works 18:09:10 *comment 18:10:03 Also happy to look at that font thing since it's probably something I did :( 18:10:28 This past week, 18:10:30 I wrote patches for #17334 and #17767 18:10:35 did some investigation of #18093 and #16211, 18:10:44 reviewed #14271, 18:10:53 worked more on (but did not entirely solve) #19459 18:10:59 and starting working on #16622. 18:11:03 I also had a meeting with the Mozilla uplift team 18:11:08 I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1301523 18:11:12 and reviewed https://bugzilla.mozilla.org/show_bug.cgi?id=1264573 18:11:29 (The last two are HTTP auth isolation and testing blob URL isolation, respectively.) 18:12:14 This week I will keep working on SponsorU stuff. I can have a look at #20121 if no one else wants to. 18:12:36 that would be neat 18:13:15 * mcs can also help with #20121 18:13:33 (I have not looked at it and have no seatbelt experience though) 18:13:56 Nor have I! 18:14:11 Well, a team effort might be in order. 18:14:27 sounds like a good idea to me 18:14:32 Sounds good 18:15:21 That's it for me 18:16:10 * huseby can go 18:16:29 progress is being made on the first party isolation uplift/refactor to origin attributes 18:16:43 the testing framework is in place and the isolation tests from TBB are being moved over right now 18:16:59 the origin attribute for isolation is in place and all but just a few subsystems are honoring it now 18:17:21 we're still targeting Nov 7th for first party isolation to be all in and passing tests 18:17:54 also, work on the unix domain socket support in the proxy framework is moving along 18:18:02 that too is also targeted for 11/7 18:18:27 all of the mozilla people are booked for being at the dev meeting in seattle 18:18:31 we'll see all of you there 18:18:34 that's it for me 18:19:16 Does the proxy framework effort include Windows or not yet? 18:19:41 (as in, Windows will not be ready by 11/7 or will it?) 18:22:04 * mcs will give a report while huseby ponders the Windows question 18:22:05 who is next? 18:22:10 Kathy and I missed last week’s meeting. 18:22:12 ah :) 18:22:15 In the past two weeks, we mainly worked on Unix domain socket tickets (#14270 and child tickets). 18:22:24 We fixed #20040 and created a fixup patch for #15852. 18:22:31 We also reviewed some patches. 18:22:36 This week we will review more patches, work on #20111, and maybe start to help with #20121 as well. 18:22:41 That’s all for now. 18:23:52 yeah, we have got another week. so, maybe at least #20111 can make it into the alpha, too. 18:23:58 would be neat i guess 18:24:10 agreed 18:25:27 who is next? 18:25:36 * boklm can go next 18:25:52 This past week I help build the new release (now delayed by a week), helped release Tor Messenger, updated patches for #19528 and #19410 18:25:57 This week I'm planning to get the testsuite run on the new releases, look at the signing process and sign the new releases, and work on #19067 18:26:03 That's it for me 18:28:19 alright. i saw amoghbl1 stumbled in. 18:28:30 anything to report from your side, amoghbl1? 18:28:59 Yup! Nothing to report yet, just thought I should be here to announce that I'm starting with the contract! 18:29:09 yay! 18:29:32 so, to give some context: amogh is working on porting the security slider to mobile 18:29:53 that's part of a small grant we got from ISC 18:30:39 https://trac.torproject.org/projects/tor/wiki/org/teams/ApplicationsTeam/TorBrowserAndroid/Roadmap is outlining the project 18:30:48 cool! 18:31:27 So I'm going to attend these meets regularly and keep you guys updated! 18:32:04 And thats all from me :) 18:32:09 I'm here as well, but don't have anything to report. :) 18:32:46 o/ 18:33:11 oh, that reminds me that i want to try backporting jemalloc 4.2.1 to the esr45 branch this week 18:33:28 and see what the testsuite is saying 18:33:59 it might help for our memory allocator hardening we promised 18:34:13 cool! 18:34:42 okay, it seems we are on our way into the discussion part 18:35:29 do we have items we want to talk about? 18:35:44 i have just the download/update graphs i sent to tor-dev 18:35:46 https://lists.torproject.org/pipermail/tor-dev/2016-September/011378.html 18:36:23 dcf had a nice theory although i am not convinced by it 18:37:00 The update ping numbers seem to be generally going down, right? 18:37:25 yes, for some reason after (8) and (9) 18:37:43 and (9) starts before 6.0 came out 18:38:06 at least i'd think so 18:38:37 It might be interesting to look at whether we have a lot of people stuck on old versions. 18:38:54 (but I don’t think that will explain the (8) and (9) events) 18:39:05 i agree 18:39:51 anyway, this is something to mull over i guess and i just wanted to point folks to it 18:40:02 do we have anything else? 18:41:28 alright, thanks for attending the meeting everybody *baf* 18:41:31 #endmeeting