17:59:46 #startmeeting tor-browser 17:59:46 Meeting started Mon May 9 17:59:46 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:57 hi everyone and welcome to another tor browser meeting 18:00:13 who wants to go first today? 18:00:22 did i just land on this channel the perfect time to ask if we've updates on disconnect.me? :) 18:00:54 * mrphs goes to the back of the line 18:01:06 there is nothing more than the mail i cc'ed tor-team on 18:01:35 * mcs can go first today 18:01:53 Last week, Kathy and I worked on #18928 and #18947. 18:02:00 We also spent a little more time looking at #18545 issues and filed #18958. 18:02:07 On Thursday and Friday we were mostly away from keyboard. 18:02:13 This week, we plan to work on #18904, #18770, and #18947. 18:02:26 We will also help with code reviews and hopefully take ownership of some other TB 6.0 tickets. 18:02:31 That’s all for us. 18:02:48 what is to be done wrt #18947? 18:03:13 Maybe nothing. We need to decide. 18:03:39 what are the options then? 18:04:18 Document it (release notes). Write code to parse torrc and try to fix paths (ick). Something else ;) 18:04:55 Maybe make the error more obvious to the user (the cause of the error, that is). 18:05:26 i see. something like that and 1) sounds like a good idea 18:05:36 OK. We will take a look. 18:05:39 as a short term thing 18:06:48 * arthuredelstein can go 18:06:55 This week I wrote patches for #18886, #18958, #18980, #18905. 18:07:09 I also have a working patch for #18884, but I am struggling to get rid of a mysterious JavaScript error that appears in the Browser console as a result. 18:07:24 I also reviewed the #18928 patch this morning. 18:07:38 So this week I want to try to finalize my #18884 patch. I'm also thinking about working on #18995, #18601, and #18914. 18:07:48 That's it for me 18:08:52 * GeKo can go 18:09:11 last week was a bit short for me as well as i took off 2 days 18:09:31 in the remaining time i finished the may tor browser team admin stuff 18:09:40 reviewed some patches and wrote one for #18915 18:09:46 i am currently testing it 18:10:21 then i asked for a review for a patch for #17406 which sat in my patch queue for quite a while 18:10:36 i made progress on #18545 but am not done yet 18:11:23 this week i'll finish #18545 and #18915 + plan on doing a bunch of reviews 18:11:37 i hope i'll get to some ff45-esr tickets as well 18:11:41 that's it for me 18:12:47 * boklm can go 18:13:04 This past week I took some days off, I added a Performance Observer API test (#18597), I Reviewed #17406 18:13:08 I also did some cleaning in the testsuite removing support for mozmill and selenium tests 18:13:13 This week I'm planning to work on #18845 and #17325, and start looking at #18867 18:14:01 That's it for me 18:14:14 re #17406 seems your machine runs out of memory somehow? 18:14:17 i'll go 18:14:54 so we're down to 0 bugs in our backlog for platform origin attributes support 18:14:55 GeKo: it seems to be the VM that runs out of memory. Did you increase the memory for the VMs ? 18:15:03 there are some bugs still in flight 18:15:06 but no new ones 18:15:13 boklm: no, works fine for me 18:15:15 we have new tracking pages that are easier to follow 18:15:28 origin attributes/container: https://wiki.mozilla.org/Security/Contextual_Identity_Project/Tracking 18:15:37 the great tor uplift: https://wiki.mozilla.org/Security/Tor_Uplift/Tracking 18:15:59 we're still prioritizing the 1st party isolation tor patches over all others 18:16:23 GeKo: did you build using KVM or LXC? 18:16:28 and will port over the isolation tests from tor to prove that the origin attributes isolation mechanism works as well, or better, than the ThirdPartyUtils way 18:16:42 that's it for me 18:19:19 huseby: cool, thanks. 18:19:29 boklm: i used the lxc machine we have 18:21:26 who else is here for a status update? 18:23:37 do we have topics for discussion? 18:26:06 alright, that was fast today. thanks everybody *baf* 18:26:09 #endmeeting