19:00:13 #startmeeting tbb-dev 19:00:13 Meeting started Mon Nov 2 19:00:13 2015 UTC. The chair is mikeperry. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:27 ok, hopefully the timezone changes haven't tripped anybody up 19:01:50 I spent nearly all of last week setting up a secure signing machine for #6540. the rest of my time was spent on ED search planning 19:02:26 this week, I'm going to try to finally get my apple developer account set up, and from there it should be just a couple of clicks to get a cert (I hope). everything else is ready, AFAIK 19:02:53 I will also be doing a bunch of ED interviews though, and writing our October status and perhaps year-end reports 19:03:32 tomorrow is a release, which I am entirely unprepared for. my build machine went down while I was travelling, and I still have not repaired it yet :/ 19:03:43 I hope that is going OK without me 19:03:48 we should be in good shape 19:04:02 aha, it is back up. I can at least try to match the build and publish a sig 19:04:46 great. thanks so much for carrying that. it looks like you also moved most of the tags over. I'm guessing you were thinking of just deferring the stuff still in https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~TorBrowserTeam201510 till later? 19:05:03 yes 19:05:35 sounds good. I'm done for now then 19:07:05 okay, before i start with the usualy stuff, thanks for everybody keeping us on track during the last days 19:07:10 *usual 19:07:10 GeKo: oh also hipefully you gt an apple developer account, too 19:07:15 hopefully also 19:07:37 i got the mail but fear what is coming after clicking the link 19:08:12 we managed to get a lot of stuff squeezed into the alpha 19:08:18 yeah, it's a lot of forms demanding personal info (though most sensitive seemed to just be mailing address, which I suppose we can use the Tor office for if you are uncomfortable with giving a personal address) 19:08:30 we got the hardened builds going 19:08:35 mikeperry: i am indeed 19:09:08 this week we need to get all the releases out to our users 19:09:32 i guess i'll write a more verbose blog post for the hardened builds 19:10:13 if there remains time i want finally start working on #15578 19:10:36 recently support for debian vms got merged into gitian-builder 19:10:51 which seems the hard work got already done 19:11:04 that's it for me 19:12:14 I wonder if that plugin will allow debian/oldstable guests 19:12:43 we'll see 19:12:53 if not i hope it is not hard to patch 19:14:38 is anyone else awake, or did the timezone change throw everyone off? :) 19:15:09 * boklm is here 19:15:20 * boklm can go next 19:15:44 * Phoul1 is awake 19:16:01 This past week I helped with the release of tor messenger, I reproduced builds of tor browser (and currently building 5.0.4-build5), made a patch for #17511 19:16:12 This week I'm planning to check why the testsuite is not working with the hardened build, rebase the split branch repo on 38.4 and push it to Try. 19:16:36 That's it for me 19:17:23 is there any reason why the tests for the alpha did not run? 19:18:26 yes, there was a problem caused by the parsing of the -hardened git tag, it should be fixed now 19:18:46 the tests for the alpha are currently running 19:19:06 * isis is lurking 19:19:28 * arthuredelstein can go 19:19:35 Last week I fixed up #17207, 19:19:40 reviewed #16620, 19:19:45 investigated #17313, 19:19:51 and posted #17446 and #17421. 19:20:14 Hm, #17421 is wrong 19:20:31 Anyhow 19:20:36 I worked on pushing forward bugzil.la/1217295, bugzil.la/1217290, and bugzil.la/1216882. 19:20:43 bugzil.la/1217985 (#16906) landed and I submitted our patch to bugzil.la/1121643 for review (which is #13313). 19:21:04 This week I hope to submit our remaining fingerprinting patches for Mozilla review. At least bugzil.la/867501 and bugzil.la/1217238, and possibly bugzil.la/1041818 19:21:07 and I'll try to keep any other bugs awaiting review alive. 19:21:17 That's it for me. 19:22:06 Shoud be #17431 19:23:01 yeah, i read the paper back then and contacted the author i should follow-up on this 19:23:28 I can go: 19:24:17 The support team is functional again, and are answering tickets. We have new volunteers working on things, so there is some learning time here still. Will be back to publishing help-desk stats monthly at the end of November. 19:24:48 cool! 19:24:50 Awesome! :) 19:26:08 Also, went through Transifex teams and added a couple new ones for languages we didnt have. I dont have the exact languages infront of me currently though. If anyone is curious, I can send a list later. 19:26:15 (thats all from me for applications) 19:27:08 Phoul1: yeah, thanks a lot for that! 19:27:51 Phoul1: oh, you might want to join the real applications team meeting tomorrow as well: 19:00 UTC in #tor-project ;) 19:28:01 being here is fine though, ofc 19:28:25 Eep, hopefully I didnt just trample a different meeting. Sorry if I did >.< 19:28:34 will be here for that :) 19:28:43 no, no, it's the regular tor browser meeting 19:29:03 * huseby can go next if nobody else is going 19:30:06 I spent last week working on bgz.la/1197283 bgz.la/1218479 and bgz.la/1218803 19:30:23 those are the "hook up contextual identities" bugs 19:30:45 once those are working, then i'll be doing bgz.la/962326 19:31:09 which is the ThirdPartyUtil API using origin attributes; which contextual identities is a part of 19:31:16 that's how it all fits together 19:31:41 i also hosted the Mozilla+EFF+Tor lunch last wednesday and it was great. we had two lightning talks for the first time 19:32:05 the next one will be in January and I plan on expanding it to include browser peeps from google/apple/microsoft too 19:32:35 I was then pre-occupied with my meetings at the mountainview office to discuss how mozilla and tor can better work together going forward 19:32:40 * GeKo cross the fingers that these patches make it into esr45 19:32:47 *crosses 19:32:48 mostly proposals on engineering collaboration 19:32:58 GeKo: we're trying as hard as possible 19:33:05 December 14th is the deadline 19:33:08 yeah 19:33:14 if we're not in review by thanksgiving, it probably won't happen 19:34:06 so this week, that's what I'm doing 19:34:15 origin attributes work as hard as possible 19:34:23 I'm happy to help work on rebasing isolation bugs for review, but we have to get bgz.la/962326 working first. 19:34:24 but wednesday i leave for London for MozFest 19:34:31 I'll be there all weekend, so that will cut into my time 19:34:36 that's it for me 19:35:11 arthuredelstein: cool! agreed. 19:35:24 once origin attributes is solid, we can do the TPU API 19:35:57 Is there any sense in just submitting the existing TPU, and then rewriting it with origin attributes when we have time? 19:36:03 So the other isolation patches aren't blocked? 19:37:10 arthuredelstein: that's a definite possibility 19:37:18 I *could* just work on landing it as-is 19:37:29 I'll bring that up with sworkman later today 19:38:01 Cool 19:42:38 ok, so how are we handling the hardened builds in terms of release process, updater, etc? 19:44:09 will we have a new update channel, or will we be updating all of our alpha users? 19:44:25 or just sending standalone builds to tor-qa for now? 19:44:50 an own hardened update channel 19:46:10 ok, is that ready? are we doing that for tomorrow? 19:46:24 i think this is ready 19:46:25 and what should I help with. I got my build machine back up 19:46:49 and doing that on wednesday seems fine to me after all the builds that need to get out are out 19:47:31 ah yes, ok, that makes sense 19:47:46 if you could give the build i sent to tor-qa a close test that would be helpful 19:48:43 ok, I can try that this afternoon. in the meantime, which build should I start now? stable? 19:49:04 sounds good 19:50:39 mikeperry: especially looking at the memory consumption would be helpful. i still think there is something wrong with that 19:53:43 ok 19:55:48 I started the stable build. anything else for today? 19:57:42 not from me. 20:02:31 ok great! 20:02:51 thanks everyone. great work! 20:02:56 #endmeeting *baf*