Notes from the polyglots chat on Oct 18
Locale 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/ 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 A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale., 1 955 (+12) PTE 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. and 15 004 (+125) translation contributors.
(A wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://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
- WordPress 4.9 release schedule – soft and hard string freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead., alpha project
- 4.9.1 now available for translation https://make.wordpress.org/polyglots/2017/10/10/start-translating-wordpress-4-9/
- 4.9 release schedule: https://make.wordpress.org/core/4-9/
- Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4 – October 23rd
- RC A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. & soft string freeze – October 30th
- Final RC + hard string freeze – November 6th
- Nov 13th – dry run
- November 14th – target release date
WCUS Polyglots team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. lead needed
– Aaron Campbell posted about needing someone to lead the Polyglots team during WCUS contributor day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. on Dec 5th https://make.wordpress.org/polyglots/2017/10/04/wcus-contributor-day-leads-needed/
Cross Locale Project Translation Editors Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles:
General Translation Editor and Project Translation Editor
We’re officially starting the Cross Locale Project Translation Editors program and trial period.
Criteria for a Cross-Locale Project Translation Editor A Cross-Locale Project Translation Editor is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localize their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors.
To be granted access to import/validate strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. for more than one locale, an organisation/plugin 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 author must cover the following criteria:
- Make sure that the translators they hire use the community style guides and glossaries, or create ones based on them and provide public links.
- 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.
- Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username) on the description of the new WordPress.org account
- List steps for other .org community volunteers to get involved in the review process
- Have a Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. account on chat.wordpress.org and provide notice to the General Translation Editors of each locale after imports.
- Update their WordPress.org name with a (CL PTE)
Handbook updates related to the Cross Locale PTE:
- Polyglots handbook updated
- Plugin and Theme developer handbook updated:
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 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/.
- A cross-locale PTE can import (or translate through UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.) 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.