WordPress.org

Making WordPress.org

Changes between Initial Version and Version 1 of Ticket #3423, comment 9


Ignore:
Timestamp:
02/14/2018 06:27:00 AM (4 years ago)
Author:
Nao
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3423, comment 9

    initial v1  
    22
    331. Initiate a PTE Request: Either on Rosetta or translate.wordpress.org. Need to send username and project name.
    4 2. Create a public post: On a new Make P2, trac, or forum section.
    5 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.
     42. Create a public post: On a new Make P2, Trac, or forum section.
     53. 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 specific keyword.
    664. GTEs approve request or decline with reasons: The resolution is posted back to the system used in step 2.
    77
    8 Here are my thoughs on each steps.
     8Here are my thoughts on each step.
    99
    1010'''Step 1:'''
    11 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.
     11I 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.
    1212
    1313'''Step 2:'''