Notes from the Polyglots meetings Nov 26th & Nov 27th
Here you´ll find the notes from the last #polyglots weekly chat meeting
Slack Chat Archive
What happened last week?
We had some trouble with the 4.0.1 because of a series of bugs in GlotPress due some temporary changes in the database. It was fixed very fast, thanks to all, who was involved.
Info: Only the 4.x (dev) branch was affected. You don´t need to rerelease older versions/tags
Reminder: If your language is missing strings, please rebuild and rerelease. This will make sure the users who update from now on will get the proper translation files.
- 37 locales up-to-date
- 18 locales behind by one minor version
- 4 locales behind by one major version
- 15 locales behind by two or more major versions.
- @markoheijnen will start displaying the percentage and changelog soon too and will flush stats values before every weekly meeting, to be up-to-date with correct data.
- Some locales that are up to date with incomplete packages (Admin’s not at 100%)
- Happiness: We have two brand new locales (Oriya and Lingala) and the Translators/Validators for Thai(@kazama), Tagalog (@krzheiyah) and Lao(@douantavanh) are now attended at our weekly meetings, this is great, because Asia was underrepresented in the past. Many thanks to @shinichin and @mayuko for knitting the connection
Recap technical lead chat meeting
We had a chat meeting for people, who wants to volunteer as a technical lead.
In the past, there were the people, who handled all technical stuff around #polyglots, overwhelmed with work. It is a volunteer work – everyone has a real life! So we don´t want to get people burnt out.
The stuff is now distributed on more shoulders. For the technical part we have a lot of people who stepped up to help: @japh, @ocean90, @miyauchi, @eathanasiadis, @sergeybiryukov, @netweb and @CoachBirgit
Many thanks for your attendance!
Next steps for the technical crew:
- hanging out on the P2 and on Slack more,
- technical list with all the responsibilities documented, @petya is working on that
- partnering up technical leads with community leads so they can work together in their region
- Importing translations into GlotPress is only recommended, if your locale is very new. Otherwise use only GlotPress for translations to avoid overwriting existing translations. Note: you need to check if the pot revision you used to translate it needs to match glotpress
- String freezeis proposed for the RC 1 at hopefully December, 1st 2014not later than Dec,3d coming week
- A lot of pain for #polyglots are the short time sequenzes, after string freeze and missing projects and branches on translate.wordpress.org
- The bbPress Theme is ready and commited – waiting for implementing to update the locale support forums from bbPress 1.x to 2.x
- The locale P2´s are planned – needs some changes for user roles, that will come with the new bbPress
- @netweb finished of the final parts of the 1.x importer on the weekend and now they are working on actual implementation of the where’s and how we’ll actually deploy etc
- Question came up, to implement Google Translator in GlotPress. This discussion will be continued on a separate post.
Next week’s Polyglots chats on Slack in the #Polyglots channel:
Sidenote: We wish our american friends great Thanksgiving holidays!