[wp-meta] [Making WordPress.org] #2000: Infrastructure for Cross-Locale PTEs

[Making WordPress.org]

#2000: Infrastructure for Cross-Locale PTEs
--------------------------------------+-----------------
 Reporter:  akirk                     |      Owner:
     Type:  task                      |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+-----------------
 As [https://wordpress.slack.com/archives/meta-i18n/p1473253227000030
 discussed on September 7th in Slack], there are some changes necessary to
 allow cross-locale PTEs on translate.wordpress.org (see
 [https://make.wordpress.org/polyglots/2016/05/27/cross-locale-pte-trial/
 Cross-Locale PTE Trial] for more background).

 It was agreed that
 * Specific user accounts (cross-locale PTEs) are able to import and
 approve translations for specific projects for all locales.
 * A cross-locale PTE can import (or translate through UI) untranslated
 strings as current.
 * A cross-locale PTE can import (or translate through UI) translated (by
 the community) strings as waiting.
 * Translations by a cross-locale PTE can be overwritten by a regular PTE
 or a GTE.

 This will need:
  * An interface (admin.php?page=add-cross-locale-pte) to assign the
 GlotPress permission which needs:
     * an input field for username/email
     * The project list/table as it already exists in the PTE assigning
 interface
     * A submit button
  * Filters in GlotPress to allow this (PR on [https://github.com/GlotPress
 /GlotPress-WP GlotPress-WP] to follow).
  * Code in wporg-gp-rosetta-roles to enforce the permissions listed above.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2000>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org