16:59:51 #startmeeting Network team meeting, 19th october 2021 16:59:51 Meeting started Tue Oct 19 16:59:51 2021 UTC. The chair is ahf. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:51 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:59:53 hello hello 16:59:59 o/ 17:00:01 hi everybody! 17:00:07 o/ 17:00:12 our pad is at https://pad.riseup.net/p/tor-netteam-2021.1-keep 17:00:58 let's start by looking at our team dashboard at https://gitlab.torproject.org/groups/tpo/core/-/boards 17:01:15 eta: here we all just take a look at the board for ourselves and often use the search function to limit the board just to our own stuff 17:01:36 * eta nods 17:01:43 so for example, searching for Assignee = ahf and then i check if everything is alright 17:01:55 once you start being assigned to tickets you will quickly get into the flow here 17:02:12 does everybody's boards look OK? 17:02:20 good now 17:02:35 dgoulet: i added Doing to a few things earlier for you in my triage session with gaba 17:02:39 based on our earlier release meeting 17:02:40 yeah, I think so. We're going to have to rearrange all the tickets for arti 0.0.1, but that is probably best done at the arti meeting tomorrow 17:02:49 ahf: I just moved one thing, it is all good 17:03:06 nickm: sounds good - have you told eta about the arti meetings? i don't think access to nextcloud is there yet 17:03:17 * eta has not been informed about this 17:03:46 eta: we have a bi-weekly (i think it is) sync on everything arti where we also sometimes have some external parties in 17:03:53 let me find the time tomorrow 17:04:16 is at 15 UTC 17:04:25 ack 17:04:33 PM'ing you the pad for it 17:04:38 ...is there an ical feed I can import with these, ooi? 17:04:56 yes, when you get access to nextcloud 17:04:57 :-/ 17:04:58 ah right 17:05:04 then all of the orgs meetings are in different calendars 17:05:07 neato 17:05:18 yeah, it is sometimes a bit chaos, but usually it works well 17:05:19 btw, we have been doing the arti meetings as recorded video calls that we post on youtube. We've been doing them that way, but now that the team is expanding, we can change how we do it if you want. 17:05:52 ya, good point 17:05:59 * eta doesn't really mind that 17:06:08 ok, we'll keep it up 17:06:31 ok, that was boards 17:06:50 release status 17:06:58 dgoulet and i are working on preparing tor.git releases for next week 17:07:07 went over some issues and MR's today with backport labels on 17:07:16 i think david got his things merged, i am missing one issue and one MR 17:07:29 otherwise i think we are OK there 17:07:42 what's your timeframe on the changelogs? I'd like to suggest doing the 047 changelog first, then getting it edited, and only then doing the changelogs for older releases 17:07:55 that way if there are fixes on the 047 entries you don't need to backport them more than once 17:08:02 maybe we'll dive into it this week, maybe we'll dive into it on monday 17:08:12 ack 17:08:54 ya 17:08:57 not very strict there 17:09:04 ok! 17:09:16 we haven't gotten anything new in for our tables from any other teams 17:09:29 EXCEPT from health team where there is an issue with metricsport and dns handling that dgoulet is onto 17:09:36 which is part of the work for next week's releases 17:10:22 ok, we have no announcements for today 17:10:23 do you think that will be difficult/risky and/or need testing? 17:10:35 it will need some testing with an exit node i think 17:10:46 dgoulet: ^^ 17:11:11 not risky, testing yes 17:11:16 It might make sense to have a continue/defer decision on thursday or friday then. You might decide to delay the release if needed. 17:11:31 or not, if the risk is low enough 17:11:34 once we get the patch, we'll be in that process 17:11:41 great 17:11:41 ya, for sure, we'll probably do a release status on our thursday meeting anyway 17:12:27 ok, we have an excellent discussion item from nickm which is related to last meeting's discussion item 17:12:35 2021-10-19 [nickm] Maybe transition team updates to forum/blog? (Since nobody is reading this...) 17:12:44 this is related to the status updates we sometimes do in this meeting pad 17:12:57 last time we put in a small message at the bottom saying "if anybody reads this please prod ahf on irc" 17:13:07 and nobody did, which either means people wont PM me or nobody reads the status messages except us 17:13:09 yup. Basically, we've been sending out copies of this meeting pad, along with links to this meeting log, to the tor-project@ mailing list. (IIRC) 17:13:31 we no longer sent out things to tor-project@ after i did the same thing with "please prod ahf if you read so far" in a few of them 17:13:37 nobody reads them 17:13:44 except for us maybe 17:13:45 So those updates aren't doing a good job of keeping anybody informed about our activities 17:13:51 i agree 17:14:20 so, i think i have a pretty good idea about the technical stuff we do each week and i could gather this in a summary that y'all just approve instead 17:14:25 We should come up with a better way to let everybody know what we're up to. I do find the pads useful for organizing my thoughts and todo lists... 17:14:30 but what i'll miss from these updates is all the things people do that isn't "direct engineering" 17:14:33 like if you go do a talk on tor 17:14:38 or write a blog post about community things 17:14:43 yeah 17:15:07 nickm: what about we just keep a big list we add things to? or is the part that keeps you well the part where it's specific to you? 17:15:20 I'd be fine with a 'big list' too 17:15:24 we could do it per project? arti, tor, shadow, ... 17:15:28 ok! 17:15:44 how about i try to come up with a format for this and then we try something else, then we could do "This month from the network team" updates to ML's/blogs ? 17:15:46 we could have a section that we edit, review, and post after the meeting? 17:15:50 yep 17:15:56 great; that would rock 17:16:03 but where i try to pre-fill it with what i have observed maybe 17:16:09 up to you 17:16:15 ok 17:16:16 excellent 17:16:25 i think we should do that too, then i also think this may have some values for people other than us 17:16:43 i'll try to get something ready for next monday then 17:17:06 do we have anything else to talk about today? 17:17:17 or does people wanna return to vim/emacs/vscode/... ? :-) 17:17:37 (intellij-rust, I'll have you know :p) 17:17:42 ! 17:17:44 that is a new one 17:17:44 quick note -- i've added a couple of items to the arti meeting pad for tomorrow 17:17:54 nickm: excellent, i'll join it too 17:18:07 nothing revolutionary, but important to figure out 17:18:20 ( That meeting pad is at https://pad.riseup.net/p/arti-meeting-pad-keep ) 17:18:34 perfect 17:18:37 and I think that's it from me. 17:18:42 Also did we formally welcome eta? 17:18:46 Welcome eta, formally! 17:18:51 we have no s61 section of the meeting today 17:18:53 * eta is formally welcomed 17:18:56 :) 17:19:27 yes, welcome to the team, eta! feel free to prod any of us if you have any questions. we probably do things very differently from elsewhere, but we also open to suggestions for feedback on processes and pretty much everything :-) 17:19:46 ahf, noted, thanks! 17:19:49 i am gonna call the meeting and we can return to what we were doing before :-D 17:19:52 #endmeeting