18:00:18 <GeKo> #startmeeting tor-browser 18:00:18 <MeetBot> Meeting started Mon Aug 8 18:00:18 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:18 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:22 <GeKo> hi all! 18:00:47 <GeKo> i hope we are back on our regulat meeting schedule now and everybody is refreshed due to vacations 18:00:52 <GeKo> *regular 18:00:57 <GeKo> let's get started 18:01:17 <GeKo> my last week was short: i dealt with the releases and it seemed we made it again 18:01:30 <GeKo> thanks to boklm who did most of the work 18:01:59 <GeKo> today i spent triaging a bunch of tickets and folded in issues found with the releases into our monthly ticket plan 18:02:15 <GeKo> i think we are good for august (the tag is TorBrowserTeam201608) 18:02:45 <GeKo> please have a look and prioritize tickets having "SponsorU" on them as well 18:02:56 <GeKo> october is coming fast and we still have a bunch of stuff to do. 18:03:29 <GeKo> this week, i'll take care of the remaining admin things, deal with my backlog and do some post-PETS things. 18:03:54 <GeKo> plus i plan to finally get back to updating the design doc. 18:04:22 <GeKo> i plan to have that one ready for review before 6.0.4 is coming out 18:04:39 <GeKo> i plan to look at the remaining test failiures 18:04:42 <GeKo> that's it for me. 18:05:47 * arthuredelstein can go 18:06:02 <arthuredelstein> Much of the week I was afk, but I did work on #13018 and #13017. Working on including libraries that make AudioContext and Math homogeneous on linux. 18:06:19 <arthuredelstein> Also I reviewed https://bugzilla.mozilla.org/show_bug.cgi?id=1289319 18:06:20 <arthuredelstein> which is the main isolation testing patch that is part of Mozilla's uplift of ur isolation patches. 18:06:28 <arthuredelstein> *our 18:07:20 <arthuredelstein> This week I will also be off for a few days, but then I will try to finish up #13018 and #13017 and look at the window resizing stuff again 18:07:23 <arthuredelstein> That's it for me 18:08:07 * mcs is back and can go 18:08:20 <mcs> As most of you know, Kathy and I were afk last week. 18:08:25 <mcs> We still have a lot of email to catch up on, so that will occupy the first part of this week. 18:08:37 <mcs> Then we will look at the TorBrowserTeam201608 list. 18:08:42 <mcs> That’s all for now. 18:11:14 * boklm can go 18:11:25 <boklm> This past week I published the new releases, and made a patch for #19818 and #19854 18:11:39 <boklm> This week I'm planning to look at tests for #8725 18:11:54 <boklm> weasel also gave me access to a build box (which can be used with https://dsa.debian.org/doc/schroot/) and I'm going to try it to see if we could use that for running our testsuite 18:12:12 <GeKo> sounds good 18:12:15 <boklm> I'm also planning to be mostly afk this thursday and friday, and next week 18:12:33 <boklm> That's it for me 18:13:02 * sukhe can go 18:13:37 <sukhe> last week I mentioned a few issues I was having with the linker search path and then there was #19809 18:13:57 <sukhe> both of these are now fixed and we are now moving to automate the MAR generation process 18:14:24 <mcs> sukhe: I am glad you are making progress; sorry we were not around to help last week. 18:14:57 <sukhe> mcs: np; the good part was that I got more familiar with the code while trying to find the problem :) 18:15:37 <GeKo> can't be wrong, can it? ;) 18:15:40 <sukhe> if there are no more surprises, we are aiming for a public release with the secure updater by the end of this month 18:16:17 <sukhe> I will need boklm's help here especially with update_responses and stuff but I will try to minimize that as much as I can 18:16:28 <sukhe> that's it from me 18:18:25 <GeKo> who else is here for the tor browser meeting? 18:18:30 <mikeperry> I am 18:18:33 <GeKo> aha! 18:18:36 <GeKo> o/ 18:18:58 <mikeperry> I think it may be time to consider trying to get CFC into shape for Tor Browser: https://git.schwanenlied.me/yawning/cfc. Unfortunately, Yawning doesn't have time to do the work to give it a better UI, etc. But we should probably start figuring out what missing pieces are needed before we could include it, file tickets for them, and see if we can get some folks excited about working on it. 18:19:48 <mikeperry> I'm going to start going in to NoiseBridge to try to get people excited about projects like this, so that might be one way to get some momentum behind a better UI and appropriate user warnings about the risks. I will keep folks updated. 18:20:25 <asn> what a mission (no pun intended)! gl! 18:21:47 <GeKo> hm. 18:22:02 <GeKo> so i am a bit torn about that idea 18:22:28 <GeKo> but i guess we are running out of good options 18:22:49 <mikeperry> certainly in the short term, we have very few/no good options 18:22:59 <GeKo> do we have some feedback whether the archive* people can handle that load? 18:23:24 <GeKo> i don't want to burn things over there and get angry mails 18:23:50 <GeKo> (this is my main non-technical concern actually) 18:23:56 <mikeperry> Shari is looking into it. I think the general feeling is that archive.org would be in a better position (and perhaps maybe more trusted?) than archive.is 18:24:45 <GeKo> okay. as long as we are talking to them and they are not caught off-guard i am okay with the general idea i think 18:27:06 <GeKo> i have not looked at cfc yet but i wonder whether it would be better to have it as a module in torbutton itself instead of an own extension. 18:27:31 <GeKo> (just as a general thing about technical desicions) 18:27:54 <GeKo> that would solve taking care about yet another extension and all the things following from that 18:28:17 <GeKo> (like extra updates, exemption from the signing requirement) 18:28:24 <arthuredelstein> I like that idea. Helps keep things in a minimal number of git repos as well. 18:28:32 <GeKo> that, too 18:28:49 <mikeperry> right. probably. I guess it depends on if some volunteer is excited about maintaining it, and what the overhead would be for them to get stuff merged into torbutton. though I think that probably every change should be reviewered 18:29:18 <GeKo> yes. 18:29:31 <mikeperry> so that review piece would argue for it being a part of Torbutton also 18:29:38 <GeKo> yup 18:31:26 <GeKo> mikeperry: feel free to add me to any mail thread if needed and we'll see how it goes i guess 18:31:53 <GeKo> it seems we are already in the discussion phase 18:32:11 <GeKo> do we have something more/something in addition to talk about? 18:32:12 <huseby> mornin 18:32:15 <huseby> sorry i'm late 18:32:20 <GeKo> hi! 18:32:25 <GeKo> but not too late :) 18:32:28 <mikeperry> GeKo: ok 18:33:36 <GeKo> huseby: if you think you have some kind of status update you wanna give, go ahead 18:33:44 <huseby> sure 18:33:55 <huseby> last week was short for me because of bsides and defcon 18:34:00 <huseby> i'm still hung over 18:34:29 <huseby> i did make some progress on https://bgz.la/1260931 18:34:45 <huseby> we're slowing making changes to the initialization of the firstPartyDomain origin attribute 18:35:14 <huseby> most importantly, it's now blocked on fixing the cookie subsystem to use loadInfo instead of loadingContext as the source of truth for origin attrs 18:35:42 <huseby> it looks like change was landed last week: https://bgz.la/1264231 18:35:51 <huseby> so i'm going to move forward on my patch and get it landed ASAP. 18:36:28 <huseby> this week, will be that, plus moving to land tor isolation test patches using the new testing framework arthuredelstein reviewed last week https://bgz.la/1289319 18:36:35 <huseby> that's it for me 18:36:43 <huseby> also... 18:36:54 <huseby> somebody finally noticed: https://news.ycombinator.com/item?id=12240722 18:36:59 <huseby> and https://www.reddit.com/r/privacy/comments/4wkoh9/our_primary_goal_is_to_unfork_the_tor_browser/ 18:37:06 <huseby> i'm ignoring it 18:37:20 <huseby> damn the torpedoes, full speed ahead 18:37:31 * huseby is done 18:38:37 <GeKo> thanks 18:38:54 <GeKo> alright, any other items? discussion points? 18:40:43 <GeKo> thanks for the meeting everybody! *baf* 18:40:46 <GeKo> #endmeeting