18:00:10 <GeKo> #startmeeting tor-browser
18:00:10 <MeetBot> Meeting started Mon May 16 18:00:10 2016 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:10 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:00:23 <GeKo> hey! welcome to a new tor browser meeting
18:00:33 <GeKo> let's start with the status updates
18:00:49 <GeKo> who is here and wants to go first?
18:01:33 * mcs can go first this time
18:01:46 <mcs> Last week, Kathy and I worked on #19014 (triage), #18904, #18770, and #18947.
18:01:58 <mcs> We also reviewed some patches.
18:02:03 <mcs> This week we plan to work on #18947 and then pick up other TB 6.0 tickets.
18:02:10 <mcs> (we already spent a little time on #18855 today)
18:02:16 <mcs> We will also help with code reviews and whatever else comes up.
18:02:22 <mcs> That’s all for us.
18:03:15 <GeKo> what is left for #18947 (given that it already is in needs_review)?
18:04:27 <mcs> Not much I think.
18:04:54 <GeKo> ok.
18:05:25 <mcs> I guess we should divide up the remaining tickets at some point (as a team).
18:05:35 <mcs> (or decide we do not have time for some of them)
18:06:28 <GeKo> yes. we can do that later after the status updates
18:08:00 <GeKo> here is what i did:
18:08:30 <GeKo> i spent quite some time on #18545 but it is done now
18:09:03 <GeKo> one thing we should look closer at is #19047
18:09:13 <GeKo> but apart from that we are good
18:09:22 <GeKo> i reviewed a bunch of tickets
18:10:18 <GeKo> i investigated a build bustage on mozilla-central due to GCC's ASan and am planning to write a patch for that
18:10:33 <GeKo> (i found that while investigating that stack buffer overflow)
18:11:05 <GeKo> we got selfrando in our hardened nightlies goins #17406
18:11:43 <GeKo> looking at this week i already grabbed some tickets i plan to work on
18:11:59 <GeKo> additionally i'll take a final look at #18546
18:12:17 <GeKo> and plan to review a bunch of patches (hopefully)
18:12:21 <GeKo> that's it for now
18:12:58 * arthuredelstein can go
18:13:08 <arthuredelstein> This week I worked on #18886, #18743, #18619, #18958, #18601, #18995.
18:13:34 <arthuredelstein> I also reviewed #18770 and opened #19004 and #19037.
18:13:53 <arthuredelstein> This following week I will work on more ff45-esr tickets, including #18884 and #18811.
18:14:16 <arthuredelstein> If there's any time I may look at a couple of patches for upstreaming
18:14:22 <arthuredelstein> That's it for me
18:15:44 <GeKo> sounds good.
18:15:51 * boklm can go
18:16:08 <boklm> This past week I fixed #19039 and #17325, and added a patch for #18845
18:16:16 <boklm> This week I'm planning to work on #19067
18:16:33 <boklm> That's it for me
18:19:22 <GeKo> who else is here for some status update?
18:20:32 <Yawning> (have a question, but not a status update)
18:21:07 <GeKo> seems we have none more, yawning, so go for it
18:21:55 <Yawning> dcf has a go 1.6 patch for the build process
18:22:00 <Yawning> is that going to get merged anytime soon?
18:22:09 <Yawning> need it for basket2 deployment
18:22:31 <GeKo> it won't get into 6.0 as dcf said it is fine
18:22:59 <mikeperry> I am here
18:23:13 <mikeperry> I will be sending a mail about sandboxing options today/tomorrow
18:23:16 <Yawning> basket2 still isn't deployment ready so that's probably ok
18:23:30 <GeKo> Yawning: thus, as soon as 6.0 is getting out (end of next week) that patch lands on master
18:23:38 <Yawning> ok
18:23:52 <Yawning> I expect basket2 deployment to be dead straightforward
18:23:54 <mikeperry> I have all the sandboxing tech reviewed (I think), just need to write up how we would use it in a coherent form
18:23:57 <Yawning> since building go is well established
18:24:19 <mikeperry> I will Cc the tor browser team, yawning, nickm, and tjr
18:24:20 <GeKo> yeah, will be a nice feature for 6.5 i guess
18:24:22 <Yawning> but fighting gitian always ends up taking longer than it should for me so wanted to get started on it early
18:24:41 <Yawning> basket2 has an anti-wf defense as an option
18:24:53 <Yawning> but it is really expensive, so I do not know if many bridges will offer it
18:25:16 <GeKo> should be fine testing it out in the next alpha series at least
18:25:50 <Yawning> yah
18:26:10 <mcs> Will basket2 eventually replace obfs4?
18:26:22 <mcs> Or is it just another option?
18:26:27 <GeKo> mikeperry: neat. could you spend some cycles replying to isabela's mail wrt the sandboxing stuff. you probably know best now what to suggest
18:26:49 <Yawning> mcs: it will replace it
18:27:12 <Yawning> it fixes some broken in obfs4 that I can't without a new protocol/breaking wire compatibility
18:27:16 <GeKo> mikeperry: it's aboubt the year2 deliverables
18:27:23 <mcs> Yawning: OK. From a marketing point of view, obfs5 might be a better name (but it is your project ;)
18:27:35 <Yawning> I'm not attached to the name
18:28:15 <mikeperry> GeKo: yes, that is what this mail will be about
18:28:38 <mikeperry> GeKo: so yeah, will reply or start a new thread. and also cc isabela.
18:29:24 <Yawning> but it's closer to basket1 in design than obfs4 >.>
18:29:36 <GeKo> mikeperry: ah, okay. that mail sounded like a much bigger thing not fitting in the space that mozilla's e10s delay left
18:29:54 <GeKo> thus, i thought you need to break it down a bit for the remaining time of the contract
18:30:08 <GeKo> leaving other stuff for a next one
18:30:49 <mikeperry> yeah, the main question of the mail will be "can we do windows by the end of the current contract", but it will have technical details about what we would do there
18:31:23 <mikeperry> and hopefully between yawning, nickm, and pearl crescent and arthuredelstein we can all decide if we want to try that windows stuff in this contract, or wait
18:31:53 <GeKo> okay, sounds good.
18:33:48 <GeKo> so, do we have something to discuss?
18:34:21 <GeKo> i guess we can look at the tickets and make some decision on what to prioritize and what not right now
18:34:50 <GeKo> looking at the ff45-esr ones that have tbb-team as assignee and are not in needs_review:
18:35:05 <GeKo> #18855 is good
18:36:30 <GeKo> #16221, #16443 and #18291 can wait
18:36:55 <GeKo> #18914 is a bit risky but would be good for the next alpha
18:37:14 <GeKo> #18945 is good to have
18:37:26 <GeKo> #19047, too
18:38:29 <GeKo> #18860, #18946 and #18996 are not a requirement i think
18:39:35 <GeKo> if anyone needs more work to do #18885 and #19047 and #18945 are the tickets
18:39:58 <GeKo> err #18855
18:40:15 <GeKo> i guess this is enough for everybody until next monday
18:40:28 <GeKo> if not feel free to choose other esr45 tickets
18:40:51 <GeKo> arthuredelstein: i think upstreaming can wait a bit until we start building 6.0
18:41:17 <GeKo> which should probably be wednesday next week (latest)
18:41:34 <mcs> Kathy and I can finish #18855 and take care of #18945 as well. After that, if no one else takes it, we will look at #19047.
18:41:46 <GeKo> does that make sense to everybody?
18:41:47 <arthuredelstein> GeKo: Yes, I think that makes sense
18:41:56 <GeKo> mcs: sounds good to me.
18:42:24 <GeKo> looking at the remainin things i am quite optimistic we get all the things in we want. nice.
18:42:29 <GeKo> *remaining
18:42:43 <GeKo> do we have anything else for dicsussion?
18:45:19 <mcs> Are you planning to remove the ff45-esr keyword from the tickets we are not planning top fix right now or lesve it for now?
18:45:35 <mcs> “to fix"
18:46:19 <GeKo> i think i leave it for now as these are technically things we could/should work on if we have time
18:46:34 <GeKo> i can create a new one making the distinction more clear
18:46:40 <GeKo> like tbb-6.0-must
18:46:41 <mcs> Sounds good to me.
18:46:59 <GeKo> you mean creating a new one for 6.0 must things?
18:47:23 <mcs> I meant leaving it for now but I also like the idea of a “must” keyword too.
18:47:43 <mcs> (we we are less likely to miss something)
18:47:44 <GeKo> okay. i'll do that after the meeting reflecting things we said.
18:47:47 <mcs> OK
18:47:49 <mcs> Thanks
18:48:07 <GeKo> i guess this wraps it up. thanks everybody *baf*
18:48:10 <GeKo> #endmeeting