Notes from the Polyglot chats on Jan 7th and Jan 8th

Notes from the Polyglot chats on Jan 7th and Jan 8th

Hey everyone,

Here is a summary of last week’s polyglots chats:

Logs: Jan 7th Chat | Jan 8th Chat.

Some stats:

(Don’t forget these are from last week)

Jan 7 Status:

  • 139 localesLocale 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/. 49 locales up to date.
  • 0 locales behind by minor versions.
  • 12 locales behind by one major version.
  • From these, lets try and bring the closest ones to 100%.

There are 6 of these that are pretty close to being done:

  • Chinese (Taiwan): 99%
  • Czeck: 87%
  • Estonian: 92%
  • Lithuanian: 74%
  • Macedoian: 89%
  • Tagalog: 32%

18 locales behind more than one major version.

  • Norwegian Nynorsk is stuck at 3.9.2, but will hopefully have a new validatorValidator See translation editor. soon and will pick up
  • Uzbek is at 3.0.1, but someone requested validator rights for it yesterday and we hope they can pick it up, it has a lot of waiting stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. too.
  • Swiss German de_CH will hopefully pick up after @swissspidy expressed interest in picking it up. The Swiss German situation has been a bit messy, there are three different locales for it, including swg which will probably be retired in favour of de_CH that will try and make use of the de translations and add their own flavour where needed. Nick Weisser and Pascal Birchler will work on it, thank you guys!

 39 locales have a site but never released

22 locales don᾿t have a site

~9,450,000 translations entries in the database table

We have two requests for new locales: for Balochi Sourthern and for Arpitan

Goals for 2015

  • Aim to have 70 very active, very updated locales by the end of 2015.
  • Focus on bringing in and mentoring new validators. Everyone’s help here will be invaluable – talk to people about your Polyglots work, find and inspire new translators to join.
    • Get Involved page linked from your local site’s primary menu.
    • Speaking and encouraging people to join the team at meetups
    • Translation sprints! Amazing idea, read more in @nao ‘s post and please share your thoughts!
  • Last year at the community summit, a lot of people didn’t know what Polyglots did. We should try and do something about this this year. Suggestions include talking about it at local meetups and WordCamps.
  • Aim to have 50% locales up to date, currently it’s just ~35% – this would mean cleaning inactive locales or trying to find validators for them
  • RosettaRosetta 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. sites are one thing that we will need to improve in 2015
  • Finish the Handbook.
  • Team P2s
  • An update on the Rosetta theme and a new bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. theme (hopefully)
  • Polyglots badges. Will help the team get a bit more visibility and hopefully encourage people to contribute more.
  • GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. will get a big push in 2015, that’s already happening and you can follow the process in #meta-i18n ( hopefully you’ve seen this: https://www.dropbox.com/s/q3lg6iee8szh1wj/ab-glotpress-v1.pdf?dl=0 )

  • bbPress 2.x

  • bPress 1.x forums need to be tested and imported into bbPress 2.x on each of xx.wordpress.org sites

  • The bbPress 1.x importer now imports 100% of the legacy data is now into bbPress 2.x.

  • Locale specific code will be retired in 2015 – which locales have it and if it’s essential as it can prevent the localeLocale 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/ from the ability to have automatically generated language packs? – will move to the next week’s agenda too.

Thanks, @japh, for leading the Asia / Pacific chat!

The next Polyglots chats are on on Wed, 14th Jan, 11:00 UTC and Thu, 15th Jan, 02:00 UTC on the #Polyglots channel on Slack.

Cheers!

Petya

#weekly-meeting-notes