16:59:39 #startmeeting Network team meeting, 25th october 2021 16:59:39 Meeting started Mon Oct 25 16:59:39 2021 UTC. The chair is ahf. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:59:42 hello hello o/ 16:59:48 o/ 16:59:52 o/ 16:59:58 hihi 17:00:07 our pad is at https://pad.riseup.net/p/tor-netteam-2021.1-keep 17:00:14 o/ 17:00:20 and i hope people are not scared of the new area for submitting "status updates" 17:00:34 it won't be perfect, but we'll try it out for a bit and modify it and maybe even find something entirely different :-) 17:00:41 o/ 17:00:57 eta: want me to add the stuff you did last week to the status section for arti, or would you like to? 17:00:59 jim's out for today 17:01:20 nickm, go ahead, just so I get an idea of the format, and I'll do it next time, maybe? 17:01:25 ack 17:01:57 juga + geko: you're also very welcome to add exciting updates on sbws to the pad if you want. we'll try to publish them as monthly updates from the team on our new interactive web-based forum! 17:02:19 ok, how are people's dashboards looking: https://gitlab.torproject.org/groups/tpo/core/-/boards ? 17:02:54 almost empty! , crazy stuff 17:02:59 hrm 17:03:10 ahf: there is no general s61 part anymore? 17:03:22 dgoulet: then you win at work and get to retire early 17:03:26 empty, but that's unsurprising :p 17:03:31 but we pick the topics like "congestion control"? 17:03:39 although I have MRs now 17:04:00 GeKo: yeah, it's just general headlines there. not related to a specific sponsor in this case because our users (the readers of these posts) shouldn't have to care much about the sponsor 17:04:14 perhaps the s61 objectives should all be their own headline? 17:04:17 okay, and the personal updates sections we had? 17:04:19 eta: very nice, this is mostly for ticket assignment, so once you start getting tickets you can dive into those 17:04:31 GeKo: no personal updates, only things you think should be broadcasted here 17:04:31 ack 17:04:38 mikeperry: they have a CC headline 17:04:39 k 17:04:54 on line 208 17:04:59 let's see then 17:05:14 ya, i do not expect this to be without a bit of chaos 17:05:36 also feel free to add important headlines that you want to track over some weeks, that is fine 17:05:42 i just added the most obvious ones from my own notes 17:05:47 aha, good 17:05:50 no worries 17:06:07 the important thing is that people try to write in a way where they know the reader is our users and people who care about the community 17:06:10 not the other team members alone 17:06:26 ok! 17:06:30 boards looks alright from what i can tell 17:06:52 david and i are okay on track with the many releases this week. roger is helping a bit with reading over the changelog work david did this morning 17:07:51 it looks like we are doing OK with tickets from other teams. there is some updates to already existing tickets over the last week, but nothing new 17:08:11 ok, we have one discussion item from what i can tell which is an evergreen discussion item 17:08:47 it's soon time to change our clocks for all the stupid reasons in the world, so we need to figure out if we decide to stick to UTC (and have a different meeting time in our own TZ's) or if we want to shift it again 17:09:09 i am usually on the team that prefers sticking to the UTC timestamp, but if it causes troubles for others i also think we can move 17:09:11 UTC++ 17:09:18 * eta is also on team UTC, given that her local time will become UTC :p 17:09:19 you want to go to UTC + 1, nice 17:09:21 ;-p 17:09:34 eta: :-D 17:09:50 all my clocks are on UTC. I have no idea what the sun does anymore, let alone what time my government thinks it is 17:09:51 In the past we decided that we'd keep our team meetings relative to US time, but I don't actually mind either way. 17:10:07 it would be much easier to coordinate everything if we keep utc 17:10:17 but it's a bit further in the past right? i think we have been at 17 UTC for these meetings at least since april 2020 17:10:22 I am okay with changing to UTC if we promise not to argue about it again when the clocks change again :) 17:10:30 :) 17:10:31 LOL. not gonna promise that 17:10:46 UTC forever 17:10:56 ok, it sounds like people want to stick to UTC. we need to hear a bit what other teams do too of course since we sometimes overlap with each other 17:11:13 ok! 17:11:19 * hiro likes sticking to utc 17:11:35 we are at the end of the agenda-driven meeting and now need to move to the mikeperry-driven s61 part \o/ 17:12:26 oh boy. yeah so we are struggling with sim results in s61 land, mostly from trying to reduce the need for artifacts 17:12:38 yeah! for s61 people please remember to review/add/edit the pad for the report https://pad.riseup.net/p/sponsor61-next-report 17:12:41 I have been working on log scraping tools for sims, jim is trying to play with gitlab storage in shadow 17:13:23 oh yeah, and I went over that report with gaba. I added some things for geko's objectives but should be looked ovewr 17:13:42 ya, it's nice to see how many different teams involved in building this setup also for future use \o/ 17:14:45 hiro: I am trying to go over the artifacts for the runs we have data for. we should talk after about trying to run your tornettools patch(es) on them 17:15:08 sounds good mikeperry 17:16:40 dgoulet: do you have a new ticket for the DNS issue? I never got the fwd'd mails you mentioned 17:17:10 mikeperry: not yet figured out 17:17:16 mikeperry: still talking to toralf about it 17:17:21 ok 17:18:33 GeKo,juga: have anything for sbws/network-health? 17:19:15 mikeperry: not that i can think of, GeKo ? 17:19:28 for sbws not really 17:19:44 we still try to get gabelmoo onto sbws 17:19:53 not exactly sure where we are here 17:20:03 for the health part 17:20:09 (waiting for gabelmoo to see how it progress) 17:20:20 i am done with my overload scripts 17:20:34 and juga is reviewing them 17:20:45 i continued to poke relay operators with fd related overload 17:20:54 we shuld see some drop in the graphs soon 17:21:10 nice 17:21:15 as almost everyone i conacted said they fixed their stuff 17:21:26 and they were happy that i did :) 17:21:43 i started some analysis in https://gitlab.torproject.org/tpo/network-health/team/-/issues/66 17:22:06 i think that's the main thing i worked on last week 17:22:13 i thnk we are good here 17:22:29 there are still rough edges 17:22:40 but we'll monitoring how this goes 17:22:44 in the coming weeks 17:22:52 and then address remaining issues 17:22:54 ok 17:23:45 we good? 17:24:27 yeah I think so 17:24:28 ... we silent at least 17:24:31 awesome 17:24:32 >_< 17:24:33 let's call it then 17:24:38 :) 17:24:57 thanks all for joining the meeting. please give feedback to the new status reporting idea in the next few weeks and we can evaluate if it makes sense over time 17:24:59 thanks o/ 17:25:01 #endmeeting