16:59:45 #startmeeting network team meeting, 14 May 16:59:46 Meeting started Mon May 14 16:59:45 2018 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:06 hi all! I'm typing a little faster this week on my new keyboard, but I still often hit enter by mistake when I mean 17:00:10 when I mean H. 17:00:15 like that. 17:00:27 so, this week's pad is https://pad.riseup.net/p/fsuA7cgc5dOI 17:00:32 how's everybody doing? 17:00:46 hello 17:00:51 i'm very good nickm :) 17:01:44 starting with the roadmap... 17:01:45 we 17:01:48 we 17:02:04 hi 17:02:04 hey! 17:02:11 we have some items that are not listed as done. 17:02:12 nickm: could you share the roadmap URL? :) 17:02:18 it's on the pad 17:02:25 pad is https://pad.riseup.net/p/fsuA7cgc5dOI 17:02:30 * dmr realized that right after hitting enter 17:02:42 thanks :) and sorry 17:02:54 Since tomorrow is feature-freeze, we should probably assume that any feature not currently in needs_review will miss 0.3.4 17:03:04 mikeperry: am I right to say that we can close #25546 after #25903 gets merged? 17:03:10 dmr: no worries 17:03:18 nickm: i pinged sbs about #25510 last week, but i don't think i've got a response yet. gonna prod again after the meeting 17:03:41 ok. Anything that's a bug we might be able to fix 17:03:48 anything else will have to wait 17:04:00 I think #25499 is de-facto done? 17:04:04 asn: yah I think so 17:04:08 #25507 is noncoding so can wait. 17:04:37 asn, mikeperry: can you adjust the sponsor-V vanguard items on the roadmap as needed? 17:04:42 mikeperry: ack. and what about #25545? do you think we are sufficiently ok with 2-4-8? should we write a doc with the motivation? 17:04:44 #25496 is non-coding (at least in tor.git) too 17:04:49 mikeperry: or should we just close 17:05:20 mikeperry: i'd just close and do any other fine tuning of the topology in the future as we test vanguards. 17:05:58 asn: do you have high run count graphs from any of 2-3-6, 2-4-6, 2-4-8? 17:06:01 o/ 17:06:07 mikeperry: not rn, but i can make. 17:06:14 mikeperry: i can also make with maxx. 17:06:26 ahf: ack 17:06:27 asn: I never let the script run for long enough to get those, esp since the layer1 compromise takes a loooong time 17:06:54 mikeperry: ok i can make those graphs tomorrow. 17:07:19 why is #25903 in needs_review again? i reviewed it? 17:07:22 oh i see 17:07:27 setting it back 17:07:53 mikeperry: and what about #25668? should we consider the 2-guard proposal "investigated" for now? it will need revision and implementation tho. 17:08:01 isis: do you think we're okay to call #24986 "as done as it will get for 0.3.4"? 17:08:21 nickm: yeah, i moved everything to 0.3.5 17:08:23 (arg, desktop weirdness, afk 1 minute) 17:08:42 isis: ok. could you also check it off on the roadmap? 17:09:08 asn: yeah we need to like write up everything from that thread I think :/ 17:09:35 mikeperry: do you think we should do it as part of that roadmap item, or make a new one for 035? we still have V anyway... 17:09:45 (re) 17:09:55 mikeperry: new roadmap item coudl be "Revise prop#279 as needed and implement" or something... 17:10:17 asn: ok 17:10:23 asn: lets do that 17:11:09 isis: okay, my desktop is working again . I checked it off 17:11:13 mikeperry: and what about #25545? do you want to wait for the graphs before closing? or should we close now, and if the graphs show us something surprising, we just revise if needed. 17:11:19 mikeperry: i'd just close now 17:11:20 a 17:11:22 nickm: yep! 17:11:29 nickm: oh you got it 17:11:48 ahf: did you have an opinion on #25499? 17:11:50 (ugh prop#279 above should be prop#291, or whatever the 2-guard proposal is numbered as) 17:13:28 mikeperry, asn: did you decide on #25546 status too? 17:13:43 nickm: let's close #25546 after #25903 is merged? 17:13:49 nickm: or we can just clsoe it now. it's just #25903 left. 17:14:17 nickm: i think after the talk we had thursday that what is there now is good, just need to hook it up in orbot too and see how that works 17:14:26 ok 17:14:49 let's close it now; #25903 can squeak in IIUC 17:15:00 soundsd good 17:15:24 i need to do some ticket moving to close the corresponding ticket 17:15:33 asn: #25545 can be closed, I guess.. I dunno. I'd rather have the graphs first :) 17:15:48 ok ill make the graphs this week. 17:15:50 ahf: okay. I'll mark it done 17:15:55 and close it soon. 17:16:03 mikeperry: which adversary model would you like me to use? 17:16:53 great. That's roadmap! 17:16:54 cool! 17:16:56 wait where was the original ticket for the simulator? 17:17:05 #23978 17:17:23 next thing to do is reviewer assignments, if we're done with the roadmap 17:17:37 we only had two needs_review tickets this week 17:17:40 i took one, david took the other 17:17:50 if more tickets come, perhaps we can assign them mid-week? 17:18:15 huh. I see a lot more than that on the spreadsheet. Are those all stale or what? 17:18:22 or are those from last week? 17:18:28 yes some of those are from last week 17:18:57 I see 6 tickets in needs_review now for 0.3.4... 17:19:00 ye i meant only two new needs_review tickets 17:19:26 ok. so people who have needs_review stuff are ahf, dgoulet, asn, and nickm. 17:19:53 Can everybody on that list get through all their needs_review stuff today, if it is something that might be affected by the feature freeze? 17:19:59 yes 17:20:36 yes 17:20:41 asn, dgoulet: ^ ? 17:20:49 hmmm i wonder why #25947 is on 34 17:20:52 hmmm i wonder why #25947 is on 034 17:20:55 but #25960 is on 35 17:21:06 and they share the same branch 17:21:22 it's okay with me if they both go to 035, unless juga objects. 17:21:27 yeah lets do both of them in 035 17:21:32 the 034 one is unittests anyway 17:21:35 ok. please frob the ticket :) 17:21:38 ack 17:22:03 rotations this week are: ahf -- triage. asn -- community. catalyst -- coverity. dgoulet -- CI. 17:22:19 ack 17:22:22 everybody cool with that? anybody have leftover stuff from last week? 17:22:40 i think david had a comment on being CI this week in the pad 17:22:50 * catalyst probably needs to follow up on #26040 17:22:53 I should be working with ahf a lot on the triage stuff, since this week will see heavy triage of old and new tickets 17:23:02 right if someone wants to switch with me on CI would be nice since I'm off mid-week :S 17:23:05 nickm: yes! 17:23:24 ahf: ok, ping me any time. You know my schedule. :) 17:24:00 nickm: maybe we could get our hands dirty with it tomorrow when you get online (or a bit later if it's early there)? i need to finish my reviews tonight first 17:24:32 ahf: sounds like fun! 17:25:18 cool! let's do that 17:25:29 i'm gonna ping you when i see you check in on irc tomorrow! 17:26:11 isis: I tried to answer your questions on the pad 17:27:28 nickm: is the hackfest pad public? sounds like not, but thought to check 17:27:30 announcement about the seattle hackfest pad:it's already a semi-public document, and it's likely to become more public. Please let me know soon if there's anything (besides the list of names) we should remove before the whole world looks 17:27:39 asn: (I am still thinking about adversary model - I might push a commit tweaking things a little) 17:27:41 dmr: ^ 17:27:50 * dmr loves human-time-scale race conditions 17:27:55 also please have a look at the pad for the stuff that's been added recently 17:28:17 mikeperry: ack let me know! 17:28:40 haxxpop: i will try to take a day to put client auth things into my brain this week. antonela is also interested in checking it out from a UX perspective. 17:28:52 other stuff: once 0.3.4 is frozen, even though it hurts to do so, PLEASE prioritize fixing 0.3.4 bugs over stuff that's roadmapped for 0.3.5 17:28:59 only you can help us release on time 17:29:29 asn, yeah nice ! antonela nice to work with you :) 17:32:21 So wow, it's been only 30 minutes, but I think we're through the agenda. any more to talk about today? 17:32:40 dgoulet brought up a logistical issue with the rotation 17:32:48 ah yes! 17:33:09 Does anybody want to swap for dgoulet's CI rotation? 17:33:18 If not I can try to pick it up 17:33:47 and is there anything else for this meeting? 17:33:58 btw wrt seattle logistics 17:34:02 i'd trade but i'm also gone thursday and friday 17:34:03 i wont be able to attend the hackfest this time 17:34:09 but let me know how i can be helpful 17:34:17 if you need me for a session or anything 17:34:43 oh also komlo and my rustconf talk about tor got accepted \o/ 17:34:56 isis: cool! 17:35:02 isis: awesome! 17:35:16 isis: awesome! remind me of the topic? 17:35:17 asn: maybe we can get you online there like we did with mike and isa in montreal 17:35:45 asn: can you look over the pad and the list of topics and see if there's anything you really want to make sure we cover or think about? 17:36:00 ack 17:36:02 or send us notes on anything you want us to have your perspective on 17:36:04 nickm: it's about integrating rust into a large C codebase 17:36:31 neat! 17:36:51 I hope we solve all our integration issues before then 17:36:53 :) 17:37:04 August, right? 17:38:17 yes, august 17 in portland 17:38:29 cool 17:38:45 the same day as i'm apparently supposed to be at a wedding on the other side of the country, no idea how to pull that off 17:38:46 they do recording of talks too? can't remember if it was a rustconf video i saw with you and henry talking about the rust crypto work 17:39:01 yep! there will be recordings 17:39:03 okay, seeing nobody else, I'm pickin up dgoulet's CI rotation on the days when dgoulet is gone 17:39:04 sweet 17:39:10 dgoulet: which days are those again? 17:39:11 nickm: thanks 17:41:05 and hearing no new topics in the last couple of minutes, I'm going to call this one adjourned. Thanks, everybody! I'll be hanging around on IRC for the next couple of hours, I hope. 17:41:20 have a great week, you awesome people! 17:41:28 o/ 17:41:35 I believe in you, and I'm honored to work with you! 17:41:37 #endmeeting