15:59:24 #startmeeting network-health 01/10/2022 15:59:24 Meeting started Mon Jan 10 15:59:24 2022 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:30 okay 15:59:59 welcome to the first network-health meeting in 2022 16:00:07 o/ 16:00:17 our pad is still in 2021, which is okay :) 16:00:19 http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-nethealthteam-2021.1-keep 16:01:00 please add your items there 16:01:15 we can change it later to a timeless pad 16:01:26 timeless efforts, yeah :) 16:02:02 ggus: ^ 16:02:15 in case you are around and there is something to sync from your side 16:02:59 so, from my side: i am still mostly on tor browser work this month 16:03:14 but that should be done by the end of january and i can finally come back to network health land 16:03:39 i'll do all the important thins, though, like regular meetings/1:1s/roadmap work 16:03:50 or help with sponsor work where needed 16:04:00 *things 16:05:23 hiro: i am doing the reviews on my plate this week in case there is still stuff to do 16:05:25 hey 16:05:47 yes GeKo hold on on that review in collector I am able to do a few test 16:06:14 I will update the ticket with the actual sleeps times that allow us not to have missing descriptors and the theories behind those missing descriptors too 16:06:18 i think we can talk about website!13 in our 1:1. right now there might only be confusion left while the techical parts are done 16:06:27 :) 16:06:31 ack 16:06:40 yes sounds good! 16:06:51 better to chat about that in the 1-1 16:07:14 i think that's all from my side 16:07:20 same for me 16:08:26 ggus: https://gitlab.torproject.org/tpo/network-health/team/-/issues/131#note_2768717 is for you :) 16:08:38 but otherwise, as i said there is not much going on 16:09:22 0.3.5.x gets EOL in 3 weeks 16:09:47 and there is probably not much need to wait after that until we start to bug operators about upgrading 16:10:15 given that there is both a newer lts version available and a newer "regular" stable, too 16:10:45 but i want to chat with network team folks here first about what to do and what the general policy should be 16:11:52 GeKo: you can close #131 16:11:56 but, regardless, dealing with that eol version wilj be something that is coming soon-ish either way 16:12:00 great, thanks 16:13:02 done 16:13:21 ggus: gaba: anything else from your side? 16:14:01 GeKo: yes 16:14:19 go ahead 16:14:28 i'm hitting this bug: https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40018 16:14:37 when counting how many new bridges we have 16:15:08 for example, who joined the network because of/after the 'run a bridge' campaign 16:15:27 uhm that's a bug that I am not sure where it comes from... how many bridges do we have like that? 16:15:43 I have actully had a first look at the ticket when I opened it 16:15:56 I think I will have to do some test in onionoo 16:16:07 by parsing the descriptors 16:16:52 it might be just an old bug in the code that we found out about now 16:16:58 or it might be something else 16:17:21 hiro7[m]: i will check again today 16:17:43 I will try to parse a few descriptors 16:17:48 will put that up for this week 16:19:08 hiro7[m]: i will check today again and i will ping you 16:19:24 gus[m]: no worries I can also find out the actual numbers 16:19:35 I thought you had it handy 16:20:09 added it to my list: https://gitlab.torproject.org/-/snippets/121 16:20:16 thanks 16:21:23 thanks hiro7[m]! 16:21:49 okay, i guess we are done here then? 16:22:16 thanks everyone and have a nice week 16:22:18 #endmeeting