13:59:19 #startmeeting Community Team meeting - 2022-02-07 13:59:19 Meeting started Mon Feb 7 13:59:19 2022 UTC. The chair is ggus. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:22 hello everyone! 13:59:29 community team meeting is starting now 13:59:30 o/ 13:59:36 hello!! o/ 13:59:36 o/ 13:59:43 here's our meeting pad: https://pad.riseup.net/p/tor-community-team-2022-keep 14:00:07 please add your updates and feel free to add topics on our discussion section 14:00:07 * gman999 will be able to lurk.. but 9 AM EST on a monday is tough 14:00:31 o/ 14:00:38 Hi! 14:01:10 gman999: i opened this ticket to track the relay op workshop - https://gitlab.torproject.org/tpo/community/relays/-/issues/36 14:01:34 if you want, we can discuss today or 14:01:38 great... is this an agenda item now? 14:01:48 i can speak briefly to it 14:02:28 let's wait people add their updates on the pad, then we can discuss it 14:02:36 sure... up to you. 14:05:34 o/ 14:06:43 done 14:07:23 re: #36 - looking good! lots of ideas similar to community building ideas we discussed as part of gamification last few weeks 14:08:23 done 14:08:37 welcome rhatto !!! 14:09:01 if everyone is done, we can start 14:09:05 yes 14:09:14 rhatto: welcome!! 14:09:22 sorry i top posted on the topic list 14:09:26 :D 14:09:38 rhatto is started last week working as the tor project Onion SRE 14:09:40 welcome! 14:09:50 \o/ 14:09:58 thank you all! its amazing to join the team :) 14:10:13 he will be working with the new education coordinator, she will start next week :) 14:10:26 :) is great to have you with us! 14:10:48 lets onionnize the world! 14:10:52 good to have you here rhatto! 14:11:10 :D 14:11:30 hehe, emmapeel. i like that! 14:11:40 +1 14:11:56 it was some campaign a while ago 14:12:00 i didnt invented it 14:12:18 (attribution) 14:12:22 it's copyleft, feel free to use it :P 14:12:41 i mean, i dont want you to think it was my idea, i only have a good memory :D 14:12:42 (https://blog.torproject.org/more-onions-porfavor/) 14:13:29 great! 14:13:37 its a wonderful moto anyays :) 14:13:37 that one, championquizzer 14:13:38 gman999: do you want to talk about 14:13:44 * Workshop - Relay operator sysadmin 101 (gman) 14:13:52 i get that updates in the pad below the "-----" refer to previous weeks... is that right? 14:14:01 rhatto: yep 14:14:09 rhatto: yes, i will delete 14:14:11 sure. 14:14:21 rhatto: yeah those are from last week. it is a bit confusing this time 14:14:25 so long story short.... 14:14:30 ready? 14:14:37 ready 14:14:43 you can see it on relay@ etc... 14:14:53 bring it on! 14:15:02 but we need to do some basic stuff on better sysadmin skills/foo for relay ops ppl 14:15:07 it's a long term issue... 14:15:17 most ppl dont have experience running internet facing services 14:15:26 esp with something as targetd as relays 14:15:35 i've had stupid arguments that are obv 14:15:43 like using time sync on servers, etc... 14:15:54 gman999: if you see documents that can be improved, we could meet one that and i help you improve the docs 14:16:00 so i was thinking hthis... 14:16:11 idt it's docs emmapeel necessarily 14:16:14 although some can be. 14:16:20 we try to provide basic things... 14:16:33 but we should also conduct some types of workshops for basic sysadmin food 14:16:34 foo 14:16:44 how to dealw ith ssh zombie brute force, 14:16:47 and even more basic stuff. 14:16:55 the outline ^ shows the basics. 14:17:08 even though it's "my" idea... i think a linux admin should prob lead it.. 14:17:11 emmapeel: keeping basic sysadmin docs for each OS is out of scope. 14:17:13 i can be there for bsd related stuff 14:17:23 some of it is really basic but ppl dont get 14:17:38 this is gman999 short hand version 14:17:40 https://gitlab.torproject.org/tpo/community/relays/-/issues/36 14:17:43 maybe we could point to nicer docs outside, ggus ? 14:17:45 i can elaborate 14:17:58 it's sort of scattered emmapeel, 14:17:59 i also agree that we should copy documents that are outside of scope 14:18:05 even though it should be logically there 14:18:21 there's a lot of loopy things. 14:18:32 "i never ran a bsd but i want to help os diversity" 14:18:41 me "pls run the OS you know best" 14:18:43 etc. 14:18:56 so maybe ppl can review ^ ticket and we can work things 14:18:58 out 14:19:10 i started writing up a blog-type version of it this weekend 14:19:27 nothing is sillier than seeing bridges rejcted by Serge if they dont have ntpd working 14:19:43 if you cant do time sync right, pls be careful! 14:19:47 EOF 14:19:50 questions? 14:19:53 but gman999 that also should be on the documentation of how to run a relay 14:19:59 thank you, gman999 14:20:11 yes.. there is some and can be enhanced emmapeel.. 14:20:13 emmapeel: some of these tips are already part of the docs 14:20:14 that would help i think 14:20:21 but also a place for ppl to ask questions. 14:20:21 but that doesn't mean that people are doing it 14:20:31 thanks, gman999 14:20:32 i also agree that we SHOULDNT copy documents that are outside of scope / sorry keyboard fail 14:20:32 i think some of my points could be integrated 14:21:15 one problem i see regarding more inexperienced bridge mantainers right now, is that there is no documentation for metrics port 14:21:35 emmapeel: why a bridge operator would need docs for metrics port? 14:21:57 ggus: because they dont configure it well and their relay appears as overloaded 14:22:50 that's useful and i think those things need to be in Tor doc 14:22:50 this page appears as a link when in metrics your relay is overloaded: https://support.torproject.org/relay-operators/relay-bridge-overloaded/ 14:23:26 maybe we could link documentation more from metrics 14:23:26 right. 14:23:38 i think though the point of this is really: 14:23:49 also, ,aybe little-t-tor could give better error messages 14:23:55 "what you need to know to run a targeted internet service, in this case a tor node" 14:24:10 for example: invalid bridge name. instead of just failing 14:24:28 i just checked and we only have 17 bridges overloaded 14:24:44 better even: 'spaces are not allowed on the bridge name' 14:24:52 ggus: maybe it is because of the new docs! 14:25:15 emmapeel: no, this number has increased 14:25:21 from 11 to 17 14:25:25 but it's a minor issue, tbh 14:25:30 i get that emmapeel but look at the page ^.... 14:25:41 EOL relays is way more problematic, imho 14:25:42 sort of out of scope 14:25:54 patching/updating/maintaining... yes 14:26:05 check 14:26:45 i like the idea of workshops, but i wonder: will this be only one time? will it be recorded? 14:27:01 i believe people are lacking of the basic sysadmin skills. adding advanced topics like metricsport would be sysadmin class 3. 14:27:12 emmapeel: i'd like to record it 14:27:17 i see 14:27:24 so we can ask operators to watch the video 14:27:30 i understand that MetricsPort would be needed on those cases only for the relay operator understand locally whats going on, not to provide data to metrics.t.o; seems like this port should not be exposed publicly and having it closed would not impact in relay added to the overloaded list... 14:28:05 rhatto: you dont need to open it to be a relay, is only to see what is going on with your relay 14:28:28 yep, it's for debugging only 14:29:03 gman999: for that outline, how much time do we will need? 1h, 2hours? 14:29:22 the actual content doesnt have to be long.. 14:29:27 it's more about the discussion 14:29:29 q&a 14:29:35 i'm sure there's more that i'm not covering 14:29:42 those are the things i've seen over the years. 14:30:15 the q&a will be more important than the presentation 14:30:41 we used to have this page maintained by the community - https://gitlab.torproject.org/legacy/trac/-/wikis/doc/OperationalSecurity 14:30:58 right.. the point is that some things are more basic 14:31:04 i remember that doc 14:31:08 maybe we can pick of these topics 14:31:23 i cna imagine this: 14:31:30 a bullet point approach 14:31:44 it would be nice if that was a section of the relay meetups 14:31:49 time? run ntpd or something similiar, dont run rdate from cron @daily 14:32:13 sshd? use pub/private key auth, yubikey, etc. 14:32:38 sshd brute force? your host firewall, fail2ban, blocklisted.. know what your OS offers 14:32:40 etc. 14:33:12 gman999: like a checklist 14:33:26 yes.. allowing discussion and questions as it flows 14:33:39 instead of writing (and maintaing) the specific doc 14:34:12 gman999, i'll probably work on an onion service checklist soon... perhaps we could share ideas, ensure we don't to duplicate work etc? 14:34:20 sure. 14:34:26 i like flow but i wish we could cristalize some docs so we dont need to answer the same question thousands of times 14:34:31 i mean, everything would also apply there too 14:34:36 agree emmapeel 14:35:06 when i first was around the ngo pets scene and i brought a buddy along.. 14:35:10 a long time ago.. 14:35:12 maybe an FAQ section on relays portal would help? 14:35:25 he was like "tehy need basic sysadmin trainings... not reading white papers" 14:35:28 gman999, yep... the onion checklist could be the relay list plus specifics 14:35:34 agree 14:35:36 i feel this workshop to be a great point to gather input of docs needed, and it would be great to have them because not everybody can attend a workshop 14:35:47 +1 emmapeel 14:36:05 i agree with improving the metricsport docs and other tor docs, but having 'how to enable SSHD pub key' is out of scope. 14:36:24 ggus: is out of scope, but maybe we should find a good doc about it and link to it 14:36:31 emmapeel, sure, and also to avoid having duplicate content scattered around many pages/docs/repos 14:36:36 maybe even one of our relay operators mantains one 14:37:17 emmapeel: but then you need to point for arch linux, debian, freebsd, netbsd, dragonflybsd... 14:37:29 i feel we should say 'you should enable logins only with ssh key, here is a doc on how to do it: {{ external doc }} 14:37:55 ggus, for those out-of-scope perhaps per-distro/OS refs could be enough... there are good official docs out there 14:37:56 emmapeel: there's so many external resources that are so helpful to the community. i also believe we should at least start including some external docs 14:38:05 with a warning that they're external 14:38:23 every "learning" community does it 14:38:33 maybe while making the workshop gman999 will end up with a list of links :D 14:38:34 miko[m], +1 14:38:42 it's just better onboarding practice 14:38:47 i'll see how much more i can do 14:39:45 gman999: and do we need a linux trainer for this event too, right? 14:39:48 we can always ask for resources in the tor-relays link: do you know a good howto to enable ssh login in openbsd? 14:40:13 i mean, a 'linux trainer'... idk... 14:40:17 i mean, i could do it... 14:40:26 most stuff is generic bsd/linux 14:40:35 ntpd, sshd, etc. 14:40:56 but having a 'me' (bsd) and someone who knows the array of linux knobs would make sense 14:41:00 in case stuff is OS specific 14:41:26 it's not my ego driving me to do it... 14:41:36 maybe we could ask kushal 14:41:43 it's that i have a specific view on this i've worried about for a long while 14:41:49 kushal would be grea.t 14:42:13 sorry, not reading the chat right now, will read back in the evening. 14:42:16 i can attend to fish documentation topics 14:42:23 i will talk with you, kushal 14:42:28 ggus, thank you :) 14:42:30 *later 14:42:32 :) 14:42:43 Cool! 14:42:52 anything else about this topic? 14:43:14 nope.. i'm done! 14:43:16 ty 14:43:19 i think is a great initiative! 14:43:25 thank you! 14:43:50 cool! 14:43:55 * Tor training with human rights defenders in brazil and mexico (March - April) 14:44:07 moving to the next topic on our agenda 14:44:31 \o/ 14:44:37 today we will publish a call for participation for human rights defenders in brazil and mexico 14:44:58 i volunteer to go to mx! 14:44:58 it's a cross-project effort with tails, the guardian project and tor 14:45:08 gman999: it's online! 14:45:16 ;) 14:45:22 because of the pandemic :/ 14:45:33 well, you can make friends and then stay at their places when you get to mexico... 14:45:51 hehe yeah 14:46:35 :) 14:47:03 we will have 4 training sessions in brazil and 4 in mexico 14:47:23 Tor Browser, Tor Browser for Android and Onion Browser, Orbot and Tails. 14:48:05 dream team! 14:48:10 nah: anything else you would like to add about it? 14:48:33 emmapeel: hopefully we can recruit more pt-br translators 14:49:09 hmm 14:49:29 the translation for pt-BR is a bit behind lately 14:49:52 we will open a call for participation for these trainings 14:49:59 i dont mean to be picky but that is the truth. not many ative translators, and we produce lots of text, so... 14:50:16 maybe we can do some tweets? 14:50:16 in our communication channels, so if anyone knows any groups and collectives they want to share 14:50:20 ggus, nah, need help to promote the event / share the call? 14:50:38 rhatto: yes, that would be nice. 14:51:03 ggus, ok.. i can pass around once there's a public URL 14:51:20 ack! i will share with you 14:51:36 i think we will have the image in the end of the day 14:51:46 great :) 14:51:47 ggus: any information you think we should add there? 14:52:10 nah: in nico's illustration? 14:52:20 there is a space for date, but as we don't know the exact dates, maybe we could replace it with something else 14:52:24 ggus: yes 14:52:39 for ref: https://gitlab.torproject.org/tpo/ux/research/-/issues/73#note_2775199 14:53:30 nah: maybe we could add the CFP deadline 14:53:56 ggus: good idea :) 14:54:09 do we have a deadline for the CFP? 14:54:45 Apply by Feb XX 14:54:49 we do, it's on the pad 14:55:06 ok, i'll add this to the ticket, thank you! 14:55:06 or maybe we have a week, but not a specific date 14:55:23 let's ask sajolida 14:55:30 just wanted to let you knwo that soon we will publish some of our websites in Traditional Chinese, that is spoken in Taiwan and Hong Kong (The CPR simplified the Chinese) 14:55:31 sounds good 14:55:38 oops sorry that was meant for later 14:55:56 go ahead emma, i think that was all for the topic. :) 14:56:02 just that, thanks! 14:56:22 maybe also https://review.torproject.net/tpo/web/support/l10n/zh-TW/ 14:56:48 the new translation preview is working :D 14:57:00 yes! that is great, many translators were happy about it 14:57:02 emmapeel: remember to update the internal docs with new links 14:57:06 including the one to russian 14:57:28 yes, i did some updates but i should look further than community/l10n 14:57:51 emmapeel: web/wiki docs 14:57:58 ack! 14:58:22 i will stop the bot because there is another meeting here 14:58:25 #endmeeting