13:59:09 <ggus> #startmeeting community team meeting - 2022-07-05
13:59:09 <MeetBot> Meeting started Tue Jul  5 13:59:09 2022 UTC.  The chair is ggus. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:09 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:59:26 <ggus> it's community team meeting time!
13:59:28 <ggus> welcome everyone
13:59:30 <emmapeel> o/
13:59:53 <ggus> here's our meeting pad: https://pad.riseup.net/p/tor-community-team-2022-keep
13:59:59 <rhatto> :)
14:00:06 <ggus> please add your updates and then we can start the discussion
14:05:10 <nina13[m]> done!
14:05:18 <emmapeel> same
14:05:27 <emmapeel> it was easy this week because ofhackweek
14:06:04 <ggus> cool! let's start
14:06:14 <ggus> * Q3 roadmap
14:06:34 <ggus> i worked with gaba on the community team Q3 roadmap
14:07:35 <ggus> but instead of doing an irc meeting about it, i thought about doing a voice meeting
14:07:42 <ggus> so we can discuss the topics
14:08:27 <championquizzer[m]> +1
14:08:28 <ggus> sound good? can we do that next monday, at the community team time?
14:09:15 <championquizzer[m]> wfm :)
14:09:43 <emmapeel> cool
14:10:30 <ggus> ok, i added the room link on the pad
14:10:36 <ggus> https://tor.meet.coop/gus-dib-5tv-zu3
14:10:36 <championquizzer[m]> raya: ^
14:10:48 <ggus> i'll add on the nextcloud calendar too
14:10:58 <ggus> (if it's still alive)
14:11:41 <emmapeel> ggus: please add us as attendants, so we receive the nice email and i can add it to my local calendar
14:11:47 <raya[m]> wfm too!
14:11:47 <ggus> sure!
14:12:24 <ggus> alright, moving on.
14:12:30 <ggus> * Tor user documentation guideline: https://gitlab.torproject.org/tpo/community/team/-/issues/5
14:13:03 <ggus> last week i worked on this draft. it's still a WIP, but as we have more contributors writing user documentation
14:13:06 <ggus> i think it's relevant
14:13:54 <emmapeel> yes, this is great
14:14:06 <ggus> if you read that ticket, you will see that the guideline isn't consistent at the moment, and we should reach to some consensus
14:14:15 <ggus> for example:   - Formal vs informal
14:14:19 <ggus> - Scope of this guideline
14:15:20 <emmapeel> maybe we could ask our new brand person about it? and ux?
14:15:21 <ggus> About the scope: when i wrote it i was thinking about the user facing documentation like tb-manual, support portal, community portal.
14:15:59 <ggus> emmapeel: we should add ux team too
14:16:55 <ggus> emmapeel: but user facing docs is pretty important for the community team, as we're responsible for the user support
14:17:14 <emmapeel> sure
14:17:58 <emmapeel> but maybe the tone is a brand thing ?
14:18:06 <emmapeel> just consulting of course
14:18:48 <emmapeel> the old docs have informal tone
14:18:48 <championquizzer[m]> the tone i believe should be informal but not like having a discussion with the reader (like how you would write a response to, say, forum post)
14:19:03 <emmapeel> agreed
14:20:14 <ggus> i agree
14:21:30 <ggus> on that ticket i also added some references to other guidelines: https://gitlab.torproject.org/tpo/community/team/-/issues/5#note_2737572
14:21:42 <ggus> if you have other suggestions/references, please add on the ticket
14:22:24 <rhatto> should terminology be included on this discussion? like about onion services (https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/88)
14:22:34 <ggus> rhatto: it should!
14:22:44 <ggus> onionsite vs onion site is a hot one
14:24:40 <championquizzer[m]> hrm, the links to gnome and tails docs is giving a 404
14:25:40 <ggus> oh, they changed it
14:25:42 <ggus> https://tails.boum.org/contribute/how/documentation/style_guide/
14:25:53 <ggus> https://developer.gnome.org/documentation/guidelines/devel-docs.html
14:26:47 <championquizzer[m]> maybe one thing to add to the the 'known issues' / 'troubleshooting' part is that we should use canonical links for bugs (notice the link by the bot ^)
14:27:02 <championquizzer[m]> like: https://bugs.torproject.org/tpo/onion-services/onion-support/88
14:27:16 <ggus> good point
14:27:42 <emmapeel> championquizzer[m]: what is the difference with the ones starting with gitlab?
14:28:05 <emmapeel> (i agree on having one way, but i want to know if there are more advantages)
14:28:24 <championquizzer[m]> i think the idea is that bugs.tpo links were still working when we migrated from trac to gitlab
14:28:38 <championquizzer[m]> so it's canonical in that sense
14:29:05 <championquizzer[m]> (somebody confirm this ^ please though :)
14:29:06 <emmapeel> oh i see, thanks
14:30:29 <emmapeel> i think if you are not used to bugtrackers 'gitlab' makes less sense than 'bugs'
14:32:29 <ggus> https://developers.google.com/style
14:33:45 <ggus> maybe we could link the tor glossary too
14:33:49 <ggus> like: https://developers.google.com/style/word-list
14:35:14 <championquizzer[m]> absolutely. the glossary has some very important info about the terminologies
14:36:16 <championquizzer[m]> i also agree with avoiding contractions (can't -> cannot) and shortening of words (repo -> repository) in the draft
14:36:23 <championquizzer[m]> what do you all think?
14:36:34 <raya[m]> agree
14:37:07 <ggus> yes +1
14:37:52 <ggus> championquizzer[m]: if we all agree with avoiding contractions, the docs guideline should follow it's own rules
14:39:10 <emmapeel> yes, the glossary has spelling and translation notes
14:39:11 <emmapeel> we should also add more words to the glossary i think
14:40:24 <ggus> oh no, the spelling here is wrong: https://support.torproject.org/glossary/onion-site/
14:40:28 <ggus> it's onionsite hehe
14:40:40 <nina13[m]> Maybe some guidance for ESL audience?
14:40:40 <emmapeel> oops
14:41:03 <championquizzer[m]> re. glossary. i have this on my plate for the 11.5 release : https://gitlab.torproject.org/tpo/web/support/-/issues/303
14:41:07 <ggus> emmapeel: i agree, we should add more Tor related words
14:41:36 <emmapeel> maybe we can add new terms there
14:41:49 <emmapeel> and ask the devs to define them :D
14:42:26 <ggus> nina13[m]: good point
14:42:55 <ggus> nina13[m]: check the section "Global audience"
14:43:06 <ggus> copied and pasted from GNOME devel docs
14:43:08 <emmapeel> i think we shoulr write in ESL
14:43:11 <emmapeel> :D
14:44:52 <ggus> emmapeel: See "Spelling"
14:45:12 <ggus> "The Tor documentation prefers no national variety of English over any other. When writing new content within an existing article it is recommended to maintain the spelling convention already prevalent in it; if the article does not have a clear prevalent spelling, write accordingly to the variant used in the edited section. Harmonizing the spelling around the edited content is acceptable, however
14:45:18 <ggus> refrain from performing edits whose main purpose is changing or harmonizing the spelling standard of articles or series thereof."
14:46:27 <emmapeel> cool. maybe add 'remember that translators will have extra work each time you change something'
14:47:02 <ggus> hah yes
14:47:05 <emmapeel> lots of translators complained that we changed many many strings where it was onion services and now it is Onion Services
14:47:09 <ggus> "think about the translators"
14:48:25 <ggus> emmapeel: can you add that on the ticket?
14:48:31 <emmapeel> i will
14:49:22 <ggus> next steps: add your comments on that ticket, so we can have a 0.1 version :)
14:49:39 <ggus> emmapeel: i think the next topic is yours
14:49:44 <ggus> * input needed for social media bank
14:50:10 <emmapeel> yes! so, on the hackweek we were gathering texts for the comms team to use in social media
14:50:38 <championquizzer[m]> very cool project!
14:51:07 <emmapeel> and so i wanted to ask you to add more texts to it
14:51:07 <emmapeel> https://pad.riseup.net/p/hackweek-social-media-bank-83X6P-keep
14:51:14 <emmapeel> or maybe images
14:51:48 <emmapeel> the best texts are those copied from our translated webpages, because they will be also available on other languages
14:52:13 <emmapeel> there is also a calendar section, so maybe you want to add them to a specific moment of the year
14:53:09 <emmapeel> memes are also welcome (they are also images, but they are not just images to accompany a text)
14:53:20 <raya[m]> fun! :)
14:53:51 <emmapeel> maybe the images can be submitted to the repo at https://gitlab.torproject.org/tpo/web/social-bank
14:54:34 <emmapeel> thats it
14:54:58 <ggus> great! thank you emmapeel
14:56:11 <ggus> alright, that's all for today. i'll stop the bot
14:56:14 <ggus> #endmeeting