Notes from the Polyglots chat on October 18

Notes from the polyglots chat on Oct 18

Locale stats

Below stats are dated 2017-10-18 compared to 2017-10-11 (differences between brackets)

*Releases*: 169 (±0) locale, 12 (+1) up to date, 55 (-1) behind by minor versions, 29 (±0) behind by one major version, 13 (±0) behind more than one major version, 51 (±0) have site but never released, 9 (±0) have no site.

*Translations*: 169 (±0) total, 4 (-3) at 100%, 31 (+17) over 95%, 39 (-13) over 90%, 30 (-1) over 50%, 57 (±0) below 50%, 106 (±0) have a language pack generated, 8 (±0) have no project.

*Requests*: There are 43 unresolved editor requests out of 1 093 (+14) total and 15 unresolved locale requests out of 67 (+1) total.

*Translators*: There are 526 (+1) GTE, 1 955 (+12) PTE and 15 004 (+125) translation contributors.

(A wordpress.org account could have multiple roles over different locale)

*Site language*: 50,386% (+0,066%) of WordPress sites are running a translated WordPress site.

WordPress 4.9 release schedule

WCUS Polyglots team lead needed

– Aaron Campbell posted about needing someone to lead the Polyglots team during WCUS contributor day on Dec 5th  https://make.wordpress.org/polyglots/2017/10/04/wcus-contributor-day-leads-needed/

Cross Locale Project Translation Editors

We’re officially starting the Cross Locale Project Translation Editors program and trial period.

Criteria for a Cross-Locale Project Translation Editor

To be granted access to import/validate strings for more than one locale, an organisation/plugin/theme author must cover the following criteria:

  1. Make sure that the translators they hire use the community style guides and glossaries, or create ones based on them and provide public links.
  2. Create a new account for this role rather than using a personal one, and fill in the profile page with contact information so that the local translation team can get a hold of them.
  3. Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username) on the description of the new WordPress.org account
  4. List steps for other .org community volunteers to get involved in the review process
  5. Have a Slack account on chat.wordpress.org and provide notice to the General Translation Editors of each locale after imports.
  6. Update their WordPress.org name with a (CL PTE)

Handbook updates related to the Cross Locale PTE:

Other questions related to Cross Locale PTEs:

  • Who can create Cross Locale PTEs: @Petya and @Ocean90
  • How does importing work and what are the special CL PTE’s functions
    • 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.
    • Imported strings by CL PTE do not overwrite strings translated by a GTE or PTE
  • How will the trials be evaluated – GTEs can provide feedback on regular basis.

 

#weekly-meeting-notes