Naoko Takano 7:30 am on January 18, 2021
Tags: polyglots ( 92 )

Proposal: Polyglots Team Plans for 2021

Just as the end of the year is a good time to reflect on the past year, the beginning of the year provides an opportunity to start discussing what we want to see happen in the coming year.

This year, thanks to many of your responses to the Polyglots Translator Research, we have more data to base our decisions on. To refresh our minds on the findings, a few of the items the research project team thought of as key findings were:

We need better communication and feedback
Editors see growing their team of active translators as a significant task
Translation approval process confusion & wait time are blockers to many translators
Machine translation usage is high among translators

As also seen in the research results, we all know everyone already works hard to help their localeLocale 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/ team. My proposals below are mainly for removing the blockers to optimize your effort, so you can focus more on the meaningful contribution that you enjoy doing.

Here are some of the proposed plans on things we can work on. If you have thoughts on what we should prioritize, please leave a comment.

~~I’ll keep the comments open until the end of the month (January 31st), then adjust the details based on the feedback.~~ Text in italic was added based on the feedback. Thanks!

1. Better Communication Between Translators and Editors

Resolving the existing communication friction will reduce the stress and frustration on both sides. This is a high-priority item that we’d like to get help from the MetaMeta 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. team and put in place this year.

Integrate a bbPress-based tool to GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., mainly for translation feedback.
Process improvement for PTE requests.
Make locale/global SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. more visible on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins..

2. Promote Team Growth

Not having enough contributors can put a heavy burden on the active ones. For sustainability, we want to make sure each team grows stronger – we will need to find a way to do this without taking away too much time from contributors to work on translation activities. Also, keep in mind that it’s important to bring in contributors in a way they won’t get lost, so that onboarding will not create too much additional load to existing contributors.

We already have some documentation – but that doesn’t seem to be enough. What other ideas can we explore to help promote team growth?
Conflict resolution: There are some locale teams having issues working well together because of conflicting opinions in workflow/translation decisions, etc. What can we do to spot & help with such conflicts?
Training: A Learn WordPress course + discussion groups – or Sensei (text-based) course – on becoming a translation editorTranslation 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 / locale manager
Mini-translation package proposal also somewhat falls under this topic, as its goal is to help kick-start a new/inactive team.
(Added) Our current process of locale team formation doesn’t always work especially when the current GTEs/LMs are not active. In addition to the vetting criteria page & inactive team doc, what else can bring positive change?

3. Further Clarify Translation Approval Process

There is documentation on how to get a translation approved in the global Polyglots Handbook, but new translators are still unsure of the process. This blocks our goal to promote team growth and creates more work for editors when reviewing translations.

Add links to translate.wordpress.org to locale Handbooks, local instructions, and any other supplemental information.
Would tooltips in GlotPress help for first-time contributors?
Welcome messages with instructions for new members in locale-based Slacks or when someone joins #polyglots?
Some type of notification mechanism could help new & experienced translators to become aware of the next steps they need to take.
(Added) Make sure to clarify translators can/need to request a review after adding some suggestions.

Thanks for your pre-feedback on this post! @tobifjellner @denisco @fierevere @psmits1567 @evarlese
Also, thanks for your feedback: @evarlese @wangql @kuailedekehu @smile32 @markscottrobson

Erica Varlese 3:11 pm on January 22, 2021

Thank you for putting this all together, @nao!

I am intrigued by the ideas to work on improving conflict resolution and training! The Handbook reorganization last year was helpful for updating our information. I imagine there are more ways to make the information more engaging.

I’m curious to hear from others what resources could be helpful. Many localesLocale 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/ already have handbooks with information on how to get involved, so I wonder if building training materials as a global resource that can be translated – or as a resource for teams that might not have their own Handbooks just yet – would be useful.
快乐的客户 8:16 am on January 24, 2021

I think the right people should be selected as localeLocale 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/ managers and general translation editorsTranslation 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. Choosing responsible people as local managers and general translation editors will greatly improve the translation situation in the WordPress community, and thus facilitate the growth of the WordPress community.

For example, there has been a great demand for WordPress localizationLocalization Localization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel." in China region or for users using Chinese language. The current dilemma is that participation in the translation activities of the WordPres community requires the consent of the project translation editorProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves., and the local managers and general translation editors in the China region are currently in a state of inactive responsibility. This creates a dilemma: I want to participate in the translation activities of the WordPres community, but neither the local manager nor the general translation editorGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. is actively responsible for the public affairs, so I have to wait long and aimlessly, and then the enthusiasm disappears. The whole WordPres community fell into silence.

I believe that a willingness to actively perform the responsibilities of public affairs is a necessary requirement for local managers and project translation editors. Serving as a local manager and project translation editor is a public authority for the WordPres community, and it is then imperative that those who are granted public authority fulfill their responsibilities.Local managers and project translation editors should have two corollary responsibilities:
1. actively participate in the WordPres community for translations.
2. Actively participate in the management of the WordPres community.

A system should be established whereby local managers and project translation editors in a given region should be disqualified if they have not fulfilled their public responsibilities for more than three months. The local manager and project translation editor should be replaced by someone who is willing to fulfill their public responsibilities.

I am willing to fulfill the responsibility of public affairs, so I request to be the translation editorTranslation 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 of local economic and general projects in China, and ask the WordPres community to give me this public authority. I am willing to actively participate in the management and translation of the WordPres community.
- wangql 7:21 am on January 26, 2021
  
  Excuse me, but is here the best place for you to apply for local manager or similar position?
  - Naoko Takano 7:54 am on January 26, 2021
    
    @wangql this (comment area) isn’t the best place to apply for a local manager – please try to reach out to the current LocaleLocale 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/ Managers
    https://make.wordpress.org/polyglots/teams/?locale=zh_CN
    See: https://cn.wordpress.org/contact/
    
    Or you can create a new post on this site: https://make.wordpress.org/polyglots/
- Naoko Takano 8:01 am on January 26, 2021
  
  @kuailedekehu thanks for sharing your thoughts on the team goals! I agree that our current process of localeLocale 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/ team formation only works to a certain extent.
  
  Last year, we created this documentation for vetting Translation Editor & Locale Managers. Do you think this needs any addition/modification?
  We also have documentation on steps to take for the case of inactive editors.
wangql 7:20 am on January 26, 2021

Thanks @nao for putting them together.

I am curious that there should be a mechanism to help local translators to make contributions for or to optimize the local glossary. Many locals has an obsolete glossary, while new terms are coined, e.g. blocks, patterns, etc. The combination of consistency statistics and local discussions might help. Some localesLocale 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/ has no SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. or IRC channels, so P2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/. could be an option for discussion.

I have heard that some 3rd-party websites (for example, wp-china.org) has introduced machine translations to accelerate the progress. I am glad to hear if GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. will introduce some similar ones, since it might be useful.
- Naoko Takano 8:10 am on February 1, 2021
  
  I agree that it’s currently not easy to determine active & skilled translators (in terms of adherence to the glossary and style guide, for example). Since tooling change can take a while to be implemented, I’d like to include best practices for training for maintaining an up-to-date glossary.
  
  We have built a “Consolidated glossary” some time ago but it’d be a good idea ot update and share it globally.
  https://make.wordpress.org/polyglots/handbook/for-editors/glossary-style-guide/ (under “WordPress.orgWordPress.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/ Glossary Examples”).
  
  We don’t have a definite plan for machine translation integration yet, but I’ll make sure to take a look at wp-china.org to see how it’s implemented.
  - smile32 9:05 am on February 1, 2021
    
    I think adding a comment feature to the translation interface like translate.wordpress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ would help improve the quality of translations so that translators can easily communicate with each other.
Mark Robson 5:08 pm on January 27, 2021

Thank you @nao for such a comprehensive post.

I totally agree that we need better communication between translators and editors. If we could integrate an appropriate tool into GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. to enable feedback, that would be great. If the communication took place within the system that the translator was already using, this would, more likely, encourage them to respond. It would save the frustration of an editor having to use the Team P2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/. to establish contact with a contributor, only for the email to end up, unread, in a Spam/Junk folder. I, very rarely, get a reply if I do this!

If we could amend the PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. request process, so that contributors are in no doubt that they have to submit stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for review first, before they can be given PTE capabilities, this would be a great improvement. There are, still, so many people who ask to be a PTE without submitting any strings!

I agree, also, that giving more emphasis to the various local and global SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channels on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. would reassure contributors that there is always help/support available for them, if they need it.

As regards promoting team growth, the main hindrance, in my opinion, to encouraging more contributors to a team is the number of waiting strings in some localesLocale 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/. I fully appreciate that some locales just do not have enough active editors to clear these strings, but many people will be put off by this and will wonder if their suggested strings will ever be approved. If a team is ever going to have a chance to grow, then prospective contributors will need to have reassurance that their suggested strings will be reviewed and approved in a timely manner. It is very important, therefore, that any team requires proactive editors and localeLocale 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/ managers.

Finally, as regards the translation approval process, I think it would be very useful to have as many links as possible on translate.wordpress.org to the relevant local RosettaRosetta 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. site, style guide, glossary, and Slack channels. This would reinforce a locale’s commitment to encouraging and onboarding new contributors.
- Naoko Takano 8:37 am on February 1, 2021
  
  If we could amend the PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. request process so that contributors are in no doubt that they have to submit stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for review first before they can be given PTE capabilities, this would be a great improvement. There are, still, so many people who ask to be a PTE without submitting any strings!
  
  This (and the last part of your comment) is a very good point for the “Further Clarify Translation Approval Process” section. The ultimate goal is to remove frustrations and time-consuming tasks that are not very productive. As you mentioned, we will need to make sure to keep in mind that simply adding more people is not a solution to the problem we are having.
  - Peter Smits 7:58 am on February 5, 2021
    
    Hi @nao I am missing a solution we have discussed to improve the translation process. We have discussed to alert a translator after adding xxx suggestions. If you make a popup after xxx sugestions to indicate that he can ask for review or become PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves.(with link to handbook), it could help to get the translator to request for PTE.
    - Naoko Takano 8:07 am on February 5, 2021
      
      I’ve reworded the point about clarification for the request to say this:
      
      (Added) Make sure to clarify translators can/need to request a review after adding some suggestions.
      
      For the “Further Clarify Translation Approval Process” section, we have lots of good ideas and possible approaches – it may be good to pull them all together and prioritize based on the effectiveness as well as ease of implementation.

Translate WordPress

Weekly Meetings

Posting here

Proposal: Polyglots Team Plans for 2021

1. Better Communication Between Translators and Editors

2. Promote Team Growth

3. Further Clarify Translation Approval Process

Translate WordPress

Weekly Meetings

Posting here

1. Better Communication Between Translators and Editors

2. Promote Team Growth

3. Further Clarify Translation Approval Process

Share this: