16:01:19 #startmeeting network-health 10/25/2021 16:01:19 Meeting started Mon Oct 25 16:01:19 2021 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:01:28 hello everyone 16:01:50 hello 16:01:53 time for a new [3~ network health meeting 16:01:54 o/ 16:02:03 hello 16:02:09 hello! 16:02:12 pad is over at http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-nethealthteam-2021.1-keep 16:02:17 hey! 16:02:33 please add things where needed (updates/discussion items etc.) 16:02:54 GeKo: newbie question — is there a link that works outside of Tor Browser? 16:03:03 yes 16:03:31 https://pad.riseup.net/p/tor-nethealthteam-2021.1-keep 16:04:08 hi! 16:04:21 o/ 16:05:07 GeKo: thank you! 16:05:17 ggus: you around by chance as well? 16:05:36 here 16:05:41 nice 16:06:24 i guess we can start while other folks are still adding things to the pad 16:06:47 maybe with you georgia[m] and irl about the website-redesgin? 16:06:51 *redesign 16:07:01 if so, please go ahead 16:07:24 GeKo: Yes — big thing there is that irl you should be getting a contract from us ASAP. it's ready, but I think just needs to get sent to you! 16:08:08 work has started on this looking at reimplementing the ggplot code using matplotlib, using the current statistics module to give the input data 16:08:13 ncie 16:08:26 We have been working on the synthesis and starting on design work. we shared a document out over email, and need to add some more to that and get into the design work 16:08:55 irl: do you have a ticket to track that work or a set of tickets? 16:09:00 \o/ 16:09:01 it would be good to see some of the design because right now we end up with just a copy of the original graphs but made with python instead of R 16:09:03 or some other place where one can follow along? 16:09:46 I think once we see the survey data and design information we will be able to put together specific tickets and we can track those in GitLab 16:09:56 irl: yes! we can get into a shared design doc this week 16:10:07 Awesome :) 16:11:11 nice 16:11:16 it would be great to have user stories around the use of the data too 16:11:18 sounds good (to both of what you said) 16:11:30 not sure if georgia[m] that is something you are doing 16:11:38 yes — we'll get that all organized into the document we started 16:11:52 we have content in a few disparate places at the moment and are unifying 16:12:30 Preliminary findings from survey: https://docs.google.com/document/d/1G4O-aROaIoSOmZF8KQoIT2oo7AVn9iyZGNcB3wrJsaY/edit?usp=sharing 16:12:49 are you sending further lnks around or is all supposed to be in the google doc at the end? 16:12:54 SusanKennedy[m]: We will keep adding to this document so that there's a hub of information and documents 16:13:20 and can update on email as we add to it 16:13:32 wfm 16:13:46 (works for me) 16:13:48 sounds good 16:14:24 Definitely not promising anything but it looks like visualising some data on a map would be a good idea… 16:14:42 georgia[m]: do you need some input/feedback for the stuff you currently have in the google doc? 16:14:54 or is that just a fyi? 16:15:01 irl: I could see a map as a good idea too :) but we just need to be careful what we show on the map, as people sometimes think maps say more! 16:15:20 GeKo: I think it's ok right now, let us add more and then questions/feedback will be good 16:15:25 it's very high level at the moment! 16:15:36 something that I will be looking forward would be understanding what is the best way to present the data - I mean understanding this from the users survey 16:16:22 something that I would intuitively expect (and I could be wrong) is that we have a set of people that will be looking for network data, a set of people that would be looking at geopolitical events and a set of people that will be looking at ways to link those 16:16:54 yes — exactly. 16:16:55 and also for us to keep an eye on the network health and work on censorship responose 16:18:22 georgia[m]: is all of the data you have evaluated in the spreadsheet 16:18:33 or is there stuff getting added to that one as well? 16:19:23 that is all the survey results that we are using. We have interview synthesis that's in a different document and we'll add it to the main google doc 16:19:43 okay, thanks 16:19:58 only thing we may do in the spreadsheet is some of the additional analysis that we mention in the google doc 16:20:11 but not new data 16:21:09 alright, do we have anything to add to that sync? anything that needs further discussion for the work in the week ahead? 16:21:24 or can we move on to the next topic? 16:21:49 I don’t have any thing else 16:22:14 all good here! 16:22:21 great 16:22:42 ggus: so, the eol work, how are we doing here? 16:23:00 i keep polling new relay ops to contact and write mails 16:23:16 and then act on replies where needed 16:23:41 i think the main question i have is one we think we should stop and just kick the remaining relays out 16:24:03 i still need to reply to one or two operators 16:24:28 i am not really happy to wait until 0.4.7 is stable and picked up by the dir-auths 16:24:59 so relays on old versions vanish "automagically" 16:25:07 how many EOL relays we have now? 16:25:16 because that will likely take nother couple of months 16:26:18 let's see 16:27:31 we started with 912 (12.24% of the network by weigth) like a month ago 16:28:06 and are now at 537 (6.43% of the network by weight) 16:29:02 do you want to give people one more month to upgrade and then in december we remove them? 16:29:22 back then when we kicked out < 0.2.9 we rejected more relays 16:29:58 with almost twice the weight 16:30:13 so it would not be too bad doing it now 16:30:16 but, yes 16:30:32 i think giving another 4 weeks or so sounds good to me 16:30:41 and then kicking the remaining relays out end of november 16:31:19 or if you want to do sooner, it's okay too. 16:31:46 i'll think a bit about it 16:31:58 the sooner the less work is on my plate :) 16:32:05 and we can close a ticket 16:32:09 win-win ;) 16:32:17 hah ok! 16:32:20 wfm 16:32:33 i thought about writing an update to the tor-relays@ thread 16:32:40 giving the final date for the kick out 16:33:01 maybe a bunch of operators get their act together that way 16:33:13 i can do that this week 16:34:02 november 22, before thanks giving 16:34:13 wfm 16:34:17 so people can use their holiday to upgrade their relay 16:34:47 wait you mean kicking them out on that day? 16:35:20 yes, but it was just a suggestion 16:36:10 okay 16:36:36 the thing is kicking them out on puts their fps on our reject list 16:36:45 and makes it *harder* to upgrade 16:37:04 because they need to change fps, too, or need to contact us getting the fps off our list 16:37:33 so, ideally, i guess that holiday for upgrading is happening before we kick them :) 16:37:42 but i'll think about it 16:37:54 maybe *after* thanksgiving would be a right time then 16:38:00 yes 16:38:07 anyway, that's all i have for that topic 16:38:22 do we have anything else to discuss today? 16:38:40 apart from a new meeting time potentially? 16:39:01 is it because of the winter time mess? 16:39:04 xD 16:39:14 the new meeting time... 16:39:23 yes 16:39:41 GeKo: if we have some minutes, we could discuss the new 'run a bridge' campaign? 16:39:42 eu is moving the upcoming weekend 16:39:56 ggus: please 16:40:11 i commented on the ticket this morning 16:40:20 but if there is stuff to discuss, go ahead 16:41:25 would be possible to have a grafana dashboard to monitor the bridge campaign? 16:41:51 i suppose so, hiro? 16:41:54 what do we need on the dashboard? 16:42:56 when the new bridge joined, if it's running, and if it has obfs4 16:43:15 on a table? 16:43:18 yes 16:43:33 ok 16:43:41 yes can do 16:43:59 do we want also - I don't know - number of bridges measured per day? 16:44:32 I think I just need everything that we want and I can start putting together a dashboard this week 16:44:46 okay! i will create a ticket for you! 16:44:49 as a first iteration 16:44:53 Watch out for what running means 16:45:04 yeah we have a discussion about that 16:45:44 https://gitlab.torproject.org/tpo/network-health/team/-/issues/131 16:46:34 Yeah that is probably orports being disabled 16:46:50 not alays 16:46:56 *always 16:47:24 ggus: anything else you need from us? 16:47:28 or want to chat about? 16:47:51 i will reply to your comment. but i'm good 16:47:57 thanks 16:48:08 okay, meeting time 16:48:18 do we keep 1600utc? 16:48:27 or do we move to 1700utc and if so, by when? 16:48:38 curently the network-team is meeting 1700utc 16:48:49 I like to keep time in UTC and adjust but some people like the opposite 16:48:52 and they'll have a discussion about that in 10 minutes 16:49:27 I guess we should follow what the previous and next meeting do 16:49:42 but I hpe they agree on the same 16:49:47 :) 16:49:57 okay, i'll sort that out with the browser folks 16:50:07 and the network-team people 16:50:28 and hopefully i'll announce something this week on the network-health list 16:50:46 meanwhile let's keep it 1600utc for next monday? 16:51:56 sounds like, "yes" :) 16:51:58 okay then 16:52:07 any last minute items? 16:53:00 nothing. have a nice week then everyone 16:53:03 #endmeeting