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