Proposal for handling PTE requests: Discussion Round 2

We have this pending proposal by @ocean90 for a new, more efficient way to handle 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. requests.

In this new post, I’d like to ask everyone further feedback on the visual summary of the previous discussion.

Note what I have here is not a final plan. They are just my interpretation of the feedback. Please do leave a comment, or make a copy of this Google Drawings file.

Flowchart (3 phases)

This is a revised version from what I posted as a comment to the previous discussion.

Screen with a “Request a review” button

On a translation overview page per 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//project (example).

Translation Request Form

Again, this is just a first version. I’m not sure about these parts, so looking forward to your opinion.

  • Translators and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme authors should use the same format?
  • 100+ and 50+ waiting checkmarks (I added them as an easy way for plugin/theme authors to determine the candidates of PTEs. For products with a small number of stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings., let’s say 50, they should be able to select anyone who has submitted translations? The lower threshold should be 30?)
  • This form may not work the best for plugin/theme authors in a special case. For example, if their product has a total of only 10 strings and 15 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/ have pending 10 strings. It’s more tedious than the current format to have to add 15 locales from the dropdown.
  • Any other edge cases you can think of?

Assign/Remove PTE Buttons

Also on a translation overview page (only visible to relevant Locale Managers/Global Mentors).

#pte