17:00:07 #startmeeting network team meeting 17:00:07 Meeting started Mon Jul 17 17:00:07 2017 UTC. The chair is asn. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:17 pad is @ http://pad.riseup.net/p/LCss5dtbyXCJ 17:00:31 nickm: dgoulet: catalyst: ahf: isis: pastly: teor: etc. ^ 17:00:38 or whoever is around 17:00:42 ehlo 17:01:02 ok im going thru the status reports 17:01:30 thanks screen -dr 17:05:15 thanks asn, sorry about this horrible internet connection i have 17:05:19 it's fine 17:05:31 so didd everyone read the status reports? 17:05:45 o/ 17:05:50 does anyone want to move to discussion and which topic? 17:06:38 i'll do my regular reminder that code review is awesome 17:06:55 and that fixing 0.3.1 bugs is nice 17:07:25 review-group-20 seems all reviewed up 17:07:35 fwiw 17:07:37 ugh i cannot load the pad 17:07:45 http://5jp7xtmox6jyoqd5.onion/p/LCss5dtbyXCJ 17:07:45 http://pad.riseup.net/p/LCss5dtbyXCJ 17:08:27 ive added my notes now, but my boat will start sailing in a second so will probably disappear after that. i will answer questions once i am on the other side of the boat trip. 17:09:29 mobile sponsor8 stuff look very cool :) 17:10:17 teor: komlo: great to see people organizing extra hackfest activities! i wrote some stuff about my availability on the pad. 17:11:41 yes, the sponsor 8 stuff is going to be a lot of fun. just need to round the sponsor 4 stuff off firstly before it becomes too exciting. heh 17:12:05 dgoulet: added #22940 and #22735 to https://pad.riseup.net/p/LPVY6AL_prop224_upstreaming as well 17:12:45 ok i guess there is not much to discuss 17:13:01 one thing i would like to know... 17:13:01 can we talk about Montreal scheduling? 17:13:07 nickm: you prefer email over irc this week, right? 17:13:31 dgoulet, teor: I wonder if we have consensus that trace is a better way to export data to privcount than the control port is 17:13:51 if we agree on that I'd like to know because I'd like to hack a little on that 17:13:55 ok. on a boat now. will read backlog later. 17:13:58 dgoulet: maybe talk to teor when you're both around? 17:14:05 ahf: yes, email is better 17:14:16 nickm: I did about it in AMS and control port is not ideal 17:14:17 so yes 17:14:18 catalyst: sure we can talk about montreal scheduling though mailing list is also a good idea for followup there 17:14:20 let's talk more 17:14:33 catalyst: no reason we can't talk here though 17:14:41 asn: should I open a review-group-21 ? 17:15:50 nickm: i think it's a reasoanble time to do so 17:16:03 all review-group-19 and review-group-20 tickets seem to be in needs_revision or merge_ready or merged 17:16:25 ok, will do 17:19:53 discussion on montreal stuff? 17:20:30 are folks at PETS this week? 17:20:49 i have a feeling this is not the best time to do the montreal discussion, given that teor who is driving it is not around... 17:21:00 but i also dont have a suggestion on how to do the discussion best 17:21:13 I am! So is mikeperry and isabela and armadev . Not sure who else. 17:21:15 email thread, we can hit everyone on the net team at once 17:21:19 right now it seems to be split among at least 2 email threads? 17:21:35 let's consolidate? :) 17:22:34 also any plans for post-meeting stuff? i wound up possibly missing some stuff at AMS because some last-minute stuff materialized; should i expect to stay late in case something comes up? 17:23:20 So, fwict, our best opportunity for that is to make sure we have a reliable plan to be available for each other during the public hack days... 17:23:29 ...and a way to schedule time and space during those days. 17:23:44 I think most people generally stay for the public hack days if they can 17:23:48 any other thoughts? 17:25:19 ok the public hack days are 14th and 15th, plus a bonus teor day on the 16th? 17:25:32 yeah that is a good strategy that pays off usually, the Rust hackfest is on Oct 10th so now we need 1) to make an agenda for Oct 11th and 2) do we do one on the 9th for people who would be there and then 3) 16th+ :) 17:25:49 catalyst: yeah teor even proposed the 9th 17:26:01 hmm. let's remember that people's energy is finite :) 17:26:07 especially for old folks like me 17:26:16 yeah the 16th I'm not sure ;) 17:26:26 as I said, I'm usually drained by then 17:26:38 also patience for poor quality venue wi-fi is limited (and slows down work a lot) 17:26:58 do we want any rust people to be invited? and/or people who teach rust? 17:27:45 nickm: PETSy question for you at #22940 ;) 17:27:57 ok 17:28:16 i know basically nothing about rust but would be interested in being in an environment that makes it easy to learn more :) 17:28:28 asn: /me looks 17:28:44 asn: huh, thought I had replied there 17:29:02 catalyst: want to consolidate the email threads for the hackfests and 11th meeting? :D 17:29:03 oh, wait, I had replied here 17:29:23 i'm pretty sure there's several who would be happy to come hack with us 17:29:27 but that might be harder if we're like "ok, it is gonna be the 9th and 10th, then we start again on the 13th-16th" 17:29:36 nickm: oh my irc box restarted... perhaps i lost backlog 17:29:52 so maybe it would be better to point out the public hackdays and invite them to that? 17:30:00 asn -- copypasted 17:30:06 thx 17:30:24 isis: that seems like a reasonable plan 17:32:02 asn: ack 17:32:22 would there be any purpose in continuing to have hackfest stuff on the 9th and 10th then? or is that "hack on rust without outside rust experts"? 17:32:37 isis: maybe this should be post-meeting but have you figured out the TB + Rust question? 17:33:18 ( dgoulet: what's that question?) 17:34:02 asn: well if we can enable Rust in TB and then probably reproducible builds at that point? 17:35:50 catalyst: I'm a bit confused by your question. You mean is there purpose to have a Rust hackfest on the 10th *without* a Rust expert? 17:37:17 if isis invites the outside rust people for 14th-16th but not 9th-10th, are we still doing rust stuff on the 9th-10th? 17:37:21 the ticket for reproducible builds in rust was started by infinity0 like a year ago, and seems to be going pretty well https://github.com/rust-lang/rust/issues/34902 17:38:05 catalyst: good question... I haz no idea ... I'm still unsure what that Rust hackfest is exactly :S 17:38:08 i mean, the TB team unfortunately doesn't get much of an option with rust, because the ESR for next june it is not optional 17:38:23 oh wow 17:40:20 i would be interested in that rust hack idea. is there a way to keep me updated so that i can take that into account when booking my flights? 17:41:43 so i guess if we do something on the 9th and 10th, we could have sort of a recap session like we did in wilmington on the current status, and then start getting people set up with the tooling to build tor with rust and start hacking in rust, and then maybe find small projects to do to start learning 17:43:02 and then 13-15th we could invite some rust people and they'll probably have a lot smarter pointers than i could give 17:43:41 i guess once we consolidate the threads i'll just put that there and ask everyone 17:44:07 neat 17:44:41 should we try to figure out who will be the thread consolidator? 17:45:00 since it seems we need a central thread with all the options/ideas and a way to declare attendance 17:45:08 GeKo: we've been talking on network-team@ but we can also cc tbb-dev@ ? or is there a better list to cc? 17:45:30 GeKo: is there a tbb-team@ list? 17:45:34 asn: +1 we need a consolidator 17:45:52 i can consolidate 17:46:04 boom 17:46:17 wait let me make sure i have both 17:46:19 i think i misremembered and there might not be hackfest stuff in the team day (11th) thread; sorry for any confusion 17:46:20 teh consolodator has been found! 17:47:02 anything else to discuss people? or should we wrap this up? 17:48:32 yeah there seems to be only one thread 17:48:46 consolidation done! boom 17:49:04 i'll cc GeKo i guess? 17:52:13 meeting is done? 17:52:43 #endmeeting