In Americas Polyglots Meeting, participants agreed that creating a 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/. channel for coordination among themselves can benefit the Latin American polyglots community (during the meeting they agreed upon
#polyglots-es may be more appropriate after all).
When I brought up this request to #meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Slack channel, there were pro/con opinions about creating an additional channel for a smaller group of polyglots.
Related previous conversation: https://make.wordpress.org/polyglots/2019/01/28/locale-specific-slack-rooms/
- It may stimulate conversations & mentoring activities among contributors that speak the same language in different regions
- It may allow interested parties to focus on the topics that they are relevant to them while reserving the main
#polyglots for more general topics that affect all polyglots
- All conversations will be always accessible unlike free versions of Slack most of locale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ teams are using
- In reality, language channels may not over-created since there are only a handful of active locales Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ with multiple variants (e.g. es_, en_, fr_, de_, and pt_)
- It may create a fragmentation between the main channel and language-specific one
- (Too much of?) non-English communication in the new channel
- This may trigger over-creation of language channels furthering the problem of fragmentation
Do you think this additional Slack channel will facilitate collaboration? Or do you think we are entering a dangerous territory where conversations are be siloed and not synced up?
Also, please add any points I missed to pick up.
If you haven’t heard of 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/. yet you should go ahead and join the WordPress team on Slack and then look for the #Polyglots channel.
The #Polyglots channel on Slack is where we have our weekly chats and where you can ask questions and look for help with translations. To log into Slack, all you need is your 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/ username and to follow the instructions here: Chat.WordPress.org
If you are a Translation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles:
General Translation Editor and Project Translation Editor (validator See translation editor.) for a locale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/, it is highly recommended that you join the channel.
New: WordPress Translate bot
The slack channel now has a bot “WordPress Translate” which informs about auto-generated release packages and language packs:
A new language pack was built.
A new release package A release package is a packaged version of WordPress. That is, a ZIP file consisting of WordPress in its entirety, along with PO and MO files for core, the PO and MO files of default themes and Akismet, and any custom changes a locale has. In the past, most locales built their release package using the form in Rosetta’s dashboard. was built.
And the bot will send notifications if new strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. are available for translation:
New strings were imported to translate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.