15:59:48 #startmeeting network-health 04/11/2022 15:59:48 Meeting started Mon Apr 11 15:59:48 2022 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:54 okay, let's get started 15:59:58 welcome everyone 16:00:06 hello o/ 16:00:11 our pad is at http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-nethealthteam-2021.1-keep 16:00:33 please add your updates in case you have some 16:00:42 so we are all on the same page 16:00:54 hi! 16:01:02 hiro: juga: ^ 16:01:10 o/ 16:03:20 okay 16:03:27 i've marked one item as bold 16:03:42 i'll be offline a bit starting from wednesday this week 16:03:47 until including next monday 16:04:06 given that day is a public holiday where i live 16:04:20 i expect that this holds for a bunch of other places, too 16:04:32 so, should be just drop the weekly sync next week? 16:04:42 or more it to a different day? 16:04:47 what's the feeling? 16:05:00 +1 on droping the meeting next week 16:05:06 some other people will be afk too 16:05:13 yep sounds good 16:05:16 yes 16:05:23 so 04/25 it is then? 16:05:49 i can write an email to tor-project after this meeting 16:06:01 ok 16:06:15 nothing else seems highlighted 16:06:45 i think ggus you can go with the relay ops expectation document 16:07:17 great! 16:10:09 * GeKo wonders whether ggus is still typing... 16:10:49 sorry, i had someone knokcing on my door 16:10:51 i'm back 16:10:53 https://gitlab.torproject.org/tpo/community/relays/-/issues/18 16:11:06 thank you, GeKo 16:11:07 is the ticket for everyone's reference 16:11:26 no worries 16:11:30 how can we help? 16:11:49 i think for the version 1.0, we can incorporate some of the suggestions that people made on the comments 16:12:19 yeah 16:12:26 where should that thing live? 16:13:12 it would be great to have a place where people can still comment on that version 16:13:22 or a link to where people can suggest any change 16:13:42 https://community.torproject.org/relay/expectations-for-relay-operators 16:13:45 i agree 16:14:00 gaba: people can send a merge request or comment on the ticket 16:14:20 ggus: you want that ticket to be open forever? 16:14:27 heh 16:14:33 i was about to ask the same :) 16:14:54 people can open a new ticket on web/community 16:15:01 like all the other documents 16:15:01 wfm 16:15:06 ok 16:15:16 let's add a note to the agreement at the bottom saying that 16:15:20 where people can make suggestions 16:15:52 only the idea of ethernal tickets makes me uncomfortable :) 16:15:53 and we should point that out when announcing that document on tor-relays@ etc. 16:16:34 ggus: how fast do you plan to get this document up? 16:16:47 gaba: what's the concern about this document? all the docs in community.tpo can be edited or changes can be suggested on web/community 16:16:56 if you scroll down, there is an edit button 16:17:05 and it will create a merge request on web/community 16:17:42 it would be good that everybody reading that document has a clear idea that it can be commented by the community 16:19:18 GeKo: this week i can take a look on the text and then open a merge request next week 16:19:35 okay 16:19:45 i can then look over it next week if you want 16:20:01 sounds good! 16:20:21 if there is anything you need from me for that until then it's tricky 16:20:40 as i essentially only have tomorrow to work on it for this week 16:20:50 and tomorrow is already quite packed :) 16:21:04 but let me know regardless and i can try 16:21:30 ok! 16:22:01 is there anything else for the relay expectatons doc we should hash out here? 16:22:20 or are we good, ggus? 16:23:19 it's good 16:23:27 gaba: seems ggus is good we could chat a bit about Q2 net-health work 16:23:32 okay 16:24:45 ok 16:24:48 sounds good 16:25:07 mostly we need to go over the backlog column and see what we can keep in q2 and what we move forward 16:25:24 could you share the link you are looking at? 16:25:32 i see this issues marked as q2 but it seems that it may be q3 by our discussion? https://gitlab.torproject.org/groups/tpo/network-health/-/issues?scope=all&state=opened&label_name[]=Q2&label_name[]=Roadmap%3A%3AFuture 16:25:45 yes, im looking at https://gitlab.torproject.org/groups/tpo/network-health/-/boards 16:26:46 * gaba wonders if this can be done over text 16:27:08 heh 16:27:23 i can just adjust the tickets in the first link 16:27:42 ok 16:28:41 okay, adjusted 16:28:52 there are only three tickets that should move to Q3 16:29:14 ok 16:29:17 let me see 16:30:46 geko: if this is the last topic for the net health meeting maybe we can jump into bbb and discuss those tickets in backlog 16:31:03 yeah 16:31:06 fine with me 16:31:15 do we have anything else on our plate for today? 16:31:43 not from me 16:32:08 hearing no one shouting i gonna close the meeting. thanks everyone 16:32:11 #endmeeting