[proposal] support.tpo update cycle
Hey folks! Last week, emmapeel and I started to draft support.tpo update cycle. Please, see if this workflow works for you. Release cycle ------------- - We aim to update support.torproject.org once a month, starting on the 10th. - Community liaison (gus) will bring the content to change. - Localization coordinator (emma) and community liaison will ask others to review the modifications and then update the website. - Localization coordinator update translations in transifex. How to submit content changes ----------------------------- For content changes, you can open a trac ticket and choose the component: Community/Tor Support. Trac ---- Where in trac.tpo we could add this workflow? :) cheers, gus -- PGP: 427F 2D71 7664 D215 378C B412 8BDC 87FB 7215 E189 XMPP/OTR: 62f58f8062da3e48e0aa076f20807ecb1488658e https://gus.computer/
gus:
Hey folks! Last week, emmapeel and I started to draft support.tpo update cycle.
Please, see if this workflow works for you.
Sorry for my slow reply! Thanks for getting this workflow started Gus and Emma!
Release cycle -------------
- We aim to update support.torproject.org once a month, starting on the 10th. - Community liaison (gus) will bring the content to change.> - Localization coordinator (emma) and community liaison will ask others to review the modifications and then update the website. - Localization coordinator update translations in transifex.
How to submit content changes -----------------------------
For content changes, you can open a trac ticket and choose the component: Community/Tor Support.
This looks good to me. I will make a point to add suggested content changes to the portal based on the monthly user advocate feedback.
Trac ----
Where in trac.tpo we could add this workflow? :)
Should we put it right on the support portal? Something like "have feedback?" or some other language that communicates that this feedback option is for content changes/additions, not for getting more help using Tor?
cheers, gus
_______________________________________________ tor-community-team mailing list tor-community-team@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-community-team
Hi Alison, Em Wed, Aug 01, 2018 at 04:39:00PM +0000, Alison Macrina escreveu:
gus:
Hey folks! Last week, emmapeel and I started to draft support.tpo update cycle.
Please, see if this workflow works for you.
Sorry for my slow reply! Thanks for getting this workflow started Gus and Emma!
I thought we're going to have enough time to discuss this during our community meeting, but turned out that we were all busy these last weeks, so replying you here.
Release cycle -------------
- We aim to update support.torproject.org once a month, starting on the 10th. - Community liaison (gus) will bring the content to change.> - Localization coordinator (emma) and community liaison will ask others to review the modifications and then update the website. - Localization coordinator update translations in transifex.
How to submit content changes -----------------------------
For content changes, you can open a trac ticket and choose the component: Community/Tor Support.
This looks good to me. I will make a point to add suggested content changes to the portal based on the monthly user advocate feedback.
Ok!
Trac ----
Where in trac.tpo we could add this workflow? :)
Should we put it right on the support portal? Something like "have feedback?" or some other language that communicates that this feedback option is for content changes/additions, not for getting more help using Tor?
Yes, and if we look in trac content draft, there was a contact section, but I don't know why it wasn't included: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Suppor... Maybe it was because the section name could confuse with the website menu? If so, we could just rename to "Feedback". Btw, the duplicated questions are intentional? cheers!, Gus -- PGP: 427F 2D71 7664 D215 378C B412 8BDC 87FB 7215 E189
gus:
Yes, and if we look in trac content draft, there was a contact section, but I don't know why it wasn't included: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Suppor...
Maybe it was because the section name could confuse with the website menu? If so, we could just rename to "Feedback".
Yeah we definitely want the contact section included! And also, I'm wondering what the status of the search function is. I will ask the UX team today.
Btw, the duplicated questions are intentional?
Yes, the questions at the top are the most frequently asked questions. There are about 5 or so of those, and they also appear under their subject headings later. If there are other duplicated questions besides those, those are not intentional! Alison
cheers!, Gus
participants (2)
-
Alison Macrina -
gus