Localization and translation of HelpHub – Meeting notes

Attendees: @amieiro  @javiercasares  @glycymeris @battelfred  @estelaris @cbringmann @chanthaboune @nullbyte  @milana_cap  @tobifjellner  @courane01 @emmaht

Agenda: https://make.wordpress.org/docs/2024/06/10/localization-and-translation-of-helphub-during-wceu-2024/

Goal

The goal of this project is to create a process to facilitate and simplify the translation of WordPress.orgWordPress.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/ documentation into other languages. Perhaps in the future, the same process can be either replicated or used as a starting point for other teams to translate their documentation. 

What does MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. need to prepare Rosetta sites for the documentation page? 

Ticket discussion:  https://meta.trac.wordpress.org/ticket/7637

@estelaris reported that the Meta team doesn’t know the scope of adding this page to Rosetta sites currently, as the requirements differ from site to site. 

There are teams like JA(Japanese), FR (French), and IT (Italian) that have a great deal of the documentation already translated but still need the new site maps. Others, like BG (Bulgarian) and RU (Russian), still connect documentation to Codex. LT (Lithuanian) does not have either a support or documentation page. These are the few teams that met at WCEU or have been in touch with the docs team at different times.

Meta tickets will be opened for the sites linked to Codex to make sure everything is documented. It is important that the existing articles in a local language do not get lost.

@estelaris is writing documentation to help the meta team. This documentation includes the steps taken while the global documentation page was created and a spreadsheet with the redirects.

Another issue to consider is that this process will need a dedicated meta team member due to the amount of work involved.

Cross-team communication

The teams working on this project are GlotPress, Docs, Meta, Training, locales, and operations. We are communicating through the  #polyglots-multilingual-community on Slack.

Any updates or related posts will be posted on the Team Updates Make blog and cross-post to the #docs, #meta, #polyglots, and #training Make blogs.

Is the marketing involved in this project?

Not at the moment. The main goal is to focus on one team. Hopefully, the marketing team and other teams can replicate the translation processes developed by this project.

Other projects

Other projects that require translation are the Developer Resources and the Developer’s blog, which are in a subsite under developer.wordpress.org. Meta will need to resolve a very specific issue related to the developer site and that is the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to be used in Rosetta sites. It was mentioned at the meeting that translating the Developer blog is important because it provides timely information for developers.

Then there is Learn. The content from Learn is uploaded directly to the Learn site, and it is not linked to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. The training team also stores all languages on one site at this time, and Sensei LMS is not yet compatible with content in multiple languages. 

For the Rosetta sites, the scope for the new page /documentation/ was discussed and needs more feedback, this team should continue working with Meta to understand how to add the developer and other pages. 

What is the process?

These are the steps we would like to test:

  1. Create the project in GitHub.
  2. Translation and revision that all the content from the article is there
  3. Add the translation to GlotPress
  4. Review and approval by GTEs
  5. Post on the local documentation page

As an example, the Spanish team is translating articles from the project created in GitHub [ES] Traducción y localización de la documentación de usuarios finales. The French team has a different process. Until we have the correct tools to work on long translations, a local team should be flexible in its work.

GlotPress

GlotPress is used only to translate strings for themes, plugins, etc., but doesn’t have the capacity to translate long blocks of text. One way could be for each paragraph to be treated as a string.

The GlotPress team needs to create a pluginPlugin 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 to import data from different sources and another one to export this data, create new projects, and define a structure inside translate.wordpress.org. Once 90% of the content has been translated, it can be moved to a page.

Screenshots and videos should come from the local site. Jeff Matson built a tool that could automate updating the screenshots with a new version, but the code source and the state of the project are unknown. @courane01 will find out more.

Tasks

Docs team

  1. Finish the documentation for https://meta.trac.wordpress.org/ticket/7637
  2. Continue working with the translation teams to add their redirects

GlotPress

  1. Evaluate what is needed to translate long blocks of text in GlotPress.
  2. Creating a system for segment labeling.
  3. How to maintain versioning of previous translations.
  4. Which URLs work better with GlotPress, English only or English + other language?

Spanish team

  1. Translate at least 20 pages to start testing GlotPress and advise the GTEs.

Operations

  1. @cbringmann will coordinate any extra developer time needed.

Thoughts on GlotPress and GitHub

  • If using GitHub for versioning, is there another tool for labeling how the segments have been changing
  • Split a page into segments to maintain versioning and keep a record of previous versions.
  • Reuse translations as much as possible to avoid additional efforts.
  • Keep segments before and after the ones that are being translated to create context and meaning. That feature is part of professional translation software.
  • GlotPress doesn’t have this capability, perhaps changing the data format from the GetText infrastructure.
  • The Spanish team is finishing a GitHub contributor handbook for beginners. This will help new contributors learn to work with GitHub.
  • The workload is heavy on the reviewers; the documentation team has to decide which tools we will use for translation.
  • The workload for the GTEs will not increase significantly because everything will be in GlotPress.
  • All the text must be on one page, and the paragraphs must be in order.
  • During the translation, we need to compare the English and Spanish/other language versions. There is a problem with that option. When you enter a paragraph, it gets an ID. The problem is that when the English version is updated, we need to add more metadata to the original strings. We will investigate more about this issue.
  • Another issue with GlotPress is that it is string-based. If you have a string that says “no,” it will be translated the same everywhere. This is an issue because “no” can mean several things. It could be the opposite of yes, or it could be used as a shorthand for “number,” or it could mean something else.
  • The same concern shows in plugins and theme translations, but with plugins; one can ask the plugin developer to change one of the strings. With the documentation, the result will be a bad translation.

Versioning

  • The docs team wants to introduce documentation for different WordPress versions, this is a good time to start thinking about this as everything needs to be translated.
  • For instance, the single article is the Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., now the Navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site.. It has changed many times since rolling out the Site Editor. If someone wanted to read the documentation on the Navigation bar at 6.0 because their site uses 6.0, how do we work this out?
  • The Learn team can have a similar issue.
  • The code reference team uses taxonomies to resolve versioning issues.
  • The documentation has the latest version, but now it will add the previous version to the articles. How can this be incorporated into GlotPress?

Multilingual sites

  • There are solutions available to work with multilingual sites, and Phase 4 may occur in 3 or 4 years.
  • Meanwhile, where do we put the information? How do we move the pieces forward and be ready for when the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. can do it by itself?
  • How do we put the URLs back on the website? This has to be resolved before Phase 4
  • A solution could be having the articles in GlotPress, which can give that page an original ID. When the page is moved to WordPress, the original ID will move with it, but it will also remain as a master ID in GlotPress.
  • The main problem is that we still need to figure out where to store the information before phase 4.
  • To avoid wasting developers’ time, start translating what is available now (the most stable is end-user documentation).

Testing GlotPress

  • The Spanish team is working on the translation of the first categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. of end-user documentation and improving the glossary. That is about 20 articles/pages that can be used to test new GlotPress features.
  • Tests can be run from WordPress with the original article.

French community

  • The French community has about 90% of the end-user translated. 
  • Need to cross-reference the articles to create a table of redirects that will help the meta team when adding the fr.wordpress.org/documentation page. This is the only way to maintain what has already been translated.
  • The French translations may need to be updated, as the docs team removed all developer jargon from end-user documentation.
  • Any other information added to the articles must be discussed with the docs team before being added to the global English version or removed from the French article.
  • The articles must be one-on-one between English and other versions of the language.
  • The sitemap has to be translated into French.
  • All of these items are part of the meta ticket mentioned at the beginning of this article.

URLs

  • Since the URLs are all custom and not content, are they going to be translated?
  • The slug is a field in the database.
  • URLs should not be arbitrary but should be translated and not changeable.
  • Perhaps this should be a role responsibility, and only GTEs or locale managers can set it up.
  • What if slugs are not translated? Because there is a decision to be made. What will the correct slug be:
    es.wordpress.org/documentation/ or es.wordpress.org/documentacion/
  • This is another task for meta, which already is es.wordpress.org/support/. The full slug is in English.
  • Presently, the slugs are in 2 languages:
    https://es.wordpress.org/support/forum/manuales-y-resolucion-de-problemas/
  • Using a redirection table that links directly from wordpress.org.
  • Perhaps it is better to maintain all the slugs in English as they can maintain the same IDs, which will make it easier to synchronize.
  • Also, it would be easier to check on the translation status of a page in another language.
  • So if there is a page with a translated slug, we can redirect it only once to the English version (adding the language prefix). If everything is in English, it is easier to maintain.
  • In the long term, it is better to keep everything in English because when translations are not available, the site can remain in English.

Props to @courane01, @javiercasares and @nullbyte for reviewing and editing the notes.

#glotpress, #learnwp

Polyglots Team Update (November 30)

Our meeting agendas and notes:

Stats (between November 12th and 25th)

  • 48 (+3) locales are up-to-date. There are 12 locales (-2) behind by a minor version and 12 (-1) behind by a major version.
  • There are 21 unresolved editor requests out of 3,790 (+42) and 14 unresolved locale requests out of 145 (-1).
  • There are 686 GTEs (+1), 4,927 (+31) PTEs, and 47,174 (+368) translation contributors.
  • Non-en-US sites are now at 55.291% (+0.05%) of active installs.

Other updates

#polyglots

Marketing Team update for August 2020

Promoting new features and benefits from WordPress releases

For the working group focused on this, the last few months have been very busy. As a pilot working with other teams, we have researched and produced a series of questions and answers on 5.5 for end users and a social media pack. We hope the Q&As will be available soon on the HelpHub and thank everyone who has been involved from the team, the Release Squad, and the documentation and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. teams. We are also finalizing promotional material for Meetups.

We’re also working with the release squad and polyglots to explore how we can promote the meeting times to encourage more contributors across timezones to be involved. From this week, DevChat for 5.6 takes place on Wednesdays ay 05:00/ 5am UTC and 20:00/ 8pm UTC in the core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

🎉Supporting new contributors update

🆕 We continue to have a good influx of new joiners to the Marketing channel, either as visitors from other teams to assist with specific tasks or new contributors to the team itself.

If you have recently joined or wanting to get involved, our weekly meeting agenda is a good starting point for how to get involved in shadowing on a task or getting more actively involved. It also has our diary of events and meetings.

These are posted on the Make WordPress Marketing blog which you can find at https://make.wordpress.org/marketing/

🕑 We meet for our global weekly meeting on Wednesdays at 14:00 UTC, followed by collaboration sessions. These are great opportunities for joiners to the channel and contributors to learn more about our tasks and the team. We encourage asynchronous involvement with the meeting for 48hours after it takes place as we know the meeting time may not work for everyone.

☕ We have a virtual coffee break on Thursdays at 19:30 UTC. In addition there are a number of meetings during the week at different times as part of our commitment to inclusivity and providing opportunities across the timezones.

💻 We are planning our next induction session later this month. Let us know if you would like to attend. We cover the tools we use as well as provide a brief introduction to some of the areas we are working on.

✍️ Urgent tasks/ rolling or soon deadlines

  • if you have experience of researching for or writing social media for organizations or brands, we have lots of tasks for you
  • if you are an experienced developer or familiar with explaining the tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ process, we have release-focused tasks you can join. Contact myself (@abhanonstopnewsuk on Slack) or @meher to get involved
  • are you fluent in writing and speaking another language and have good presenting skills? Then you could help the project with our onboarding videos. Contact @OGlekler and @marks99
  • interested in promoting diversity within the project and in tech through drafting social media posts? Contact @Nalininonstopnewsuk and @lmurillom

Contributor events

We have supported a number of small group contributor events at recent WordCamps and Meetups, as well as some led by workplaces.

If your WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. or organization is planning a WordPress contributor event for staff, come and chat to us about marketing tasks we could plan for you.

Translation promotions

We continue to work with the wonderful #polyglots on marketing WordPress translation opportunities and achievements. We are focused on mini WordPress Translation Day events being planned for the end of September and beginning of October 2020 to coincide with International Translation Day celebrations. Could you support this promotion?

WPDiversity workshops promotion

We have a social media pack available to help promote these important events by the Diverse Speaker Training Group in the Community Team. These free to attend workshops offer support for members of marginalized or underrepresented groups. Contact myself , @nalininonstopnewsuk and @lmurillom to find out how you can use the prepared social media posts in your networks.

You can also help amplify the message by simply retweeting the messages on the WordCamp Central Twitter and Facebook accounts. They are tagged #WPDiversity in these channels. Help us promote the September 2020 events.

Meetup marketing and glossary update

Thanks for all the messages from about promoting Meetups and suggestions for the glossary. Please keep them coming in. Thanks to the community team for helping us promote these areas.

Useful links

Quarter 2 – 2020 Team updates, August 2020

Marketing team update – July 2020

Marketing team update – June 2020

#marketing-team

Polyglots team update – May 17, 2017

Meeting headlines

The following topics were discussed in the weekly meetings (6am and 10am UTC)

  • 4.8 BetaBeta 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. 1 and 4.7.5 releases
  • Get Involved flyer and banner
  • Security Whitepaper translation
  • Global WordPress Translation Day 3 – Call for organizers and videos from GWTD2

Full report available on https://make.wordpress.org/polyglots/2017/05/19/notes-from-the-polyglots-chat-on-may-17th/

Statistics

Releases: 169 (±0) locale, 68 (±0) up to date, 27 (±0) behind by minor versions, 0 (±0) 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, 65 (-1) at 100%, 7 (+2) over 95%, 4 (-1) over 90%, 27 (±0) over 50%, 58 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 31 unresolved editor requests out of 776 (+16) total and 4 unresolved locale requests out of 48 (-1) total.

Translators: There are 402 (-4) GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor., 1 548 (+42) PTE and 13 255 (-874) translation contributors. (A wordpress.orgWordPress.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,682% (+0,062%) of WordPress sites are running a translated WordPress site.

#polyglots

Polyglots team update – April 12, 2017

Meeting headlines

The following topics were discussed in the weekly meetings (6am and 10am UTC)

  • Global WordPress Translation Day 3 – Call for organizers

Full report available on https://make.wordpress.org/polyglots/2017/04/18/notes-from-the-polyglots-chats-on-april-12th/

Statistics

Below stats are dated 2017-04-12 compared to 2017-04-05 (differences between brackets)

Releases: 169 (±0) locale, 68 (±0) up to date, 27 (±0) behind by minor versions, 0 (±0) 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, 65 (±0) at 100%, 6 (±0) over 95%, 5 (±0) over 90%, 26 (±0) over 50%, 59 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 52 unresolved editor requests out of 726 (+18) total and 6 unresolved locale requests out of 47 (+2) total.

Translators: There are 501 (+1) GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor., 1 447 (+31) PTE and 13 745 (+173) translation contributors. (A wordpress.orgWordPress.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,373% (+0,091%) of WordPress sites are running a translated WordPress site.

#polyglots

Polyglots team update – March 29, 2017

Meeting headlines

The following topics were discussed in the weekly meetings (6am and 10am UTC)

Full report available on https://make.wordpress.org/polyglots/2017/03/29/notes-from-the-polyglots-chats-on-march-29th/

Statistics

Below stats are dated 2017-03-29 compared to 2017-03-22 (differences between brackets)

Releases: 169 (±0) locale, 67 (+2) up to date, 28 (-2) behind by minor versions, 0 (±0) 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, 66 (+1) at 100%, 4 (-1) over 95%, 5 (±0) over 90%, 27 (±0) over 50%, 59 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 38 unresolved editor requests out of 689 (+7) total and 5 unresolved locale requests out of 45 (-1) total.

#polyglots

Polyglots team update – January 18, 2017

Meeting headlines

The following topics were discussed in the weekly meetings (6am and 11am UTC)

  • Glotpress 2.3.0 is in BetaBeta 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.
  • Outreach Campaign on Rosetta sites

Full report available on https://make.wordpress.org/polyglots/2017/01/18/notes-from-the-polyglots-chats-on-january-18/

Statistics

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

Releases: 164 (±0) locale, 65 (-3) up to date, 3 (+3) behind by minor versions, 12 (±0) behind by one major version, 17 (±0) behind more than one major version, 58 (±0) have site but never released, 9 (±0) have no site.
Translations: 164 (±0) total, 64 (-1) at 100%, 4 (+1) over 95%, 3 (±0) over 90%, 31 (±0) over 50%, 55 (±0) below 50%, 87 (±0) have a language pack generated, 7 (±0) have no project.

Requests: There are 15 unresolved editor requests out of 585 (+8) total and 9 unresolved locale requests out of 41 (+1) total.

Translators: There are 483 (±0) GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor., 1 251 (+18) PTE and 12 295 (+62) translation contributors.
(A wordpress.orgWordPress.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: 51,762% (+0,010%) of the WordPress sites are running in en_US (English (US)).

#polyglots

Polyglots team update – November 30, 2016

Meeting headlines

The following topics were discussed in the weekly meetings (6am and 11am UTC)

  • WordPress 4.7 is in soft string freeze
  • Preferred languages research continues

Full report available on https://make.wordpress.org/polyglots/2016/12/02/notes-from-the-polyglots-chats-on-november-30/

Statistics

Below stats are dated 2016-11-30 compared to 2016-11-23 (differences between brackets)

Releases: 164 (±0) locale, 74 (+1) up to date, 0 (±0) behind by minor versions, 5 (±0) behind by one major version, 16 (-1) behind more than one major version, 60 (-1) have site but never released, 9 (+1) have no site.
Translations: 164 (±0) total, 27 (+27) at 100%, 14 (-17) over 95%, 13 (-5) over 90%, 46 (-6) over 50%, 57 (+1) below 50%, 83 (+1) have a language pack generated, 7 (±0) have no project.

Requests: There are 26 unresolved editor requests out of 510 (+17) total and 8 unresolved locale requests out of 35 (±0) total.

Site language: 51,891% (-0,078%) of the WordPress sites are running in en_US (English (US)).

#polyglots

Polyglots team update – November 23, 2016

Meeting headlines

The following topics were discussed in the weekly meeting (11am UTC)

  • Upcoming WordPress 4.7 soft freeze
  • Statistics

Full report available on https://make.wordpress.org/polyglots/2016/11/23/notes-from-the-polyglots-chats-on-november-23rd/

Statistics

Below stats are dated 2016-11-23 compared to 2016-11-16 (differences between brackets)

Releases: 164 (±0) locale, 73 (±0) up to date, 0 (±0) behind by minor versions, 5 (±0) behind by one major version, 17 (±0) behind more than one major version, 61 (±0) have site but never released, 8 (±0) have no site.
Translations: 164 (±0) total, 0 (-3) at 100%, 31 (+7) over 95%, 18 (-3) over 90%, 52 (-1) over 50%, 56 (±0) below 50%, 82 (±0) have a language pack generated, 7 (±0) have no project.
=> New strings arrived just before the weekly stats, so 100% is at 0.

Requests: There are 12 unresolved editor requests out of 493 (+13) total and 8 unresolved locale requests out of 35 (±0) total.

Translators: There are 476 (+1) GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor., 1 149 (+17) PTE and 12 469 (+167) translation contributors.
(A wordpress.orgWordPress.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: 51,969% (-0,061%) of the WordPress sites are running in en_US (English (US)).

#polyglots

Polyglots team update – November 16, 2016

Meeting headlines

The following topics were discussed in the weekly meetings (6am UTC and 11am UTC)

  • Global WordPress Translation Day Recap & Stats
  • WordPress 4.7 soft freeze of strings in the next days
  • Request for translation: iOSiOS The operating system used on iPhones and iPads. App translations

Full report available on https://make.wordpress.org/polyglots/2016/11/16/notes-from-the-polyglots-chats-on-november-16th/

Statistics

Below stats are dated 2016-11-16 compared to 2016-11-09 (differences between brackets)

Releases: 164 (+1) locale, 73 (±0) up to date, 0 (±0) behind by minor versions, 5 (±0) behind by one major version, 17 (±0) behind more than one major version, 61 (+1) have site but never released, 8 (±0) have no site.
Translations: 164 (+1) total, 3 (-6) at 100%, 24 (+15) over 95%, 21 (-2) over 90%, 53 (-7) over 50%, 56 (+1) below 50%, 82 (±0) have a language pack generated, 7 (±0) have no project.

Requests: There are 19 unresolved editor requests out of 480 (+20) total and 12 unresolved locale requests out of 35 (+2) total.

Translators: There are 475 (+9) GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor., 1 132 (+33) PTE and 12 302 (+437) translation contributors.
(A wordpress.orgWordPress.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: 52,030% (-0,148%) of the WordPress sites are running in en_US (English (US)).

#polyglots