Here’s the follow-up on the survey regarding external communication tools. Data can be downloaded in PDF or xls format.
Q1: As a team who translates WordPress into your language, do you use any tool or platform for discussions in your language?
Out of the 14 teams that answered question #1 (it looks like we had 1 duplicate with fr_FR), only 1 team does not use any extra tool for discussions in their language.
For all other teams, Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. seems to be most popular, at least for smaller discussions, followed by Skype and IRC.
Forums, P2s (e.g. hosted at wp.com), Google and Facebook groups, even e-mail and Twitter are used for longer discussions.
Among those who say they use forums, only 1 mentions a forum hosted at wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, while 2 others refer to privately hosted forums.
￼Q2: If you use a different platform, what do you discuss there?
Translations are discussed the most (40%), but a significant amount also discusses community topics like meetups and WordCamps (30% each).
Q3: On a scale from 1 (worst) to 5 (most ideal), how would you rate the tool you use serves the purpose you use it for?
For all participating teams, the communicative tool(s) they’ve picked seem to serve their purpose almost ideally (4), or at least okay (3).
The main purpose of that poll was to validate whether or not there is an overlap of concerns for Rosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites and the Community Hub, as suggestively sketched out in this post.
Or, more simply put, to answer the questions:
- Should we bring Rosetta and CommHub together?
- If so, how would a minimum viable product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia for both look like?
Personally, I do think it is quite remarkable that wordpress.org offers a place for localized information on WordPress (aka Rosetta sites), but does not offer any means of localized communication for the teams running those localized sub-sites.
CommHub obviously doesn’t aim to solve that situation, at least not primarily. The MVP "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia sketched out in wireframes so far mostly reflects an approach of promoting meetups. Which is cool, I just don’t get why we’re starting to build something completely new, without anyone from our “localized communities” (polyglots) involved, when there’s already a localized network of sites (Rosettas) we could start with an improving on?
Or in short terms: How can a Community Hub project not involve the current state of Rosetta sites?
Now, the fact that most teams here, who took part in the survey, seem to have external, non-w.org means of localized communication in place they obviously are quite happy with, makes me feel like a bit of an idiot.
If y’all see something I fail to see, please do me a favor and fill me in. 😉 Otherwise, if this whole thing isn’t a case at all, I apologize for the time taken. Better to communicate a bit too much, though, than too little.