Releases: 162 locales. 51 locales up to date. 0 locales behind by minor versions. 20 locales behind by one major version. 22 locales behind more than one major version. 61 locales have a site but never released. 8 locales don᾿t have a site.
Translations: 162 locales. 52 locales at 100%. 9 locales have more than 95% (5 of them at 99). 8 locales have more than 90%. 29 locales have more than 50%. 55 locales have less than 50%. 9 locales don᾿t have a WP project.
In March 2015, when we introduced the Polyglots badges, we had 319 GTEs and 4,690 translation contributors.
This morning, the stats looked like this:
- Translation Contributor: 10,059
- Translation Editor: 1,247
WordPress 4.6 releases
Two locales (Japanese and Malay) are at 100%, but haven’t released yet.
Reminder: For automatic releases to be packaged, the branch should be created in advance. If it was created after the release, it’ll only get picked up in the next 4 hours, or next 24 hours in a week after release.
@petya suggested that we should have a launch checklist like the one the core team does. It’s easy to separate a bunch of tasks including checking svn branches within the team, maybe we can work towards delegating some tasks around helping people release as well.
Keep in mind that once your locale falls behind more than one major version, it becomes inactive for either selecting on install or downloading from your local site. Please release the translations if they’re at more than 95%.
The goal is to have 70 released locales by the end of next week.
A reminder for everyone who translates their Planet string
If you’ve translated the Planet WordPress feed to include your locale support forums, you may need to update those to the new URLs.
For Japanese, for example, that would be changing
We’re working on the new Handbook structure here: https://docs.google.com/spreadsheets/d/1-qPU8FOMvJO5zhJwjXjcCRCBw9jPvhcN6h60_X9-Zpg/edit#gid=0
Some new page and new link suggestions:
- Add a GTE step by step guide to releasing your translations. We have extensive documentation around releases, but there should also be a simpler guide for people who do this for the first time and even for the more experienced contributors.
- Bundling custom functionality with your locale (with examples). Also – documenting our existing use cases.
- Add links to local Slack teams/IRC channels in the Glossaries and Style Guides by locale table.
- Add a link to the consistency tool as a separate page with instructions how to use it in the Translation Tools section.
- Add a Stats page as a part of our About The Polyglots Team section.
- Add a link to stats per locale: https://translate.wordpress.org/stats
- Add a link to stats of the active installs per locale: https://wordpress.org/about/stats/
- Add a link to overall locale stats: https://make.wordpress.org/polyglots/teams/
Again – the experienced contributors know about these pages, but they are not clearly visible for the newcomers or random visitors curious about the work of the team. And not clearly visible for other contributors as well.
Outstanding PTE/Locale requests
- Locale requests: Albanian (Kosovo) aka Shqip, es_DO, es_BO, Romani, Hausa.
- We have an open issue for updating Kyrgyz with its proper locale code.