23:01:39 #startmeeting network team meeting, 23 April 2019 23:01:39 Meeting started Tue Apr 23 23:01:39 2019 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:01:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 23:01:43 how goes? 23:01:44 hi 23:01:50 hi catalyst! 23:01:53 anybody else around? 23:01:59 hi 23:02:21 hi mikeperry ! 23:02:32 dgoulet is not on channel; I've pinged him on #tor-dev 23:02:36 we expecting anybody else? 23:03:07 ahf has gone to sleep, asn may also be sleeping 23:03:12 * meejah lurks 23:03:28 I think it's 0100/0200 for them :) 23:03:43 as usual our pad is https://pad.riseup.net/p/tor-netteam-2019.1-keep 23:04:42 going down the standard items -- there are no currently unaddressed tickets on the CI list. 23:05:05 ahf suggests that #29930 doesn't hve to be 040-must, and I concur 23:05:13 I agree 23:05:39 in theory we should look at the kanban now, but it isn't loading for me. Can anybody else see it? 23:06:13 hiro sent me a workaround about the board 23:06:25 click an 'all boards' and then in the board... then it loads 23:06:27 oh? 23:06:30 it seems it is the bug with the new wekan 23:06:34 new version 23:06:52 'all boards' is a link at the top 23:07:24 wow 23:07:29 software is great :) 23:07:33 yeah, it works 23:07:56 we have a _lot_ of things in backlog right now 23:08:07 gaba: should we talk about prioritizing? 23:08:22 ok 23:08:33 the backlog should be sorted out by priority 23:08:45 if it is not then we should sort it out by priority 23:09:01 mmm, actually. nickm: do you want to talk about it now? 23:09:04 teor: when do you disappear? 23:09:15 gaba: yes, let's 23:09:19 ok 23:09:50 nickm: at the end of today, in ~8 hours time 23:09:53 the onion services tickets are still not integrated into the backlog. asn and dgoulet will look at the priorities for it and then we integrate them (right now they are in its own column) 23:10:12 teor: cool 23:10:21 gaba, nickm: I have sorted my backlog tickets by priority 23:10:28 there are a lot of tickets that were "planned" for march/april that are in the backlog. 23:10:31 nice teor. thanks 23:10:34 gaba: IIUC that sponsor has a much later due date than the other stuff... 23:10:41 yes 23:10:49 the next one ending is s19 at the end of may 23:11:20 is the canonical backlog we are supposed to sort in the kanban? my workflow would be faster if I could just update priorty fields on trac 23:11:29 for wtf-pad tickets, at least 23:11:36 teor: looking at my backlog for S19, the chutney-PT stuff seems high priority. I'd like to know your thoughts on how you think I should procede there, so that when I try to do it I have the benefit of your suggestions 23:11:57 mikeperry: how do you sort it out in trac? 23:12:30 gaba: this query https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~wtf-pad&order=priority 23:12:31 teor: is chat or email most convenient there? 23:12:32 mikeperry: i find that trac isn't fine-grained enough to really prioritize things 23:12:51 mikeperry: I agree. I would rather use trac and ignore the kanban. The kanban does not update automatically, so it gets out of sync. 23:13:01 catalyst: it depends. I like to group by tag or topic and then priortize 23:13:13 nickm: let's talk in tor-dev? 23:13:15 otherwise there's too many other high priorty things in the way I don't care about 23:13:17 one problem with the trac approach is that it has so darn much 23:13:29 and it doesn't restrict itself to the roadmapped stuff 23:13:36 yes, we need a subset of tickets for the team, that are the onews being worked on 23:13:43 My best experience with trac is mikeperry's grouping then prioritising method 23:13:44 nickm: yes this is why tags, milestones, and other filters on queries ar essential 23:13:54 i agree that integration trac/kanban would be the best but we do not have it right now 23:14:12 gaba: no, I just want to use trac, sorry 23:14:13 teor: sure. I will try to be around after but I need to do bedtime for the kid tonight, so I may not have a lot of time 23:14:22 nickm: email also works 23:14:43 ok. if we run out of time, email me what you think some time in (your) today? 23:15:22 gaba: "Having too many tickets on the one page" is a process failure. "Having different statuses in different tools" is another. 23:15:37 I really do think we can use trac better, so we avoid both these issues. 23:16:09 nickm: sure, I haven't read your updates on the sponsor 19 tickets yet 23:16:22 so here's a problem about the "different statuses" that makes it harder to use trac as "source of truth". 23:16:31 Maybe we can come up with a solution 23:16:50 today gaba and I tried to figure out which of the roadmapped items we had done and which we did not have done 23:16:56 for a couple of sponsors 23:17:19 a lot of the "SponsorX-must" items had gotten that label after Brussels, based on one person's judgment. 23:17:39 and so it's hard to figure out which items of that kind are actually our contracted deliverables 23:17:46 and which are just things somebody found to be really important 23:18:26 We also have a similar problem with the release milestones 23:18:51 Whatever we use as our sponsor-tracking roadmap, maybe it needs not be world-writable. 23:19:08 Or maybe it needs to have a propose-change/actual-change process 23:19:15 the kanban will have these miscategorization issues too, if we all have to update it... at least trac has the changelog updates of these things emailed, archived, searchable, etc 23:19:21 +1 23:19:34 trac is where the community and everybody brings issues/bugs to. we need a place where we can filter and sort out more specifically that is related with the sponsor work that the team decides to do. 23:19:51 gaba: I don't think that's a solution 23:20:17 Now we have two places that are out of sync 23:20:34 FWIW, I really don't like it how every time we have a procedural "and now we update X to match Y" thing, we need to have a discussion about whether to have X and/or Y 23:20:37 don't get me wrong, I like the idea of kanbans; I will be proposing using one on Friday in the scalability meetings.. but it's going to be used differently; it can't ever replace trac. I think it has to have much less granularity than trac, inherently 23:20:56 Maybe we should have a rule about separating meta-discussion and non-meta-discussion? 23:21:46 nickm: I think you're right. We can't change our use of trac and kanban in this meeting. Let's talk about it in July at the in-person meeting? 23:21:51 +1 23:21:56 +lots in fact 23:22:12 +1 23:22:21 Looking at my own issues for the kanban ... #29210 is still in progress; I'm blocked on catalyst finshing their review 23:23:05 for my backlog items, I want to take on #29267 next, based on advice from teor 23:23:15 nickm: was in the middle of writing up a comment on that :) 23:23:29 I can't to #28878 until #29732 is reviewed 23:23:32 catalyst: great! 23:23:48 #29283 and #29263 are less important than #29267 imo 23:23:52 #agreed We will use the kanban and trac until the July meeting. Then we will talk about it in July at the in-person meeting. 23:25:38 teor: I also want to talk at some point about what I can do for privcount while you're away 23:26:09 the kanban is still not lading for me 23:26:20 did you try the workaround above? 23:26:23 loading either. maybe that is non-meta 23:26:30 mikeperry: https://github.com/sandstorm-io/sandstorm/issues/3132#issuecomment-485948463 23:26:43 (click on "all boards"; then click on the roadmap) 23:27:35 nickm: ok, we have a lot to talk about. Let's try to start handovers earlier next time. 23:28:16 shall we move on to the next item? 23:28:35 I am fryustrated to have to update two places when I work on a ticket that takes less time than to update either 23:28:54 mikeperry: we're going to talk about that at the July meeting. 23:29:11 Indeed, let's talk about it then? 23:29:13 that's nice. I still prefer to only use one of these systems 23:29:18 until then 23:29:28 It is also frusterating to talk about this every single time we have a meeting 23:29:57 Did the page load for you after you tried the workaround? 23:30:17 mikeperry, nickm: I understand and share your frustration, but we need to cover other things in this meeting. If it's urgent, let's do it by email on the network-team list? 23:30:36 yes.. I havce filtered on my sponsor.. I have a lot of data entry to do apparently.. we created like 4 small subtickets of #28683 last week 23:30:53 it's frustrating to have to do all that when these items are small.. maybe I should merge my tickets first? 23:31:08 #28634 23:31:10 we don't need a kanban item for every ticket 23:31:21 if that's in-progress, just set it to "in progress" 23:31:54 (by merge I mean combine) 23:32:05 can we go on to reviews? 23:32:47 I have just updated the list of stalled reviews on the pad 23:33:08 (I will turn it into a trac wiki page eventually, so it updates automatically) 23:33:40 catalyst, mikeperry: do you need help with your old reviews? 23:34:07 if they are uent, yes. I need to task switch to tor-performance meeting stuff tomorrow 23:34:12 *urgent 23:34:23 The expectation is that we work on reviews the same week we get them 23:34:36 IIUC 23:35:14 mikeperry: can you do all your reviews this week? 23:35:19 teor: #27130 should probably be needs_information or needs_revision because there are tricky things, but i haven't had time to comment and it didn't seem urgent 23:35:20 no 23:35:34 catalyst: ok, please pass it over to me or mark it needs_information? 23:35:40 mikeperry: can you expand your no? 23:36:32 no, I don't have time to get through all of those reviews; I need to task switch to tor-performance meeting stuff tomorrow 23:36:49 Do you need help with the tor-performance stuff? 23:36:49 as it says on the pad, I want to write up a wiki page of the experiments we discussed for the meeting on Friday 23:36:52 and work on other things 23:36:53 teor: also #29732 could go to someone else 23:37:44 mikeperry: am I being naive when I choose to review your code the same week that I get assigned the review? 23:37:47 Am I being a chump? 23:38:18 nickm: #27130 reassigned to your review 23:38:21 sorry, that was unkind 23:38:22 I try to do reviews that are coming in an upcoming release soon first 23:38:35 mikeperry: But please understand: everybody's workflow depends on their code getting reviewed and merged 23:38:36 mikeperry: maybe we can drop roadmap work for this week and do the reviews? 23:38:48 the ability for us to put Tor out depends on all reviews happening in a timely way 23:38:53 We are trying to share this work as a team 23:39:13 I also got to the end of the week and realized I had to choose between self-performance review, booking travel, code review, my temportary bug triage role, vanguards issues, and some other things 23:39:30 If you put this work no to all the other people, then those people have less time to help you with stuff that you do evaluate as important 23:39:42 I dropped several of those things. I didn't expect the self-performance review to take so long; I chose bug triage and that, though 23:40:03 hey folks this sounds like classic overwork; could we please not try to assign blame? 23:40:12 overwork from process issues, that is 23:40:18 sorry, I am having a hard time today 23:40:58 gaba: could you run the meeting for a few minutes? 23:41:01 hey o/ - reading backlog 23:41:04 ok 23:41:39 so, reviews from mike, let's talk about it later so we continue 23:41:59 sorry that you are feeling overwhelmed with all the stuff 23:42:19 it has happened to all of us. It is not anyone's fault. 23:42:25 * gaba trying to see which part of the meeting is next 23:42:28 yep 23:43:06 We are here to help you, but we need to know what you need help with. 23:43:13 review assignmetns for this week 23:43:33 anybody else need to drop some reviews this week? or are peole ok with their reviews 23:43:42 any blocker from reviews from last week? 23:44:11 * catalyst could use someone else to take review of #29732 23:44:22 asn and dgoulet aren't here, so let's just leave the reviewer for #29732 blank, and shift it to next week? 23:44:35 i only have 2 and one is a shellcheck one, so i could take one more if that helps anybody 23:44:40 ok 23:44:47 ahf: can you take #29732 ? 23:45:08 yes 23:45:11 assigning it to me 23:45:12 thanks 23:45:21 I didn't have any review capacity this week, because I had 4 peer feedbacks. I know that increases the load on the rest of the team, and I am sorry about that. 23:45:34 ahf: thanks! 23:45:45 np! 23:45:58 mikeperry: if you have an idea which ones you can't do please bring them to dgoulet and asn tomorrow 23:46:05 I'm also happy to take on what reviews I can; I'm done with my reviews for the week, and can pick up stuff, so long as I didn't write it. 23:46:12 next topic is rotation updates. 23:46:37 I'm bug triage this week; what's the status, mike? 23:47:00 * ahf is CI+coverity and i've seen there was a small new coverity CID opened today/yesterday 23:47:20 teor: very nice description on the meeting pad for the handover btw, thank you for doing that 23:47:27 gaba: ok, I can do that by EOD tomorrow (depending on state of experiments wiki page) 23:47:34 ahf: I hope it isn't too much info. 23:47:54 gaba: (by which I mean I'll work on the wiki page tomorrow, and let you know how it looks and take a guess at how many reviews I can do 23:48:00 teor: i think it's good, gives a much better overview than i've felt i had before 23:48:07 gab: on Thursday 23:48:18 thanks mike 23:48:40 mikeperry: do you have any status on the bug triage from last week? 23:48:47 there is a lot of comments int he pad about it 23:49:04 gaba: yeah it's in the pad 23:49:27 ok, is that enough nick for this week? 23:49:42 nick? 23:49:46 I mean I feel like this role transition is forcing us to do role-knowledge-transfer each weeek.. I leanred that I wasn't sure what our current preffered support page is 23:49:50 and about CI is from teor to ahf 23:49:53 I guessed tor.stackexchange.com 23:49:59 and that is noted on the pad 23:50:03 among othere things 23:50:06 I think we don't have a great one. We could ask the community team what they recommend 23:50:15 yes, it seems there is always a learning :) 23:51:04 next is 0..0 status 23:51:18 0.4 23:51:39 mm, did I miss coverty? 23:51:55 coverity and CI is same 23:52:00 ohh, hehe 23:52:01 ok 23:52:03 :-) 23:52:14 same person 23:52:15 nice 23:52:16 ahf: ping me tomorrow about coverity status ? I have ideas about the newer coverity issue. 23:52:23 The other old coverity issues are waiting for code review 23:52:36 hey, would anybody think it would be OK if i spend some time this week trying to do a thing where i create a ticket automatically on trac when i see appveyor, travis or jenkins fail? 23:52:45 everybody ok about what needs to be removed from 0.4.0 23:52:52 ahf: how do you mean? 23:52:55 nickm: i will, there was a new item yesterday too 23:52:56 +1 ahf, that seems good 23:52:56 mikeperry: I have been trying to make transitions easier by creating wiki pages for each role. But I can only do one wiki page every week or two. 23:53:12 nickm: like pull info in a cron from appveyor/travis/jenkins and create a ticket once one of them goes red 23:53:15 ahf: that sounds like a great idea! as long as it doesn't make too much noise on transient failures 23:53:15 mikeperry: let's talk about roles on the network-team list, or at the July meeting? 23:53:27 catalyst: agreed 23:53:44 july meeting +1 23:53:48 ahf: or maybe that will be a reason for us to shut up or fix the nondeterministically failing tests? 23:54:01 teor: ok 23:54:09 catalyst: hah, maybe :-S let's brainstorm a bit about this over the weekend, i think you will have some good feedback for this 23:54:59 ahf, catalyst: I tried creating a ticket or ticket comment every time I saw a transient CI failure. There should be 1-2 per week right now. A few weeks ago it was one daily. 23:55:00 ahf: sure, i'd be happy to talk more about it later (though why the weekend?) 23:55:13 teor: yeah, i actually think this is a good idea 23:55:22 catalyst: err, sorry, i'm very tired. i meant over the week :-S 23:55:35 treating intermittent failures as bugs was really helpful 23:55:54 we tag them with "tor-ci", I think? So we don't accidentally re-create? 23:56:03 * gaba needs to run to get kid from school... 23:56:16 gaba: see you tomorrow! Say hi to the kid! 23:56:29 good idea with a keyword also for handover 23:57:10 nickm, ahf: tor-ci-fail 23:57:13 #action talk to community team about what to say to people who put support requests on trac 23:57:17 teor: thanks 23:57:32 teor: ack 23:57:34 tor-ci has been used for every CI feature and ticket, so it doesn't help in queries 23:58:28 #action talk about roles and role transitions at the July meeting (or on the network team list) 23:59:01 looks like we talked about reviews 23:59:12 teor makes a good point about splitting up the pad 23:59:38 I think that's somethign we could do via trial-and-error -- would everybody be okay with me just trying to do it for next week, and we see how it works? 23:59:44 +1 00:00:32 Since teor is about to go away, let's use the rest of this meeting for their most important handover stuff. 00:00:51 teor: (when are you planning to be back? My apologies; I have bad memory for that stuff) 00:00:52 nod 00:01:10 May 21 00:01:13 ack 00:01:40 teor: have a very nice leave! hope you can relax and re-charge all the batteries :-) 00:01:45 Thanks! 00:01:57 yeah; I hope you have a great time and many awesome days 00:02:27 Here are my high priority things: 00:02:40 I talked with juga about blocking sbws merges until I get back. Because we really need a stable sbws, now it is deployed on 1-2 directory authorities. 00:03:01 I can't see any other way to do a handover and make it work right now. 00:03:20 Is it "stable enough for now"? 00:03:23 what's the status? 00:03:33 Yes, it is stable and functional. 00:03:56 We need to improve the number of measured relays before we deploy to a 3rd authority. 00:03:59 But that is delicate work. 00:04:04 proposal: let's try to find a couple of people to work on sbws stuff, but not merge unless emergencies come up. 00:04:09 +1 00:04:24 #action let's try to find a couple of people to work on sbws stuff, but not merge unless emergencies come up. 00:04:42 I don't think adding more load to the team is a good idea right now, so our best option is slowing sbws and other non-funded work. 00:05:42 Next item 00:05:45 Who will do urgent CI backports? 00:06:02 I think that's nickm? 00:06:03 We can just block other backports until I get back. 00:06:07 As in, "0.2.9 CI is broken, we must backport?" 00:06:11 Yes. 00:06:29 Which should only happen if Travis changes. 00:06:34 I think that's me, though I would also consider not backporting anything but critical security issues 00:06:49 I agree 00:07:06 0.3.5 and later are affected by the stem failures, if we fix the tor_mlockall() bug, we should backport that to 0.3.5 00:07:31 ack 00:07:34 But maybe we should test it first, so that might mean disabling stem in 0.3.5 and 0.4.0? 00:08:45 I think it will depend on what the issue turns out to be. 00:08:52 Fair enough 00:09:03 I'll try to muddle through? 00:09:10 As we all do 00:09:25 As I told Roger once, the cost of delegating to others is that they will not do it the same way as you would. :) 00:09:34 I think you'll be better at mlockall() than I will be 00:09:37 Indeed. And that's ok. 00:09:59 I don't want to do reviews or rotations until the week of 27 May, because 21 May is a short week filled with backlog. 00:10:14 makes sense 00:10:23 And that's about it, apart from PrivCount. Which I think nickm and I should talk about in tor-dev. 00:10:28 ok 00:11:34 Do we have anything else to talk about? It's 10 minutes past the hour. 00:11:56 It looks like there are no other discussion topics, other than juga's questions. I'll try to answer them if you don't get to them before you go? 00:13:00 hearing no other topics? 00:13:23 * ahf is good 00:13:23 thanks, everybody! It's stressful times, but we're awesome programmers and we'll make it through together. 00:13:30 o/ 00:13:33 There's nobody else I'd rather be working with 00:13:36 #endmeeting