[wp-meta] [Making WordPress.org] #3423: Add new functionality for editor/locale requests

Making WordPress.org noreply at wordpress.org
Wed Feb 14 05:32:20 UTC 2018

#3423: Add new functionality for editor/locale requests
 Reporter:  danieltj                  |       Owner:
     Type:  task                      |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  2nd-opinion               |

Comment (by Nao):

 To summarize, the steps will be:

 1. Initiate a PTE Request: Either on Rosetta or translate.wordpress.org.
 Need to send username and project name.
 2. Create a public post: On a new Make P2, trac, or forum section.
 3. GTEs receive the request: On Rosetta or translate.wordpress.org (if new
 admin backend is to be created). For now, this may have to be an
 aggregated view of the system used in step 2 + wordpress.org notification
 system using a certain keyword.
 4. GTEs approve request or decline with reasons: The resolution is posted
 back to the system used in step 2.

 Here are my thoughs on each steps.

 '''Step 1:'''
 I think translate.wordpress.org is most suitable because starting the
 workflow from there feels more natural & less confusing. Translators are
 already translating on it and plugin/theme authors are looking at the list
 of contributors to determine who should be a PTE.

 '''Step 2:'''
 Creating a new Make P2 sounds good to me. GTEs are most familiar with the
 format - some of GTEs may not be used to using Trac. Forums currently
 don't have a way to show all unresolved with a certain tag, so that may
 require more customization.

 '''Step 3:'''
 Even if we don't have the resource to get a new system for this step, it's
 still an improvement to get other steps more streamlined.

Ticket URL: <https://meta.trac.wordpress.org/ticket/3423#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list