17:00:03 #startmeeting network team meeting, 26 August 17:00:03 Meeting started Mon Aug 26 17:00:03 2019 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:06 hello, network-team! 17:00:11 hi o/ 17:00:13 o/ 17:00:14 o/ 17:00:15 Our pad is at https://pad.riseup.net/p/tor-netteam-2019.1-keep 17:01:38 do we have mikeperry this week? 17:01:43 I guess we get ahf back next week 17:01:55 * nickm just pinged dgoulet on #tor-dev 17:01:57 let's start! 17:02:02 I am here 17:02:05 hi mike! 17:02:23 * asn doing kanban 17:02:36 so, woo, our 0.4.1 stable release is out. We don't need to track getting 0.4.1 stable any more! 17:03:01 and we don't have a page for 0.4.2, so I think we can skip this step this week 17:03:08 (Freeze for 0.4.2 is Sep 15) 17:03:32 woa sorry! 17:03:37 hi dgoulet ! 17:03:42 next up is the roadmap 17:03:53 everybody please kanban the kanban :) 17:04:02 gaba has added items from our september roadmap 17:04:21 #26768 is both in backlog and in next, but with different cards 17:04:22 all setember iteams are in 'backlog' 17:04:24 is this intended? 17:04:29 all remaining august issues are in 'next' 17:04:42 asn: it is not intended and pretty sure it is a mistake 17:04:45 ok 17:04:50 deleting the one in 'backlog' 17:05:04 removed 17:05:09 ok 17:05:14 thanks 17:06:15 #26768 is something you are going to work soon asn? 17:06:16 gaba: should we be adding new items when we add new subtickets to existing tickets? 17:06:28 I think we should 17:06:52 gaba: yes. 17:06:56 ok 17:07:04 gaba: it's what im working on, but it has spliced into #31369 now 17:07:13 so im doing #31369 now, and when it's finished i jump back into #26768 17:07:20 ok, then I will try to add some new subtickets today 17:07:24 nickm: actually, are those subtickets new work or part of the work that you are already estimated to do for the parent? 17:07:28 should I add tickets that are already done? 17:07:39 gaba: I am not sure 17:07:46 maybe? 17:07:55 ok, I think is good to add them to the board. 17:08:10 ok 17:08:14 you do not have to add the tickets already done. 17:08:19 great 17:08:36 I'll make a list, and show them to you when I am done, so you can check if I did it right 17:08:43 thanks 17:09:08 anything else on the kanban? next up is reviewer assignments. 17:09:21 looks like this time I have the big backlog. 17:09:26 I'm going to try to clear through them this week 17:10:01 any review I can't do by end-of-week I am going to admit I'm stuck on, and ask for help with. 17:10:12 how are everyone else's reviews looking? 17:10:44 i think i got it under control for this week 17:10:49 one review spilled from last week to this one 17:10:59 #31314 but i think i can do it this week 17:11:14 cool 17:11:33 #12399 concerned me in that I don't know the protocol consequences of what is happening here 17:12:07 I feel like dgoulet and/or asn should check that this is not serious. I don't ee them commenting on the ticket so far 17:12:36 i was not aware of this ticket 17:12:42 or that it's relevant to HSes 17:12:45 dgoulet, asn: either of you want to take that on? It is a very short diff. 17:12:51 and the patch is in rendmid.c 17:13:05 yes feel free to pass it over 17:13:06 yeah protowarn 17:13:11 great 17:13:18 yeah, the tricket bit is that I think it would be nice if we had some idea why this was happening and if it was serious, before sweeping it under the protocol warn rug 17:13:33 otherwise the diff itself is simple 17:13:49 arma seems to think that it's a custom tor 17:13:58 but we should look into it indeed 17:14:00 apparently it hasn't been seen for a long time... 17:14:09 so, next item is announcements. Only one new one this week: S31 meeting this Thursday at 2300 UTC 17:14:28 everybody's welcome 17:15:20 discussion time! 17:15:29 first one is, what do we do with the remaining august roadmap items? 17:15:53 to see them, have a look at the query on the pad, or search for the network-team-roadmap-august keyword 17:16:28 there is still a week to go so maybe they can be done. 17:16:43 Many of these are subtickets of #29211 -- I'll try to get what I can done in August, but I believe #29211 is now on track to spill into september 17:16:56 I'm going to try to get a head start on some september items, though 17:17:29 I have put less time than planned into #29211 this month because of the branch's backlog 17:17:37 do any of this tickets need to move to the icebox not to be in the next month? 17:17:54 for config refactor,I don't think so. 17:17:54 asn: how is your week looking? would you like to work on #28804 on a pad or something? not sure how to manage merging to git to check the markdown tho.. 17:17:56 from s27 there is only one of them that is new 17:18:07 ok 17:18:12 mikeperry: yep i saw your note and was waiting for the discussion section 17:18:19 yeah, most of the the s27 items are looking pretty far advanced 17:18:41 I could use some help there. I still need to look at this firefox ESR code, which I think the first alpha is next week :/ 17:18:59 except for #23493 .. except it has only one child ticket , which is currently needs_review? 17:19:01 i think the ipv6 s27 item is teor's, and they put it early in the roadmap on purpose, but maybe they can move it for later months. 17:19:15 ah ok there is action 17:19:19 so perhaps they have it in control 17:19:22 right! 17:19:59 asn: looks like you're the reviewer on the child ticket (#23818) and on the grandchild ticket #31492 :) 17:20:16 i think these were assigned today to me 17:20:19 i will check them out 17:21:02 yes I did that :) 17:21:26 i hope they are not heavy ipv6 stuff because i dont know it. but still will check them out early this week. 17:21:41 nope it is not 17:21:44 excellent 17:22:18 mikeperry, asn : did you decide something about #28804? 17:22:51 should we talk about it now? 17:23:09 mikeperry: so my week is pretty loaded because i just came back from camp and there is backlog etc. 17:23:20 mikeperry: but i can perhaps push onionbalance a bit in favor of the circpad docs 17:23:29 mikeperry: are we talking about doing all of it, or doing some of it? 17:23:42 (we should figure out who is doing it when. Personally I tyhink that deferring to september is okay, but I'm against deferring indefinitely) 17:23:48 agreed 17:24:10 asn: I am currently looking for a markdown etherpad thingy so we can collaborte on edits. supposedly this exists but I am not sure who runs them 17:24:28 ack 17:24:29 it would be good if we can collaborate in realtime on it, when we have time 17:24:32 if we cant find it, we can do it on a normal pad 17:24:37 aha 17:24:43 wanna setup a meeting time this week or sth? 17:25:04 i replied on the ticket as you might have seen 17:25:10 but at that point it was just a skeleton 17:25:14 well, I mean more realtime than git pushinhg, but yah 17:25:24 i think i would do a fine job with many of those sections, and not so good with others 17:25:31 it's not a hard deadline for Sept 1.. but I would feel better if we coiuld both edit it 17:25:42 sounds good 17:25:45 yah exactly. with a pad I think it will be easier to manage that 17:26:01 ok 17:26:20 as long as the stuff that i need to do is a manageable quantity, i can def help. 17:26:29 * asn tries to find the ticket 17:27:00 mikeperry: you want to put this stuff in a pad (or i can do it) 17:27:03 nickm: where do you think the circuit padding developer documentation should live? 17:27:06 once we've got it done 17:27:08 and then i can mark the sections that i feel comfortable writing 17:27:13 and we can split them or something? 17:27:28 mikeperry: maybe in a new subdirectory of doc/ ? I am not sure and I think we can be flexible. 17:27:39 I threw my draft in tor.git/doc/circuitpadding-dev.txt or smth I think 17:27:40 ok 17:29:08 also, this is not a bad time for us to look at the september roadmap tasks: 17:29:16 https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~network-team-roadmap-september&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&col=points&col=sponsor&order=status 17:29:50 a bunch of them currently have nobody assigned, including most of the S31 stuff. This will be something to talk about at the Thursday S31 meeting mentioned above :) 17:30:05 anything else on these roadmaps before we move to the next discussion topic? 17:30:17 mikeperry: i went quickly and marked the sections i can do here: https://pad.riseup.net/p/qNuar_OnN6RUrJM5fnSp 17:30:30 Next topic is whether to do an August retrospective, or postpone to end-of-Sep. I am okay both ways 17:31:37 doing it in August is probably not workable at this point... 17:31:42 so we can schedule early Sep or late Sep 17:31:43 yes 17:31:48 or mid sep, I guess 17:31:53 Anybody with a preference? 17:31:59 I think late sept would be good 17:32:05 late sept works for me 17:32:43 post freeze would be best I think also 17:32:44 * catalyst also would like late sep 17:32:45 so late sept. 17:33:00 mikeperry: i think we can also slim down the document potentially as an MVP 17:33:11 mikeperry: IMO some of the sections there while good to have, might not be necessary for an MVP 17:33:18 ok 17:34:37 looks like late sep it is 17:34:46 Do we have any other topics for this week's meeting? 17:36:02 * asn is good 17:36:04 there is one 'need help with' in the statuses 17:36:52 mikeperry: are you ok now with the help from asn on doc writing? 17:37:51 gaba: yah for now. I need to check back in on the Firefox ESR side with gk 17:37:57 ok 17:39:50 anything else for this week? 17:40:18 okay; thanks, everybody! Please ping me about anything; I'm in a good mood to talk about software. :) 17:40:21 cheers! 17:40:22 #endmeeting