17:00:52 <nickm> #startmeeting weekly network team meeting!
17:00:52 <MeetBot> Meeting started Mon Jun 20 17:00:52 2016 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:52 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:01:08 <nickm> my lunch is still cooking, but I am glad to see so many folks!
17:01:51 <nickm> hello atagar dgoulet Yawning armadev isis athena asn  and more!
17:01:58 <nickm> who would like to do the first status report? :)
17:02:36 <asn> i'll do the third one
17:02:48 <nickm> ok ok ok
17:03:03 <nickm> so, I've been more or less frazzled, but I got some code written and code reviewed and stuff merged last week
17:03:17 <nickm> mostly I've been using my free time to improve coverage in src/common here and there, and to answer emails.
17:03:43 <nickm> I had a great sponsorU/sponsorS meeting with athena/yawning where we came up with some thoughts on how to make sure that both of those get completed
17:04:32 <nickm> I'll post a link to our pad once I find it
17:04:43 <nickm> more triage work is left, but we have more a plan than we did before.
17:04:50 <isabela> :)
17:04:52 <isabela> awesome
17:05:06 <nickm> This week I aim to do #19468 , and make some progress on #15055, and review the prop250 stuff again, and do a lot of review.
17:05:11 <nickm> and that's me
17:05:19 <Yawning> hurrrr
17:05:32 <nickm> (I'll still be working on coverage whenever i feel too daft for other stuff)
17:05:46 <nickm> src/common coverage is over 80% for me now...
17:06:05 <nickm> and that pad link is: https://pad.riseup.net/p/M0RbDow6NQm9
17:06:12 <asn> i can go next even if that's not third.
17:06:12 <nickm> next person can go!
17:06:23 <asn> ok i go
17:06:26 <asn> Hello. Past week I've been doing prop224 specwork
17:06:27 <asn> (https://lists.torproject.org/pipermail/tor-dev/2016-June/011059.html). There
17:06:30 <asn> has also been plenty of bug bounty activity on hackerone. Also helped with some
17:06:31 <asn> SponsorU bug triaging. Some prop250 debugging. Did some patches and reviews for
17:06:34 <asn> misc tickets. Next week I anticipate to do more prop224/prop250, more reviews
17:06:35 <asn> and more guards (as nick revises prop259). That's that!
17:06:56 <asn> (also 40 degrees celcius)
17:07:01 <isabela> !
17:07:17 <nickm> are you in a fire?  you should get out of the fire.
17:07:28 <nickm> ;)
17:07:33 <asn> :P
17:07:55 <asn> next plz
17:08:26 <dgoulet> Most of my work last week was on reviewing tickets, making patch for 029 tickets and some prop224 work (specifically #19024) for which I think I'm done but I'll need external comment on how it was done.
17:09:05 <asn> dgoulet: ack. let me know when it's ready to be seen and I will review.
17:09:08 <dgoulet> this week I plan to catch up on code for 029 specifically prop224
17:09:20 <dgoulet> asn: I just pushed the latest so looking at the top commit would help me :)
17:09:23 <dgoulet> --
17:09:53 <isabela> last week i was in seattle working on a bunch of things with sue armadev and shari... now i am in detroit but on my way back to california.. i predict a lot of drl work this week and some follow ups from last week -- will try to do a summary of the state of 029 for y'all by EOM #fingerscrossed
17:11:20 <Yawning> oiokkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk
17:11:32 <Yawning> my cat has contributed to the meeting
17:11:34 <isabela> (wonders if that is the cat update)
17:11:47 <isis> hello
17:11:55 <nickm> hi isis!
17:12:09 <isis> nickm: hey :)
17:12:11 <isis> hello, Yawnings cat!
17:12:19 <Yawning> I am stuck in a mountain of ducmentation, all alike
17:12:32 <Yawning> my plans for the week are, write more documentation
17:13:08 <Yawning> and to catch up on paperwork
17:14:26 <Yawning> the cat's plan is "wtf, I haz less teeth now, come up with an alternative 'bite yawning' solution"
17:14:45 <isis> i am mostly here to catch up and listen, since my past two stressful weeks have seen nearly no real work done (all lawyers, journalists, and organisational work)
17:15:05 <isabela> <3
17:15:15 <athena> i finished #18322 and reviewed #16801 and #19361
17:16:42 <nickm> isis: if you're conversant with the guard / prop#259 stuff, you might like to check out the backlog of the meeting we had right before this one.  I'm planning to revise that proposal this week
17:17:23 <nickm> athena: cool! what's up for this week?
17:18:07 <isis> nickm: sound like it could be fun, ;) reading it now
17:18:35 <athena> #18640 next i think, and round 2 of #18320
17:18:48 <nickm> cool
17:19:05 <nickm> anybody else with an update today?
17:21:20 <nickm> ok. my two main discussion topics are : looking at code review again, finishing the S/U triage, and 0.2.8 stable.
17:21:32 <nickm> (oh. that was another thing I did last week. 0.2.8-rc)
17:21:42 <nickm> any other discussion topics?
17:22:39 <nickm> ok.
17:22:47 <nickm> code-review-wise, review-group-3 is almost done.
17:23:10 <nickm> we have 4 items in needs_review there. the rest are a pending merge_ready, and a bunch of needs_revision
17:23:26 <nickm> among the needs-review, we have me reviewing and talking to athena about #15942
17:23:38 <nickm> I've got to review #16943 again
17:23:54 <nickm> #17799 is in limbo ; we should talk about that, maybe
17:24:03 <nickm> and #13081 I guess I should take :/
17:24:19 <nickm> (unless somebody else wants to take it)
17:25:04 <dgoulet> anyone with VS here? :)
17:25:15 <isabela> (is so windy where i am that the wind is pushing my laptop)
17:25:31 <nickm> isis: whoa
17:25:39 <nickm> err
17:25:42 <nickm> isabela: whoa
17:25:51 <asn> nickm: hmm, what else could we do to make us more confident on the RNG branch?
17:25:56 <nickm> dgoulet: I would have to download a copy, or just trust that the patches wouldn't make anything worse.
17:26:05 <nickm> asn: first, any kind of consensus that it's actually a good idea to pursue this idea
17:26:13 <nickm> asn: after that, one last review
17:26:16 <nickm> IMO
17:26:19 <isis> heh, i could start spelling my name in all-caps to avoid collision :)
17:26:46 <asn> that would be like you are shouting!
17:27:13 <isis> among other things of questionable taste, yeah
17:27:56 * isis sees that a ticket they own in review-group-3 is needs_revision…
17:28:06 <asn> nickm: one last review makes sense i agree
17:28:22 <nickm> isis: if you revise it, that would be a lovely thing
17:28:35 <nickm> else I'm actually thinking of scuttling review-group-3 after this meeting and opening review-group-4.
17:28:46 <nickm> (any objections ? )
17:29:18 <asn> review-group-4 sounds good to me.
17:29:20 <dgoulet> yup
17:29:48 <nickm> oh yes btw, other people with needs_revision tickets in review_group_3 are : teor, str4d, athena , cypherpunks.
17:29:54 <nickm> oh, and "nobody".
17:30:21 <nickm> i think that's about it for code review. when I make review-group-4, please remember to assign yourselves as reviewers for stuff. :)
17:30:33 <nickm> next topic was 0.2.8 stable.
17:30:38 <nickm> I see we found at least one regression
17:30:43 <nickm> I wonder how long we should wait for more
17:31:49 <asn> :)
17:31:49 <dgoulet> not that long I would say
17:31:50 <nickm> a week at least, I think :)
17:31:54 <asn> how long was our freezing time historically?
17:31:59 <nickm> totally random
17:32:00 <asn> yeah at least one more little-t-tor IRC meeting :)
17:32:03 <nickm> based on how busy roger and I were
17:32:25 <nickm> but ... everybody should try the delicious software that we are serving.  And look for bugs in it. :)
17:32:28 <asn> let's reevaluate next week depending on whether other regressions appeared
17:32:45 <nickm> ok
17:32:59 <nickm> I have one more thing, but it can wait till after the meeting. any other discussion topics?
17:33:08 <nickm> [the one more thing is "look at 029-proposed"]
17:33:57 * dgoulet is running new git master every day
17:33:59 <nickm> (#19454 is the 028 regression)
17:35:45 <nickm> ok.  given no other topics, I declare us to be happy haxx0rs.  If anybody is not a happy haxx0r, please ping me and I'll try to change things until it is easy to be one. :)
17:35:48 <nickm> #endmeeting