12:59:51 #startmeeting Community Team Meeting - 2022-01-19 12:59:51 Meeting started Wed Jan 19 12:59:51 2022 UTC. The chair is ggus. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:59:51 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:01 hello, hello! 13:00:17 Hi, we're starting now the community team meeting. :) 13:00:27 o/ 13:00:37 here's our meeting pad, please add your updates: https://pad.riseup.net/p/tor-community-team-2022-keep 13:00:53 o/ 13:00:58 o/ 13:05:14 . 13:08:24 done 13:08:42 do you need more time or shall we start? 13:09:02 done! 13:09:35 done! 13:09:58 done 13:10:07 i added some discussion points, but feel free to add other topics 13:10:27 * (update) Telegram user support channel: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40578 13:11:25 We're going to setup a telegram user support channel in a new cdr.link instance 13:11:53 there was some back and forth with tpa 13:12:05 since they weren't expecting hosting a new service 13:12:17 tpa will provide the machine after figuring out a few things 13:12:44 gaba: see irl last comment 13:13:06 i like that we host it internally, it seems such a service has access to very sensitive information about our users 13:14:28 ok, well. if irl has an alternative until we decide if cdr.link will be the replacement for rt, then it would be fine 13:14:52 yeah, me too, but for now there are some adjusments that needs to be done on the setup to fit inside TPA infra. 13:15:15 understood 13:18:32 so, as the support on telegram activity was planned to start in january, we will need to update and plan the public launch again 13:18:36 i think to take this decision maybe it will be good to have a list of requirements fo rthe new service 13:18:56 what do we want to have on the new service, what does not work in rt, what will be good to have... 13:19:26 i didnt understood that cdr.link was a replacement for rt 13:19:59 emmapeel: as i pointed out on the ticket, we want to evaluate doing user support on popular chat apps like telegram. 13:20:22 emmapeel: it might happen, but right now we're on the early stage of testing. 13:20:23 you should tell me if you want signal/whatsapp too 13:20:49 ggus: mabe we could start a list in a wikipage of the things we want? then we can review more apps and see if the have it 13:21:02 i am in the process of setting up the cdr link instance on the hetzner box, but it probably won't be finished until tomorrow 13:21:05 if they have what we want. and what tpa or other stakeholders want 13:22:00 yes, i think we can start with telegram and then enable other options 13:22:01 emmapeel: i think that is a process we should look into after we are done with the rapid response fund project 13:22:11 understood 13:22:45 emmapeel: yes, or a ticket to track down possible RT replacaments 13:23:15 it will be important to test some of these solutions 13:23:45 ggus: yes, what i meant was a step previous to track down the possible replacements: once we have the requirements, it will be easier to evaluate the replacements 13:24:14 right 13:25:14 yes, i can start on that (weighing rt replacement) work and then we can improvise as we setup the cdr telegram support for .ru/.kz 13:25:45 championquizzer: great! i can give a hand also looking for stakeholders 13:26:07 ty, emmapeel 13:26:16 (you are one important one because you are doing user support, but maybe tpa or the money machine also have a say) 13:26:40 i will open a ticket on community/support to follow up on this issue 13:26:52 yeah i am already having so many thoughts on hearing about replacing RT so.. :) 13:27:04 a ticket sounds good. thanks, ggus 13:27:20 i will move to the next topic: * Tor translations in Chinese (S96 work) 13:28:07 emmapeel: for s96 work, we will need tor browser user docs (support and tb manual) translated in chinese 13:28:13 yes. i wonder, which chinese? simplified Chinese that is read in mainland China, or maybe traditional spoken in Taiwan and hong Kong? 13:28:28 we should check how many translators we have 13:28:53 simplified Chinese 13:29:05 we also need the translation status 13:29:25 we can discuss on friday this 13:29:31 simplified we need some more translations on the suport portal but it is released and kinda complete 13:29:36 same with the manual 13:29:52 maybe i could contact our translators to make a review 13:30:03 ok, lets discuss in Friday. 13:30:05 great! 13:30:39 ggus: the new texts on support are hard to translate (relays, etc...) so maybe we need some techie translator help 13:30:50 thank you! 13:31:09 the last topic on our agenda: 13:31:15 * Community Team OKrs, 1:1 and team organization 13:31:50 emmapeel: ok 13:33:28 last year we did our team OKrs, and you can read it here: https://gitlab.torproject.org/tpo/community/team/-/issues/47 13:33:43 we need to do our 2022 OKrs (Q1/Q2) 13:35:13 how are we going to do it? 1:1? 13:35:28 last time i opened a pad and we contributed, but this time i'm thinking about doing 1;1 and filling a pad 13:35:42 would that work for you? 13:36:31 sure 13:36:52 wfm too! 13:37:55 i can put together some sponsor work that we have to do and we review together 13:38:43 sounds good. next week? 13:39:11 yess 13:39:17 ack 13:39:25 ok 13:40:46 i will ping you both on irc to find a date/time for our sync 13:40:56 ok 13:41:02 sure. ty, ggus 13:41:33 anything else for today? 13:41:56 i added something to announcement on the pad after the meeting started: 13:41:58 ... 13:42:07 oh yeah! 13:42:14 this Friday we Hangout! 13:42:24 this Friday is the Monthly Tor localization hangout! 13:42:41 starting at 12 UTC with a BBB call at 13 UTC 13:42:49 first hangout of the year 13:42:57 oh yes! 13:43:02 https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Monthly-Tor-Localization-Hangouts 13:43:35 cool! 13:45:09 i will remember comms to tweet/toot about this 13:45:14 alright i will stop the bot 13:45:14 thanks 13:45:16 thanks everyone 13:45:19 #endmeeting