16:59:45 <nickm> #startmeeting
16:59:45 <MeetBot> Meeting started Mon Jun 13 16:59:45 2016 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:59:45 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:59:52 <nickm> hi all!
16:59:59 <nickm> It's time for another happyfun network team meeting
17:00:07 <nickm> I see so many of my fave people.l
17:00:15 <espress> hi!
17:00:17 <nickm> Yawning is out doing errands, and will be around tomorrow for the patch party
17:00:28 <nickm> I believe teor1 is on antipodean time, and is probably asleep right now.
17:00:42 <nickm> let's start as we usually do, with quick checkins:
17:00:45 <nickm> I'll go first
17:01:10 <nickm> My last week was supposed to go mostly to triage. I spent a lot of time on triage, and a lot of time on non-networkteam stuff -- more than I'd like.
17:01:20 <nickm> I wrote a couple of test coverage patches for the fun of it.
17:01:56 <nickm> my goal for today and tomorrow is to finish the triage-tickets-for-deliverables project that we started with Isa, and make sure that we're actually on target to get everything done, and assign myself June tasks at last.
17:02:01 <athena> hi meeting
17:02:02 <nickm> Then I aim to hack and review and merge.
17:02:03 <nickm> hi athena !
17:02:10 <nickm> and that's about my status right now.
17:02:26 <nickm> #note let's talk about triage status
17:02:29 <nickm> who's next?
17:02:30 <athena> i reviewed a bunch of stuff and wrote patches for #18320 and #15942
17:04:08 <nickm> ok. what's for this week?
17:04:23 <athena> working on #18322 now
17:04:40 <nickm> cool.
17:04:59 <nickm> please remember to keep "actual points" up-to-date as you finish stuff
17:05:07 <nickm> oh, another note from me:
17:05:11 <nickm> review-group-3 is now open.
17:06:11 <nickm> there are 9 needs-review tickets in that group, of which 5 have no assigned reviewer yet!
17:06:36 <nickm> athena: any more?
17:06:40 <nickm> otherwise: who's next? :)
17:06:47 <athena> that's it for now
17:07:28 <dgoulet> hi!
17:07:34 <nickm> hi dgoulet !
17:08:22 <attila> I updated #19374 with what i hope is the right answer, FWIW
17:08:35 <dgoulet> so last week was not very productive for me... sorry about that, I had to take a bit of time off. I did some tor triage for R, a bit of #19024 (not done yet), some relay sybil hunting down and maybe a review or two, I can't remember :S
17:09:11 <dgoulet> I've done this morning #18280, I'm back on some 224 stuff this week and I'm trying to cleanup torsocks ticket this afternoon!
17:09:23 <dgoulet> --
17:09:39 <armadev> my short summary for this week is that i'm wearing my other hats this week and i think the dev hat might have fallen off and be under the bed or something. please keep fighting the good fight for us. :) (i am in seattle this week doing all sorts of org meeting stuff.)
17:10:35 <nickm> dgoulet: quick question: did your #18280_029_02 changes also make the change I called "suggestion 2" ?
17:11:16 <dgoulet> nickm: hrm I did reply to that, was my answer not satisfactory?
17:11:25 <dgoulet> (maybe I failed to understand what you wanted also...)
17:11:29 <nickm> I liked  your answer, but I don't konw whether you made the change. :)
17:11:38 <nickm> you didn't say whether you were doing it or not
17:11:48 <dgoulet> nickm: ah it was like that by design I think since we always zero out the destiation buffer
17:12:19 <nickm> hm, I don't understand, let's talk more after the meeting. :)
17:12:20 <nickm> who's next?
17:12:51 <dgoulet> (FYI, asn said earlier he can't make it to this meeting)
17:13:12 <nickm> Ok. if nobody else to check in, let's move to discussion.
17:13:15 <nickm> topics I have are:
17:13:24 <nickm> - review-group-3 is open, folks should grab some tickets to review.
17:14:00 <nickm> armadev: did you mean to put #11966 in needs_revision?
17:14:11 <nickm> - let's finish triage
17:14:21 <nickm> anything else to discuss atm? anything I can do to be helpful?
17:14:29 <nickm> (or anything others can do to be helpful?)
17:14:54 <armadev> nickm: please do something smart with 11966
17:15:06 <nickm> dgoulet: do we have a "let's try gitlab" writeup anywhere to tell people what to do to put big branches on gitlab and/or review them there?
17:15:11 <dgoulet> nickm: there is something you could be helpful actually. This is an important ticket and somehow stuck: #19162
17:15:33 <armadev> it went into needs-revision and then isis said it didn't need revision and i'm not here enough to do the stubborn "no, really, revise it" thing
17:15:46 <armadev> "needs explanation" maybe
17:16:12 <armadev> and yes, having nickm think about #19162 seems wise
17:16:32 <dgoulet> nickm: re gitlab, nope nothing yet, you want to expand the experiment to more branches? :)
17:16:46 <nickm> dgoulet: I want more people to try it.
17:16:49 <nickm> we should have a writeup
17:16:52 <nickm> explaining how
17:16:58 <nickm> unless you want to teach everybody, one by one
17:17:02 <nickm> it might not be pretty, fwiw
17:17:03 <dgoulet> nickm: I can draft one
17:17:06 <nickm> thanks!
17:17:33 <Sam_> Hello guys, I was redirected to here from #tor
17:17:38 <nickm> adding myself as cc on #19162, though I don't know what to do
17:17:57 <nickm> hi, sam! We're wrapping up a meeting right now, should be done in a couple of minutes.
17:18:02 <nickm> so, on the triage topic?
17:18:08 <nickm> I think that what I'm supposed to do is:
17:18:25 <nickm> - Make sure that 100% of our deliverables have SponsorFoo-must tickets that cover what they should be.
17:18:47 <nickm> - Make sure that 100% of our SponsorFoo-must tickets are really "must" and not just "I thought they were a good idea really strongly"
17:19:01 <Sam_> nickm: ok
17:19:16 <nickm> - For deliverables that have a huge list of SponsorFoo-can tickets, cut that list down to size, as we did for the big pile of DoS issues.
17:19:35 <nickm> (I'm mostly saying this aloud so that isabela can read it later and tell me what I'm missing)
17:20:02 <nickm> - at that point, we'll know around how much work we have and how long we expect it to take, and we can see whether there's time for anything else, and if so what's most important
17:20:17 <nickm> Anybody want to help me improve that process? or do I just wait to see what isabela thinks.
17:20:38 <nickm> dgoulet, armadev : on #19162 ,is the help you want "try to figure out why the 'mystery' is happening?" or something else
17:22:21 <dgoulet> nickm: well yes, why this uptime value is always growing and never "fluctiating" like it should is what we are trying to understand
17:22:23 <armadev> yes, correct. it is totally possible that the time-known thing is actually broken and has been this whole time. anything is on the table.
17:23:31 <nickm> ok, will look
17:23:59 <nickm> dgoulet, armadev : I'd like to quote your last two statements. may I?
17:24:04 <nickm> (any more discussion topics for today?)
17:24:39 <dgoulet> I'm good for now
17:24:42 <dgoulet> nickm: sure
17:25:16 <nickm> ok. assuming armadev is okay with it, since he never minds.
17:25:21 <nickm> thanks, all!
17:25:22 <nickm> #endmeeting