Notes from the Polyglots chats on June 28, 2017
- 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
- PTEonboading docs
- Open discussion
*Releases:* 169 (±0) locale, 56 (+2) up to date, 0 (±0) behind by minor versions, 39 (-2) behind by one major version, 14 (±0) behind more than one major version, 51 (±0) have site but never released, 9 (±0) have no site.
*Translations:* 169 (±0) total, 42 (+6) at 100%, 30 (-6) over 95%, 2 (±0) over 90%, 29 (±0) over 50%, 58 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.
*Requests:* There are 48 unresolved editor requests out of 864 (+16) total and 9 unresolved locale requests out of 55 (+1) total.
*Translators:* There are 504 (-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 657 (+17) 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 14 119 (+109) 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:* 49,895% (+0,048%) of WordPress sites are running a translated WordPress site.
New page about the various leader roles in the 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/.: https://make.wordpress.org/polyglots/handbook/polyglots-global-team-leads-and-mentors/
More updates from the summit & 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/. are on their way, some notes are in the meeting notes from last week: https://make.wordpress.org/polyglots/2017/06/26/notes-from-the-polyglots-chats-on-june-21/
In the last week’s chat, Birgit brought up a great point about how hard it is for new PTEs and theme/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 developers to understand the whole translator approval process.
She drafted two docs as “skeletons”:
Several people (@Nao @tobifjellner @zetaraffix) have made comments in the second document, so that one will be used for the continued work, going forward.
@coachbirgit will soon finalize the first version of this document. It will be one document with some special notes for developers. This is meant to function as a skeleton. Each locale is free to adjust it to their needs and translate, if they want.
Even if a locale decides to use this document in English, there are certain things they may want to add themselves, like: chat resources, people you may contact, language resources, locale style guide…
@nao suggested that it might be useful for developers if it would be possible to create one document in English, which would describe the situation for most 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/ in one place.
@coachbirgit commented that some general documents would be good, both aimed at translator and at developers. In addition, this “skeleton” document may be used by locales when they describe their particular rules and processes. Currently, some limited information of this type is hidden deep inside the FAQ section of our handbook. ( https://make.wordpress.org/polyglots/handbook/frequently-asked-questions/#how-do-some-locales-manage-pte-requests )
@nao suggested that a page aimed at developers might have the topic “How to get your plugin/themes translated” or similar, since not all people know about our internal terminology (PTE, GTE, etc.) Perhaps it could be good to even have some graphic explanation of the various roles we have defined.
A short discussion followed about the need for locale sites to have their own handbook pages. (Related ticket https://meta.trac.wordpress.org/ticket/1919 ) Further discussion whether special handbook functionality would be needed may be done in that ticket.
@wolly pointed out that one may use certain styles to position a TOC in the left margin on a Rosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. page and gave an example:
<div class=”col-2 sidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.” style=”margin-left: 0;”>
<li class=”subcurrent”>Come iniziare</li>
<li><a href=”https://it.wordpress.org/traduzioni/#reg_stil”>Registro e tono</a></li>
<li><a href=”https://it.wordpress.org/traduzioni/#reg_gram”>Regole grammaticali</a></li>
<li><a href=”https://it.wordpress.org/traduzioni/#terms”>Un po’ di terminologia “Polyglots”</a></li>
<li><a href=”https://it.wordpress.org/pte-status-requests-by-devs-for-italian-localization-the-guidelines/”>PTE status requests by Devs for Italian localization: the guidelines.</a></li>
Conclusion on the PTEonboarding discussion:
- The PTEonboarding draft is in a good shape to get a transfer to polyglots/handbook
- As long as the local sites don’t have a handbook functionality, we suggest a HTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. code snippet for TOCs on local sites pages
- Local teams can decide if they want to translate the PTEonboarding skeleton into their language or only adjust it to their needs (links to 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/., resscourcen etc.)
Several people offered their support in creating visual elements for the PTEonboarding project. @semblance_er @zetaraffix and @sheilagomes @coachbirgit will contact these people separately to discuss what can be done.
On Friday (June 23) there was an issue where localized release packages disappeared for a short period of time, but that seems to be resolved now. If you notice anything strange in your list of releases, write a note in the channel #meta-i18n