17:00:08 #startmeeting network team meeting, 24 June 2019 17:00:08 Meeting started Mon Jun 24 17:00:08 2019 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:12 Hi, all! 17:00:20 The pad is at https://pad.riseup.net/p/tor-netteam-2019.1-keep per usual 17:00:52 Who is here today? I know that this is a holiday in Quebec, and I think some people might be returning from Moz allhands... 17:00:58 o/ 17:01:00 (or recovering from) 17:01:06 hi catalyst ! 17:01:11 hello o/ 17:01:15 o/ 17:01:24 hi! Looks like we are 4 today 17:01:33 unless asn or mikeperry is secretly here :) 17:01:59 I am here, oops forgot to updte that line :) 17:02:05 :) 17:02:07 oh. Hi, mike! 17:02:54 First issue is CI. Any updates there? 17:03:00 nope 17:03:15 great. next is 041. 17:03:52 let's take a minute here, since I'd like to get 0.4.1.3-alpha out today 17:03:57 the status page is https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases/041Status 17:04:38 mike, status on #30649 ? 17:05:31 everybody: are any of the "owner: (none)" items at the top of the page things that we *need* to do before we can call 0.4.1.x stable? 17:05:37 oh I havew to check out asn's commit on that still 17:06:17 mikeperry: will you have time to do that early in the week or should it wait for 0.4.1.??? 17:06:26 err, I mean 0.4.1.___ 17:07:45 I can do it right now/right after the meeting 17:07:55 ahf: do you think you could take a quick look at #30956 as well? I'd like to mege it today if possible, but I can't do that if I'm the reviewer. 17:08:10 If you sign off on it too I could merge it today, and put it in 0.4.1.3-alpha 17:08:13 mikeperry: thanks! 17:08:49 yes, i can do that 17:08:54 i can do it right after the meeting 17:09:08 ahf: thanks! 17:09:24 then I should be able to get 0.4.1.3-alpha out in the next 24 hours, barring misadventure 17:09:47 It is sounding like nothing else is blocking on 0.4.1. I'm going to triage a bit later this week in that case 17:10:02 next up is the roadmap kanban. Any updates there? 17:10:07 * nickm loads it... 17:10:35 next up would be code review, but I do not think we will have assignments till tomorrow 17:12:26 catalyst: do you want to talk about the status of #29211 subticket reviews after this meeting? 17:12:50 * nickm moves a few completed tickets around on the kanban 17:12:59 thanks 17:13:36 on announcements: please remember to look at the links there 17:14:30 nickm: maybe around 15:00 EDT today? 17:14:35 catalyst: wfm! 17:15:12 on discussion: please remember that the retrospective is Thursday. Like last time, we'd like everybody to show up with a short list of +1 / -1 issues to add to the pad. 17:15:29 yep 17:15:46 please +1/-1 on the network team meeting pad for which meeting modality you prefer 17:16:22 On the stuff about archive.tpo anarcat was asking if somebody from the network team can help with coordiante it. #29697 17:16:38 What would need to be done there exactly? 17:17:15 have somebody to access at the network team for when anything needs to be uploaded to archive.tpo 17:17:56 I'll reach out to anarcat to see whether this can be automated; previously we never actually did this manually. 17:18:11 ok 17:18:12 We just put source releases on dist.tpo, and the archive took care of itself 17:18:52 next topic is permanent CI role 17:19:07 there's a request for us to vote on that pad, but I don't see a place for us to do so. 17:19:10 about the permanent CI role, it is being shaped here: https://pad.riseup.net/p/network-team-draft-CI-role 17:19:11 actually this is for uploading things to archive.org (not archive.tpo) 17:19:12 did I miss it? 17:19:41 boklm: ah, ok. What do we need to do there? 17:19:45 nickm: i didn't add that. I want to be sure that everybody agree with this proposal and see when we can start with it. 17:20:22 nickm: adding options to the top of the pad 17:20:28 thanks 17:21:13 I think that we should also give the people in this role substantial latitude to define it and redefine it as suits them best. 17:21:24 but it seems good to me 17:21:28 nickm: I think having one person from network team with access to the archive.org account, and upload tor releases there 17:21:49 Yes. It makes sense. catalyst and teor will be doing it. 17:21:55 boklm: It can't be automated to mirror dist.tpo, like the old archive.tpo does? 17:22:49 network-team: okay, there is now a place to vote. Let's say that this becomes our policy starting monday if there are no strong objections. 17:23:00 nickm: I am not sure how much it can be automated. I think there is a command line tool to upload things, but I didn't look yet more closely how it works. 17:23:07 ok 17:24:24 I haven't heard anybody actually objecting to this proposal yet, so unless I missed that, I think we'll just get suggestions and a declaration that it's happening 17:24:40 boklm: okay, I'll volunteer to try to work on this 17:25:19 (I'm doing so on #tor-project) 17:26:03 any other discussion issues for today? If not, it might be an extra short meeting... 17:26:36 [coverity is still saying that it is "down for maintenance"] 17:26:41 i have a question 17:26:45 go for it! 17:27:18 what is the next step in the evaluation process you have been doing today? we get an email with our summary in and then we do 1:1's with you about it? or we talk in stockholm? or something third? 17:28:45 So I've been working on summarizing everybody's feedback. After that I'm going to work with gaba to make sure I didn't miss anything, and that the suggestions I'm offering are reasonable. Then we'll try to send it to everybody, and schedule 1:1:1s before Stockholm if we can, I think 17:28:52 gaba: does that sound right? 17:29:17 oki, cool! 17:29:24 yes! 17:29:35 It would be great to have everything before Stockholm. 17:29:52 I'm going to finish my drafts today, so I think that is doable. 17:30:46 cool! thanks 17:31:23 okay. Have we got anything else for this meeting? Or any other topics we should schedule meetings about between now and Stockholm? 17:32:02 It looks good. 17:33:00 okay. then let's call this meeting done, and have a great week! 17:33:03 peace all! 17:33:06 o/ 17:33:07 o/ 17:33:15 I'll be around most of the afternoon, if you need me for anything 17:33:16 #endmeeting