17:01:34 #startmeeting weekly network team meeting 17:01:34 Meeting started Mon Apr 25 17:01:34 2016 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:01:38 hi hi hi 17:01:43 we'll start with checkins! 17:02:22 I've been working on code review, merging stuff, fixing up my patches as people find issues with them, categorizing tickets, getting the bug retrospective done, and did I say code review? :) 17:02:57 In the rest of this week I aim to finish the bug retrospective and finish fixing-my-patches and review more code. Also I must help Isa with a sponsorS report, and did I mention more code review 17:02:58 i've done a bunch of backport tickets recently; looks like we finally have none left before 0.2.8, and some code reviews. 17:03:24 i take it you're going to ahead and drop the absolute timeouts from #18365, nickm? 17:04:30 I think so 17:05:19 They don't have a would-be user right now. 17:05:20 hi 17:05:23 hi Yawning! 17:05:32 hi hi yawning 17:05:38 poking at obfs5 17:05:58 it might actually hand shake and relay bytes, though obfuscation still needs more work 17:06:03 since only the null padding is implemented 17:06:16 probably the last PT I'm going to write in go 17:06:34 because having to replayce parts of the runtime is dumb 17:07:01 See: https://github.com/golang/go/issues/11833 17:07:11 for "how not to implement a cryptographic entropy source" 17:07:21 (Yes, I fix that) 17:09:38 nickm: I am here 17:09:53 hihi! 17:09:58 I apparently am also allowe to do business 17:10:00 I finished the Firefox networking review finally. still need to get to the tor reviews 17:10:03 according to the government 17:10:10 so yay I guess 17:10:18 I sent an email yesterday reminding folks that we are at the last week of the month. we should be reviewing april tag and adding things to may tag 17:10:35 Yawning: we should get together and get your deliverables and contract hammered out so that we're clear what you want to do and you're clear what Tor can pay you for doing. :) 17:10:52 yes, I was writing an email to you two about it :) 17:11:05 Ideally the overlap amounts to as much money/work as you like. 17:11:57 yeah 17:12:44 I'm mostly happy with how obfs5 is coming along 17:13:01 I'll document and post to tor-dev@ once I have something feature complete 17:13:25 I'm 99% sure life will be a lot better for the default bridges with the new code 17:13:42 for varying amounts of "a lot better" depending on if I want to write a poly1305 or not 17:14:23 next ish? 17:14:30 Yawning: I will write a note about you coding obfs5 for the q1 report I am doing for sponsorS 17:14:49 Yawning: I show you so you can review, ok? 17:15:26 yeah 17:15:33 note 17:15:37 name not final 17:15:48 it likely isn't going to be obfs5 unless there is a reason for it 17:16:11 hi! sorry i'm late 17:16:16 no worries 17:16:19 who else has a checkin? 17:16:26 i got lost in a sheep field again 17:17:00 :) 17:17:03 baaaaaa 17:17:19 i can checkin 17:17:46 i reviewed #16792 and started to review #8185 17:18:30 for the latter, i used to hit what i think is that bug, but then i tried to trigger it on a bunch of version with chutney and couldn't 17:18:41 when i used to be able to trigger it in chutney 17:18:50 so i'm not sure what to do with that one 17:20:02 i also went over my #7144 patches and found that the tests were failing due to my rebase leaving out a line of initialising part of a mocked structure in the unittests 17:20:32 so i fixed that, wrote more tests, and then rebased onto master for 0.2.9.x 17:21:01 i need to test it more, and i still have a few more comments from nickm's review to address 17:21:32 i also read yawning's newhope code and obfs5 code 17:21:38 i think that's it for me 17:22:33 * isis goes to read scrollback 17:22:43 yawning's gigantic piles of insanity? 17:22:44 >.> 17:22:45 ok. anybody else? mikeperry / asn_ / dgoulet / ... ? 17:24:33 mcs: I'm looking at the patch for #7920 (aka #6786). For upstreaming to Firefox, do you think this needs to be behind a pref? 17:25:21 Or is that code only active when the "ui.use_standins_for_native_colors" is enabled? 17:25:40 arthuredelstein: meeting in progress, fyi :) 17:25:49 oops, sorry 17:26:03 ok, let's move on to discussion and hope that mikeperry/ asn_/ dgoulet show up as we're doing so. 17:26:12 (with checkins) 17:26:15 oh wait, mikeperry gave one 17:26:16 sorry, mike 17:26:20 yeah 17:26:23 * nickm has no short term memory 17:26:28 I think dgoulet is busy in dc with armadev 17:26:32 ok 17:26:59 So, topics for discussion? (if any. We're not obliged to use a whole hour) 17:27:04 I have a couple 17:27:11 1. Reviews reviews reviews! 17:27:35 2. what to do approaching end-of-month. 17:27:40 3. 0.2.8.next 17:27:50 isabela: what do you have? and do we have more? 17:27:53 (i wonder if special got gerrit set up 17:27:56 ) 17:28:20 (I've been using cakelab as a review engine for the prop250 branch.) 17:28:21 nickm: I think you cover it - btw I updated the wiki page to have april and may tags 17:28:28 nifty 17:28:58 oh, here's a bookkeeping question. Should I remove the April tag from stuff that won't happen in april now, or should we do this as part of may planning? 17:29:09 and should we be tagging stuff for may this week, or next? 17:30:44 we should start this week - because for all the things on april, you will have to decide if 1) will be close by EOM so nothing need to be done 2) should be moved to May to be finished 3) won't get this done now or later, remove monthly tag .. will be picked up another time 17:31:04 ok 17:31:05 first week of may we will check what is the situation looking like for may 17:31:23 is it important to track what we _thought_ would happen in april, to know how much we postponed ? 17:32:24 yes 17:32:34 i wonder how tho 17:32:50 so we should leave the april tag and just append a may tag? 17:34:01 without an appropriated plugin for tracking this stuff is hard to have a way that is not funky :) 17:35:05 we could add a deferred-from-april tag? 17:35:42 sure 17:36:11 ok. 17:37:20 isabela: is there a plugin which would help you track this sort of thing? 17:38:28 isis: yes but I am not sure about the quality of the code/maintainance 17:39:36 https://trac.edgewall.org/wiki/AgiloForScrum 17:40:47 nickm: for 1. reviews reviews reviews 17:41:01 I wonder how the first review and 2nd review is going 17:41:04 yes! 17:41:19 sometimes first review happens and 2nd review goes fast and I merge. That's my favorite. 17:41:26 hehe 17:41:35 sometimes during 2nd review I throw it into needs_revision. That slows things down. 17:41:50 Sometimes first-review doesn't happen so much. That's a problem. 17:42:08 we have 5 needs_review tickets with no reviewer, and 12 other needs_review tickets. 17:43:39 we should check how long tickets stay on need review state 17:43:45 i just assigned myself to review #18240 17:44:00 so now we only have 4 :) 17:44:35 \o/ 17:44:40 i am tempted to put #8185 into 'needs_information' state as well 17:45:31 since i'm not sure how i'm supposed to review cipherpunk patches when i can't even trigger the bug anymore for some reason 17:47:07 actually i think i will do that, if nobody objects 17:47:16 go for it; be bold 17:47:25 I've set myself as reviewer on #18685. 17:47:58 the hard parts of #17158 and #18749 are related to teor's python fallback-list code. 17:48:32 #17983 needs review (which should be easy) and a little hard thinking by somebody who likes crypto and compilers. 17:48:43 and that leaves #17101 with no reviewer. 17:49:10 #action for everybody:if you are listed as reviewer and you won't be reviewing this week, see if you can get somebody else to do it :) 17:49:29 is there a way to check to see what 17:49:33 I'm a reviewer for 17:49:57 You can do a search by fields. 17:50:13 you can add the reviewer column to the trac list view by clicking on the '> columns' thing near the head of the search results 17:50:37 for april tickets, you (yawning) are currently listed as reviewer on #18402. 17:50:53 asn is on #17799 and #18607 17:51:04 dgoulet on #18363 and #18616 17:51:12 oh ok 17:51:15 isis on #8185 and #18240 17:51:27 mikeperry: on #7478 and #14881 17:51:40 nickm on #16861, #17592, #17604, and #18685. 17:51:55 nobody on #17101, #175158, #15983, and #18749. 17:52:05 (that's only for needs_review tickets) 17:52:59 (that's only for needs_review tickets in TorCoreTeam201604) 17:53:19 but if everybody does two reviews early this week, we'll be in such a happy place. 17:53:29 isabela: anything more to add? 17:54:51 i will try to build a report first week of may for us to learn more about how we are doing 17:54:55 that's all :) 17:55:06 tor browser meeting in 4 minutes 17:55:15 ok. any more for us for today? :) 17:55:25 0.2.8.next I guess 17:56:09 yes, please follow teor1 orientation for 0.2.8 prioritization 17:56:16 while electing tickets for may 17:56:17 :) 17:56:20 makes sense. 17:56:28 ok, thanks everybody! 17:56:31 #endmeeting