Here are my (slightly) structured notes from the Polyglots and GlotPress meeting at WordCamp Europe Contributor day on September 29th.
If you were there, please feel free to add to the notes if you feel I missed something important.
Roadmap for GlotPress
- GlotPress is not even at 1.0 – Doesn’t have caching, doesn’t have translation memory. Who’s gonna work on it?
- Data Schema, different one – Nacin and Nikolay are going to work on that
- Next step: Include Themes and Plugins in GlotPress
- Be prepared for hundreds of new validators
- Find a way to fight spam and security issues
Promised: Marko will ship profiles for GlotPress before WCSF
Scaling the community
A lot of languages don’t have an active validator – we need to change that
Average number of strings:
- Themes – 200-300 strings
- Plugins – 150-200 strings
- Core – 4000 strings
- BuddyPress – 1400 strings
Next step for Polyglots and i18n: Plugins & Themes
There needs to be a way for readmes to be translated.
There’s a lot of potential to get WordPress to 90 different languages.
We need to find developers to help with translations who are not heavily involved with core.
How do we put all the plugins on GlotPress (translate.wordpress.org)?
30 000 plugins that need to be translated
Rosetta sites will have their own theme and plugin directories with all translated plugins and themes
need a search that will work across languages. Search for plugins and themes should target both the translated language and English.
We start with 25 plugins
We need a mechanism to block spammers better. For forums, for local sites.
- agreed that each global communit should have their own P2
- there will be functionality to approve comments as approve/delete/move to forum
@siobhan to get in touch with Jetpack ppl about subscribing to tag
- should have lists of validators. Lists of validators should also be on local sites.
Promised: Remkus is doing the forum theme for BB Press for the local sites/forums 🙂
We need to make it easier for validators to work
Redesigning GlotPress, improving the tools
Security concerns with strings
Possible decision: Two tears of validators. Trusted validators for the core project and some of the other main projects.
Other validators for all of the plugins etc.
Polyglots team leads
The current goal is to split the role of Polyglots lead in two:
Community role/team – pushing validators, pushing people, finding validators, pinging validators, giving validator rights, helping validators and translators get started. The goal is to have a team of community ppl from at least three different parts of the world.
Sam will document the specific tasks of the role of Community Lead for Polyglots and also the technical lead
- Select people from the existing validators and community
- Select people who we know are responsible and will get the job done
- Give them a long term role and back them up with others