15:59:42 #startmeeting community team weekly meeting 15:59:42 Meeting started Mon Feb 11 15:59:42 2019 UTC. The chair is flexlibris. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:44 o/ 16:00:44 okay pulling out the pad.... 16:00:55 has everyone got it? 16:01:19 yup 16:01:26 yep! 16:01:30 let's start on the support/community portals 16:01:59 i havent had any time to look at the support portal content pull requests. all my attention has been on the community portal. has anyone had time for these? 16:02:26 o/ 16:03:00 i'm gonna move them to march but....iirc they were fairly specific use cases that i didnt think had a lot of utility on the support portal 16:03:01 I actually had a question regarding the support portal, if it's ok to ask now? :) 16:03:04 sure 16:03:22 oh also, i just realized that we agreed to talk about community team visioning at this meeting 16:03:26 and i totally forgot :) 16:03:29 yup, we can do it at the end :) 16:03:37 okay we can do this part quickly then 16:03:40 please ask your question 16:03:45 so, I was talking to isabela and she said that we should move over the relay operator guide from the wiki to the support portal 16:03:46 but 16:03:54 I can see we already have an operators section 16:04:04 o/ 16:04:15 AND that the guide in the wiki doesn't really follow a Q&A format like the support portal currently does 16:04:19 yeah i thought it was all going to go on the community portal 16:04:29 me too 16:04:29 i dont think it really belongs on the support portal, that is for end users 16:04:33 It should be a single place to search/read. 16:04:34 so I was just wondering if anyone had any ideas about the best way to do that 16:04:35 hmm... :) 16:04:36 ok 16:04:45 there is some basic relay guidance there but it all links to the longer guide 16:04:50 sure 16:04:53 i think is content for the community portal, we could link to it from support tho 16:04:58 yeah 16:05:02 +1 16:05:06 maybe the links were the other way round then 16:05:07 maybe we need a lektor instance for it 16:05:07 ok 16:05:16 I'll figure it out ;) 16:05:20 let's move on :) 16:05:52 cool 16:06:01 i will just name the items that i tihnk are outstanding to save time 16:06:24 if in the long term we want to have all the manuals (tb and tba) in support.tpo, it make senses to have relay guide there too. 16:06:29 ggus sent me his training materials and I have to finish mine and send them to the others working on the portals. LFI has been taking over my life. 16:06:59 okay but then do we also have onion services setup instructions on the support portal too? 16:07:16 we originally were making some distinction about what level people were at 16:07:23 support portal being for more basic/intermediate users 16:07:43 that depends on the size, if it's like 5 steps or like an article. 16:07:44 I think it mights sense to keep a separation between end-user programs like the Tor Browser or the mobile Tor Browser, and running infra like relays and onion services. 16:08:07 makes sense* 16:08:12 yeah i agree with Phoul 16:08:24 i'm not sure what you mean ggus, do you mean shorter, bulleted lists SHOULD go on the support portal? 16:09:11 no, the opposite. the glossary is in support portal, for example 16:09:18 Phoul, agreed 16:09:27 my idea is to have long article in support 16:09:27 yes, but i think the glossary needs their own section 16:09:33 is lost at the support portal now 16:09:35 not only small Q&A 16:09:38 yeah and the glossary is for basic/intermediate users 16:09:57 long articles for what content ggus? 16:10:19 basically, How to's 16:10:22 why if we briefly introduce it into support and then we link to relayoperators.tpo.org or something like it 16:10:33 yeah i like that better antonela 16:10:59 i don't know, i prefer to give people one link and they will find the right resource 16:11:12 that's why we link to it 16:11:18 i'd prefer in community 16:11:23 i think that keeping basic user info on one page and more involved stuff on another page is better 16:11:32 and keeping the basic user stuff short, no long articles 16:12:03 anyway i suggest we debate this at the portals meeting on friday 16:12:07 yup 16:12:25 emmapeel: can you come to that meeting on Friday and talk about localization needs/plans for the community portal content? 16:13:23 emma couldn't make this meeting 16:13:30 ah okay 16:13:36 i will email her or maybe she will see the highlight 16:13:52 okay so moving on to outreach 16:14:05 anything to update about under this heading? 16:14:25 I?ll run 2 activities this week 16:14:32 cool! 16:14:41 At Campus Party, a huge event here in SP 16:14:51 I still don't have my activities url 16:15:11 * antonela really liked how the Solid project is calling the relays "Community Servers", i know we are not storing anything on the relays computers but sounds more friendly not? 16:15:23 but one is DEsmystifying deep web and another is Do you have a moment to hear the word of Tor? 16:15:42 nice cy63113! 16:15:45 :) 16:15:52 the gospel of Tor 16:15:57 hahahahhahahahha 16:16:12 that's it for now 16:16:22 cool good stuff thanks Cy! 16:16:28 :) 16:16:32 volunteer updates? 16:16:47 antonela: My worry with wording like that is I think "community server" would apply to relays, onions, auths, etc.. not just relays; in the Tor context. 16:17:14 seems like no updates there... 16:17:23 phoul, you right, i just found that label very friendly 16:17:29 i don't have much to say about LFI, I'm still doing the same stuff I was doing last week :) 16:17:37 Phoul do you have anything to share about relay advocacy tasks? 16:17:41 antonela: agreed :) 16:17:45 flexlibris: yup! 16:17:48 I will be quick 16:18:04 cool 16:19:13 This week I should hear about a date for the RRC / ISACA / SkullSpace cryptoparty & operator meetup, I've been working on content for this. This week I'm also meeting with the local IX group to discuss pushing ISPs to run more relays and to get more contacts in that space. I've also been working on the blog post to explain 100% bandwidth usage vs a "useful contribution to the network", this should be 16:19:19 ready for sharing mid this week. I've also been assisting a number of operators with NAT issues the last week. 16:20:30 good stuff phoul 16:21:40 any other updates folks? if not, we will talk about the community team vision 16:21:57 We have Delhi and Bangalore events this week. 16:22:40 ggus, do you want to share something from today's event? 16:22:44 oh yeah, anything you want to say about those? 16:23:21 flexlibris, ggus is the only person in Delhi, I will join in Bangalore 16:23:49 End of update. 16:24:00 tor training month in india started today with a workshop for journalists 16:24:05 oh awesome 16:24:10 my connection is very lagged and it's terrible to write 16:24:22 but so far so good? 16:24:43 all women workshop, it's pretty nic 16:24:47 nice 16:24:53 it was 16:25:25 tomorrow i'll meet pari and we have two training activities 16:25:46 awesome 16:25:48 reconnecting brb 16:26:00 anyone else have anything to share before we move on to the visioning stuff? 16:27:15 okay seems not 16:27:17 pili hey 16:27:17 from brazil: cryptorave opened today their crowdfunding campaign. 16:27:27 hey :) 16:27:34 let's talk about the future 16:27:59 * kat5 arrives, with apologies for spacing.. 16:28:10 kat5: just in time for the vision exercise :D 16:28:34 so I just wanted to ask all of you first: why do we need a community team at the Tor Project? :) 16:29:08 I think we need to make people feel welcome, so that they feel empowered to use Tor 16:29:12 because is the only way to reach our end-users 16:29:59 To keep our community, in all of its guises, healthy and welcoming. 16:30:03 we want to offer resources and support to our community members who do outreach 16:30:04 Its important to provide support to users and operators, and to facilitate a sense of community within Tor. 16:30:12 to reach communities that wouldn't have haerad about us, becausethey are non technical users 16:30:26 to show the world a more human face of Tor 16:30:50 to support the UX team's work 16:31:02 To encourage people to join our community, whether that's users, operators, volunteers, advocates... 16:31:27 sometimes when I explain what is the main difference when moving from a corporative environment to an open one I say: I switched the marketing team from the community team, and it feels so real, good and rewarding 16:32:03 :D 16:32:05 Marketing without the cringe ;) 16:32:26 yee 16:32:52 that was actually part of my own brainstorming process for this session :D what department in a corporate environment would the community team translate to? :) 16:32:53 awwww 16:33:00 probably support also :) 16:33:15 But it's more than that, I think. We don't just want to get people to become users or whatever. We also want to support them once they join us. 16:33:24 +1 16:33:28 +1 16:33:31 kat5 yes 16:33:50 +1 16:34:21 Like, we care about them being able to accomplish their goals for their own sake. Not just so they buy the next product. 16:34:34 what would you say are our biggest challenges in the community team? and what problems are we trying to solve? (if any) 16:35:03 but also for everyone's sake in a way, because the more users there are, the more anonymous each user is 16:35:23 Yep. 16:36:13 any more thoughts about the need for the community team? :) shall we move on to challenges and problems? 16:36:21 move on to challenges imo 16:37:22 Challenges: Lack of funding. We should be sending more people to more cons. We need a dedicated tech writing person. A dedicated volunteer coordinator. 16:37:23 maby 16:37:26 ... 16:37:34 I think one challenge is volunteer retention 16:37:40 and +1 to what Kat said :p 16:37:47 +1 to kat5 and wayward 16:37:50 +1x2 16:37:58 the single greatest challenge for me is being the team lead when i have another full time job 16:38:16 What Phoul has done as a relay advocate is a great model for other roles for sustaining community engagement. 16:38:17 our team needs an actual funded team lead who can do things like this visioning exercise for one :) 16:38:36 Challenge: Growing the capacity of the Tor network to allow for wider adoption of the network, and to allow our users to continue using Tor without experiencing delays. 16:38:55 and set goals for the team longterm, provide support for team members, do other work as needed for the team. with a full time team lead we could make real progress. 16:39:20 another challenge I've run into has been getting users to the right sources - the information they need exists, but they often have trouble finding it 16:39:51 flexlibris: +1 (Though to be clear, no knocks against your efforts!) 16:39:59 thanks kat, none taken! 16:41:03 +n to everything said, funded team lead, funded volunteer coordinator 16:41:29 maybe a funded frontdesk corodinator 16:41:34 +1 16:41:35 yes 16:41:36 +1 16:41:53 Was just typing out that another challenge is 1 on 1 end-user support :) 16:41:56 full time support person who manages the support portal, answers questions at the desk, and then turns those answers into more support portal content 16:41:57 ohhhhh definitely 16:42:08 yess 16:42:38 that person could take on what wayward has been doing with user issues, but since their whole job would be support they could be more active in getting people to the right places/creating the right places for them to go 16:42:53 like a chat thing phoul? expensive tho but necessary. Not all endusers can arrive to irc 16:42:54 yesssss 16:43:01 yess 16:43:25 antonela: I was thinking RT in that case, but a chat system would also be an option. Wayyy back we (the tor support team) created a web chat system called PUPS that we used for a little while for live support. 16:44:14 nice, we could consider it for the support portal at some point 16:45:12 so, given all these challenges, where do we want the community team to be in 2 years time? This may be an "easy" question in that we just address all our challenges, but maybe there are some other things we see in our future... ;) 16:45:49 (also, feel free to keep throwing out challenges in the meantime) 16:46:05 I would love to be checking in with local communities we've met, and meeting new people every time we see them who are amped about getting involved with Tor :) 16:46:18 i think there's a counter narrative that we need to make all time about how tor is not a bad thing; this is a challenge. looks likes we are always on the defensive, when it should be the oppoite. bside that i was thinking more about the structure that we want to build: volunteer based, staff based.. 16:46:21 in two years time i'd like for our full-time community team lead to be entering their second year :) 16:46:26 which I guess already happens! 16:46:34 ggus, that is very important point 16:46:45 flexlibris: :D 16:47:51 Do we know any college syllabus which includes Tor Project? 16:48:12 kushal: We may soon, I'm working with a local college on adding running a relay to their Linux sysadmin program. 16:49:16 nice!! 16:49:54 For the future, I'd like to see the community team continue to grow in both volunteers and paid staff. I'd like to see ISPs around the world donating their spare capacity to the Tor network. I'd like to see Tor branching out to different types of events, especially for relay operator recruitment (like ISP summits, NANOG, etc..). 16:50:34 Phoul: I like that idea about the different types of events 16:50:35 yep 16:50:42 we don't always just want to be preaching to the choir 16:51:11 Agreed :) 16:51:25 i'd to like to see non tech people using Tor, just like they use chrome or ff 16:51:34 +1 !! 16:53:00 I would love to find ways to engage more young crowd. 16:53:19 kushal: +1 16:53:23 As they will grow into different job, and lives, Tor will be spread along with them. 16:53:23 (and cy63113) 16:53:32 kushal: emmapeel shared a very good article about memes and vpns in zimbabwe 16:53:36 let me see if I can find it 16:53:38 in 2 years: to more human rights defenders organizations in global south to recognize tor as a tool that can protect their work and their lifes (and not something that they should be scared). at the moment many don't know the difference between tor and vpn, and what's tor in general. 16:53:41 pili, yup, I read it. 16:54:05 https://www.localizationlab.org/blog/2019/2/5/1i93a95cm8rdegvtqu3xm9n7gloyqh for everyone else 16:54:09 icymi 16:55:47 ok, we can continue for a bit longer or we can try to wrap it up, anyone want to throw out any more ideas on anything we've discussed so far? :) 16:55:52 Finding a way to approach younger learning institutions would be helpful. This has been something I've struggled with personally, a lot of schools (at least in Canada) do not want people in to talk about Tor, because then their students can evade the school firewall. 16:56:22 But I think it would be super awesome to perform outreach to younger communities. Privacy is for all ages. 16:57:07 That attitude doesnt seem to change until College / uni years. 16:57:53 i just noticed that it's one minute to the hour 16:57:59 and i think another team meets in here right after we do 16:57:59 yup :) 16:58:00 flexlibris, :) 16:58:01 so we should wrap up 16:58:05 ok, let's wrap this up then 16:58:09 do we want to continue this next week pili? 16:58:10 we can 16:58:13 yup 16:58:34 I'll send an email out to summarise what was discussed 16:58:35 to the community mailing list 16:58:37 and maybe we can continue that discussion there also 16:58:49 sounds great 16:59:00 thank you for leading us in this conversation pili! 16:59:05 i am closing the bot 16:59:07 #endmeeting