17:00:46 #startmeeting Network July 6th 17:00:46 Meeting started Mon Jul 6 17:00:46 2020 UTC. The chair is gaba. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:54 hello hello 17:01:06 pad is here: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-netteam-2020.1-keep 17:01:19 ahf: o/// 17:01:50 XD 17:01:54 hope you all are doing well! 17:02:02 let's start with the lovely board https://gitlab.torproject.org/groups/tpo/core/-/boards 17:03:12 asn: are you working on tpo/core/tor#33704 17:03:25 * asn looks 17:03:31 gaba: quick question on the lovely board -- if I filter it to only show tickets assigned to me, is that reasonable for the purposes of this meeting? 17:03:34 my screen is not wide enough for moving things from the Open to Doing ehehe 17:03:40 nickm: i do that too :-S 17:03:48 nickm: totally reasonable 17:04:13 ahf: what you need to move? 17:04:18 gaba: no. im removing it from my doing. 17:04:32 ahf: we should move back the s28 and s30 into backlog while you are not working on them 17:04:35 asn: ok 17:04:39 wrt doing, i predict im gonna be busy all this week finishing up 044 and reviews before i go on vacs. 17:04:44 ahf: go fullscreen and zoom out? :) 17:06:24 i have solved it by zooming out, collapsing the left hand sidebar 8) 17:06:27 all is good 17:06:36 gaba: let me do that 17:07:10 done 17:08:01 asn: those 2 issues you have in the backlog is not something you are going to do this week, right? 17:08:07 * asn checking 17:08:16 they are 044-should 17:08:39 they are 17:08:55 i took them in the thursday meeting 17:09:03 and will attempt to do them this week 17:09:11 should i move them to "doing"? 17:09:21 ok 17:09:26 i moved them to next 17:09:36 kk 17:09:51 ok, anything else about that board? 17:10:05 * ahf good 17:10:19 Next we have the reviews. How reviews from last week worked? Any blocker? Assigments? 17:10:36 i did not assign reviews today 17:10:42 but will do so later today or early tormorrow 17:11:01 oh damn forgot about that :( 17:11:02 looks like all our merge requests are assigned, but not sure about needs_review tickets 17:11:03 asn: ping me when you can 17:11:47 for needs_review tickets that aren't merge requests, when you assign them, could you let people know about merge requests? :) 17:11:52 dgoulet: pinged u 17:12:04 nickm: ack 17:12:20 thanks 17:12:53 ok then 17:13:16 * ahf needs to get a personal board for tor too. i keep using lists for everything 17:13:33 about 0.4.4 status, did you all talked about it on Thursday? 17:13:51 i think so? 17:14:06 we have the must/should tickets assigned 17:14:14 the can tickets are in icebox 17:14:31 ye 17:14:32 tpo/core/tor#7193 is a special case, since it's needs_revision 17:16:24 * gaba trying to figure out who needs to revise 7193 17:17:58 do we have the author of 7193 in gitlab? 17:18:00 volunteer that dropped that somemonths ago :S 17:18:08 "maurice_pibouin" 17:18:14 hmmmm 17:18:20 that is a person i have communicated with 17:18:34 do they have an account? 17:18:50 i think so, let me just look 17:19:07 yes, they are created *after* the migration 17:19:09 same username 17:19:24 https://gitlab.torproject.org/maurice_pibouin 17:19:32 we can not assign them the issue because they are not in the team, right? 17:19:37 I'll ask if they have time to revise it? 17:20:02 ok 17:20:11 and then we figure out how to assign them the issue 17:20:44 done 17:20:50 i think *we* can, but they can't do it themselves 17:20:59 ahf: i didnt see how 17:21:04 hmm ok 17:21:18 they do not come up in the list of users to assign the issue to 17:21:50 try "/assign @foo" ; not sure if that will work though... 17:21:58 but for now, please don't, unless they show up and agree to do it 17:22:20 maybe just higlight them and ask? 17:22:27 it seems it works :) 17:22:34 yes, i will remove 17:22:45 ahf: I think I did on the ticket? 17:22:57 yes 17:23:29 yep, sorry, i was looking in the admin tab of my browser and not the refreshed one from @ahf 17:23:31 is good 17:23:39 ok, the next item in the pad is about updating the fallback list 17:24:57 who added this item to the discussions? 17:25:12 me 17:25:31 quick question -- on thursday, we were going to ask somebody if they had time to do the communiction side of the fallback update 17:25:34 was that gus? 17:25:37 if so, did somebody talk to gus? 17:26:13 I have not 17:26:16 still on my list 17:26:21 ok 17:26:26 I was off friday so I didn't do it since Thur :( 17:26:45 no worries, just wanted to make sure somebody had it 17:27:56 ok, nothing else for me 17:28:01 ok. Anything else for today? 17:28:08 * ahf has none 17:28:15 just a quick note - 17:28:32 the main development branch for shadow is now in the public repo, named 'dev' 17:28:40 woh! 17:28:53 oh yeah! 17:28:55 nice 17:29:00 :) 17:29:02 jnewsome: nice milestone reached :) 17:29:11 it is still in the github project? 17:29:27 well, it's still very much 'dev', but nice not to be splitting the work into a private repo 17:29:35 yeah, I'll grab the link 17:29:56 Here's the dev branch: https://github.com/shadow/shadow/tree/dev 17:30:01 yeah, looking at it now 17:30:02 very cool! 17:31:47 jnewsome: nice :))) 17:33:04 :-D. It doesn't run Tor yet, so mostly only of interest if you're interested in seeing or poking at the new arch 17:34:18 Right now we're at the point where we can run some realistic-ish but still simple benchmarking, so we're iterating there on performance before expanding the implementation 17:34:19 well i was thinking of it for the v3 metrics thing 17:34:28 but i guess this is not the thing to use yet 17:34:34 nope, not yet 17:34:55 ack ack 17:35:59 pretty neat 17:36:12 do we have anything else for this meeting? 17:36:14 * asn ugh phone bbiab 17:36:58 * dgoulet is good 17:37:18 * jnewsome is good 17:37:29 ok. gaba -- time to #endmeeting? :) 17:37:32 sounds good. I'm going to close the meeting then 17:37:35 #endmeeting