Notes from the Polyglots chat on October 18

Notes from the polyglots chat on Oct 18

Locale stats

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

*Releases*: 169 (±0) locale, 12 (+1) up to date, 55 (-1) behind by minor versions, 29 (±0) behind by one major version, 13 (±0) behind more than one major version, 51 (±0) have site but never released, 9 (±0) have no site.

*Translations*: 169 (±0) total, 4 (-3) at 100%, 31 (+17) over 95%, 39 (-13) over 90%, 30 (-1) over 50%, 57 (±0) below 50%, 106 (±0) have a language pack generated, 8 (±0) have no project.

*Requests*: There are 43 unresolved editor requests out of 1 093 (+14) total and 15 unresolved locale requests out of 67 (+1) total.

*Translators*: There are 526 (+1) GTE, 1 955 (+12) PTE and 15 004 (+125) translation contributors.

(A wordpress.org account could have multiple roles over different locale)

*Site language*: 50,386% (+0,066%) of WordPress sites are running a translated WordPress site.

WordPress 4.9 release schedule

WCUS Polyglots team lead needed

– Aaron Campbell posted about needing someone to lead the Polyglots team during WCUS contributor day on Dec 5th  https://make.wordpress.org/polyglots/2017/10/04/wcus-contributor-day-leads-needed/

Cross Locale Project Translation Editors

We’re officially starting the Cross Locale Project Translation Editors program and trial period.

Criteria for a Cross-Locale Project Translation Editor

To be granted access to import/validate strings for more than one locale, an organisation/plugin/theme author must cover the following criteria:

  1. Make sure that the translators they hire use the community style guides and glossaries, or create ones based on them and provide public links.
  2. Create a new account for this role rather than using a personal one, and fill in the profile page with contact information so that the local translation team can get a hold of them.
  3. Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username) on the description of the new WordPress.org account
  4. List steps for other .org community volunteers to get involved in the review process
  5. Have a Slack account on chat.wordpress.org and provide notice to the General Translation Editors of each locale after imports.
  6. Update their WordPress.org name with a (CL PTE)

Handbook updates related to the Cross Locale PTE:

Other questions related to Cross Locale PTEs:

  • Who can create Cross Locale PTEs: @Petya and @Ocean90
  • How does importing work and what are the special CL PTE’s functions
    • Specific user accounts (cross-locale PTEs) are able to import and approve translations for specific projects for all locales.
    • A cross-locale PTE can import (or translate through UI) untranslated strings as current.
    • A cross-locale PTE can import (or translate through UI) translated (by the community) strings as waiting.
    • Translations by a cross-locale PTE can be overwritten by a regular PTE or a GTE.
    • Imported strings by CL PTE do not overwrite strings translated by a GTE or PTE
  • How will the trials be evaluated – GTEs can provide feedback on regular basis.

 

#weekly-meeting-notes

Notes from the Polyglots chats on June 28, 2017

Notes from the Polyglots chats on June 28, 2017

Agenda

  • Locale stats
  • PTEonboading docs
  • Open discussion

Locale Stats

*Releases:* 169 (±0) locale, 56 (+2) up to date, 0 (±0) behind by minor versions, 39 (-2) 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, 42 (+6) at 100%, 30 (-6) over 95%, 2 (±0) over 90%, 29 (±0) over 50%, 58 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

*Requests:* There are 48 unresolved editor requests out of 864 (+16) total and 9 unresolved locale requests out of 55 (+1) total.

*Translators:* There are 504 (-1) GTE, 1 657 (+17) PTE and 14 119 (+109) translation contributors.

(A wordpress.org account could have multiple roles over different locale)

*Site language:* 49,895% (+0,048%) of WordPress sites are running a translated WordPress site.

Team news

New page about the various leader roles in the Polyglots team: https://make.wordpress.org/polyglots/handbook/polyglots-global-team-leads-and-mentors/

More updates from the summit & contributor day are on their way, some notes are in the meeting notes from last week: https://make.wordpress.org/polyglots/2017/06/26/notes-from-the-polyglots-chats-on-june-21/

PTEonboarding documents

In the last week’s chat, Birgit brought up a great point about how hard it is for new PTEs and theme/plugin developers to understand the whole translator approval process.

She drafted two docs as “skeletons”:

For developers:
https://docs.google.com/document/d/18XBAYmRbAyWGb8RiIjPxDQeuY-DVwg1XAYmuNU2kpVg/edit?usp=sharing

For translators:
https://docs.google.com/document/d/1fSoXhOeLwxx0qJtEXOKGLICYHeLrz85FTxg9wX-cMQY/edit

Several people (@Nao @tobifjellner @zetaraffix) have made comments in the second document, so that one will be used for the continued work, going forward.

@coachbirgit will soon finalize the first version of this document. It will be one document with some special notes for developers. This is meant to function as a skeleton. Each locale is free to adjust it to their needs and translate, if they want.

Even if a locale decides to use this document in English, there are certain things they may want to add themselves, like: chat resources, people you may contact, language resources, locale style guide…

@nao suggested that it might be useful for developers if it would be possible to create one document in English, which would describe the situation for most locales in one place.

@coachbirgit commented that some general documents would be good, both aimed at translator and at developers. In addition, this “skeleton” document may be used by locales when they describe their particular rules and processes. Currently, some limited information of this type is hidden deep inside the FAQ section of our handbook. ( https://make.wordpress.org/polyglots/handbook/frequently-asked-questions/#how-do-some-locales-manage-pte-requests )

@nao suggested that a page aimed at developers might have the topic “How to get your plugin/themes translated” or similar, since not all people know about our internal terminology (PTE, GTE, etc.) Perhaps it could be good to even have some graphic explanation of the various roles we have defined.

A short discussion followed about the need for locale sites to have their own handbook pages. (Related ticket https://meta.trac.wordpress.org/ticket/1919 ) Further discussion whether special handbook functionality would be needed may be done in that ticket.

@wolly pointed out that one may use certain styles to position a TOC in the left margin on a Rosetta page and gave an example:

<div class=”col-2 sidebar” style=”margin-left: 0;”>
<ul class=”submenu”>
<li class=”subcurrent”>Come iniziare</li>
<li><a href=”https://it.wordpress.org/traduzioni/#reg_stil”>Registro e tono</a></li>
<li><a href=”https://it.wordpress.org/traduzioni/#reg_gram”>Regole grammaticali</a></li>
<li><a href=”https://it.wordpress.org/traduzioni/#terms”>Un po’ di terminologia “Polyglots”</a></li>
<li><a href=”https://it.wordpress.org/pte-status-requests-by-devs-for-italian-localization-the-guidelines/”>PTE status requests by Devs for Italian localization: the guidelines.</a></li>
</ul>
</div>

Conclusion on the PTEonboarding discussion:

  • The PTEonboarding draft is in a good shape to get a transfer to polyglots/handbook
  • As long as the local sites don’t have a handbook functionality, we suggest a HTML code snippet for TOCs on local sites pages
  • Local teams can decide if they want to translate the PTEonboarding skeleton into their language or only adjust it to their needs (links to slack, resscourcen etc.)

Several people offered their support in creating visual elements for the PTEonboarding project. @semblance_er @zetaraffix and @sheilagomes @coachbirgit will contact these people separately to discuss what can be done.

Other topics

On Friday (June 23) there was an issue where localized release packages disappeared for a short period of time, but that seems to be resolved now. If you notice anything strange in your list of releases, write a note in the channel #meta-i18n

#weekly-meeting-notes

Notes from the Polyglots Chats on May 31st

Locale Stats

Releases: 169 (±0) locale, 63 (-5) up to date, 32 (+5) 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, 16 (-49) at 100%, 56 (+49) over 95%, 2 (-2) over 90%, 29 (+2) over 50%, 58 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 39 unresolved editor requests out of 801 (+25) total and 5 unresolved locale requests out of 49 (+1) total.

Translators: There are 406 (+4) GTE, 1 576 (+28) PTE and 13 619 (+364) translation contributors. (A wordpress.org account could have multiple roles over different locale)

Site language: 49,745% (+0,063%) of WordPress sites are running a translated WordPress site. Upcoming Release

Translating WordPress 4.8

  • 4.8 RC1 is out, final release is targeted to be on June 8 (#)
  • The About page wording may change (#)
  • String freeze schedule: June 1
  • No news on video/subtitles yet.

Finalizing WCEU Contributor Day Topics

  • 120 people will contribute to Polyglots of which 23 completely new, 48 contributed and 46 (very) experienced.
  • “New General Translation Editors onboarding / Mentorship program and new translation contributors onboarding plan” – Similar to the Community Team, how about putting together something like their training program? Or at least, a checklist or some sort. More structured way to get people started. (@nao)
    • @tobifjellner said sv_SE team is working on a local version of onboarding doc. Would be good to collect existing materials from teams and share good & bad practices (style, glossary and work procedure).
  • Contributor onboarding
    • @fxbenard points out that contributors mostly come to translate something they use, and then disappear
    • How to ‘review’ a contributors work in a quicker way (it’s very frustrating if work has been done but it takes ages before it gets approved)
    • Proposed goal: Prepare a written strategy for effectively onboarding new contributors (e.g. list of attention points and draft list of actions, to be detailed more after WCEU ?)
  • PTE Onboarding
    • Proposed goal: Clarify the role of the PTE for new contributors and sign up as many new PTEs as we can
  • Translating
    • Proposed goal: Complete at least 1 plugin/theme/project for each locale that has contributors present during Cday
  • GTE – Compare experiences
    • @lasacco would  love to know from the other GTEs which are the things going well or failed in their locale
    • Proposed goal: Compare GTE experiences and come with a list of Do/Don’t items. Adding the ‘How did I solve this’ where possible.
  • @luisrull and @arnaudbroes would love to talk about strategies to improved polyglots communities engagement and efficiency, plus helping new people
  • Inform contributors what to do after adding suggestions
    • @tobifjellner: there needs to be information flowing about where to look.
    • @pedromendonca: The biggest income a new contributor can have is the help of another humans. Know how and where to put questions, discuss doubts,…
    • Information could be links to polyglots handbook, to page(s) on localized Rosetta sites, to the list of local slacks, etc.
    • What to do if there is no PTE, or how can the contributor somewhere link to the existing PTE?
    • Proposed goal: Create a list of items where information/pointers should be improved and what information should be given.
  • Statistics/chat/notification inside the translate.wordpress.org platform site
    • @vitormadeira indicates that would be a (somehow) easy feature to start motivating people who contribute for one project and just leave…
    • No comparison / top tables , but related to ‘self-details’: how many strings one have already contributed, How many strings of “my” strings were approved, How many of “my” strings have been rejected, what projects did one work on, …
    • @sheilagomes and @vitormadeira pointed out that other ways could be explored to ‘lock’ translations or have the possibility to communicate (chat?)
    • Also if a GTE is maintaining a plugin, it looks like there is no PTE for it
    • Proposed goal: Creat a list of how the community sees possible improvements to GlotPress
  • Waiting strings
    • @lasacco indicates that they have a problem in managing the many waiting strings
    • @pedromendonca indicates that this could be because of a too low number of PTE and/or low or unclear communication
    • Some locales have global PTE and the GTE that deal with them. Other locales wait for a ping or until a PTE is appointed
    • Proposed goal: Create a list of approaches to reduce the list of waiting strings
  • @pedromendonca thinks also on how to improve consistency in some of the most widely used plugins.

Open Topics

  • i18n of default plugin (#): Readme is fully translatable as of now, but there is no further plan for i18n right now. Akismet can be used as a sample if needed.

Asia-Pacific slack meeting log

2nd meeting log

#weekly-meeting-notes, #weekly-meetings

Notes from the Polyglots Chat on May 17th

Locale Stats

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) GTE, 1 548 (+42) PTE and 13 255 (-874) translation contributors. (A 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.

4.8 beta 1

4.7.5 Security and Maintenance Release

Get Involved banner and flyer

  • A page will be added in the WordCamp handbook linking to the templates like this English PDF or this half-page one.
  • A French version is on its way (for WCEU), but if you also want the docs in your own language, add the translation to https://translate.wordpress.org/projects/meta/get-involved and the Community Team will create the banners/flyers and share them from that page in the handbook.
  • The details on how to get the final Get-involved flyer will be posted in the community WordCamp handbook, @casiepa will crosspost it in #polyglots Slack for info. For now, let’s do the translation job on our side and when done, ‘ping’ in #community-team to ask for creating the PDFs.

Security White Paper Translation

GWTD

  • The videos from GWTD2 with ‘acceptable sound quality’ have been published on WordPress.tv
  • GWTD3 Call for leads: leads of the event itself and some of the areas of event organization are needed. Mark yourself on the “Team” tab here if you’re interested.

Open Discussion

  • @divyadeepsawhney asked about a way to integrate Google Translate with GlotPress.
    • Make sure not to use machine translation as it is (without manual review)
    • GP Machine Translate plugin (not for use on translate.wordpress.org, external install only)
    • Poedit Pro (paid version) comes with machine translation suggestions, but the downside is that the locale glossary is not integrated since it’s outside of translate.wordpress.org.
  • @petya informed that 117 people signed up for WCEU Contributor Day (and 50 as second choice). The first 2 workshops (Intro and GlotPress) will be lead by resp. @glueckpress and @ocean90 . For the 3rd workshop on the glossaries the lead is still to be defined. Any GTE could do this.

#weekly-meeting-notes

Notes from the Polyglots chats on April 12th

Locale Stats

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) GTE, 1 447 (+31) PTE and 13 745 (+173) translation contributors. (A 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.

WPTranslationDay3

  • Event organization spreadsheet is now ready: https://docs.google.com/spreadsheets/d/1Fecq1StAPn9nDgabGMLdXiqszWkkxP6-5cM5YHXwLPg/edit#gid=1361186426 (thanks @casiepa)
  • Our main goal right now is to gather an organizing team. Volunteer responsibilities are described in this post. You can add yourself from here.
  • Local event organizers in Hyderabad, Lucknow (India), Tokyo (Japan), İstanbul (Turkey), and Bangkok (Thailand) are interested in having a meetup. Also Mumbai

Open Discussion/Announcement

  • According to @emre, “Waiting” strings count for #tr_TR is below 5,000 now thanks to @turker who singlehandedly moderated over 15k strings!
  • @sergeybiryukov has created ticket https://meta.trac.wordpress.org/ticket/2728 so GTE get notified automatically when editor requests arrive for their locale

Asia-Pacific slack meeting log

Europe-Africa-Americas slack meeting log

#weekly-meeting-notes

Notes from the Polyglots chats on April 5th

Asia-Pacific meeting log

Locale Stats

Releases: 169 (±0) locale, 68 (+1) up to date, 27 (-1) 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%, 6 (+2) over 95%, 5 (±0) over 90%, 26 (-1) 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 708 (+19) total and 5 unresolved locale requests out of 45 (±0) total.

Translators: There are 500 (-2) GTE, 1 416 (+25) PTE and 13 572 (+99) translation contributors. (A wordpress.org account could have multiple roles over different locale)

Site language: 49,282% (+0,117%) of WordPress sites are running a translated WordPress site.

WPTranslationDay3

  • Several Indian & Japanese communities are planning to host local meetups, including possible meetup during WordCamp Nagpur.
  • Indian locale GTEs (Hindi, Marathi, and Gujarati) are working on style guides & glossaries to be completed before the events.

WordPress Community Summit reps for Polyglots Team

Open Discussion

  • A unified Slack team for all Indian regions and locale is being proposed – @fitehal suggested to post the idea on WP India Group
  • @chandrapatel asked about Rosetta site news subscription.
    • Currently, there is no subscription feature – leave a comment on meta ticket #727
    • If you want to show local news to users on the wp-admin dashboard, you can edit these strings to your Rosetta site URLs
    • @mayuko mentioned the Nearby WordPress Events widget the community team is working on. Feedback for the plugin is welcomed.

#weekly-meeting-notes, #weekly-meetings

Notes from the Polyglots chats on March 8th

Locale stats

Releases: 164 (±0) locale, 64 (-32) up to date, 31 (+31) behind by minor versions, 0 (±0) behind by one major version, 14 (±0) behind more than one major version, 46 (+1) have site but never released, 9 (±0) have no site.

Translations: 164 (±0) total, 64 (±0) at 100%, 5 (±0) over 95%, 5 (±0) over 90%, 28 (±0) over 50%, 54 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 27 unresolved editor requests out of 659 (+9) total and 13 unresolved locale requests out of 45 (+1) total.

Translators: There are 494 (+2) GTE, 1 362 (+18) PTE and 13 117 (+82) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language: 48,856% (+0,048%) of WordPress sites are running a translated WordPress site.

Technical Updates

  • WordPress 4.7.3 was just released. Let’s make sure to announce it and encourage everyone to upgrade.
  • No new strings for translation.

New support theme for the Rosetta sites

To see the result, check e.g. the DE support site: https://de.wordpress.org/support/

WCEU contributor day

Volunteers have been found, speakers are being evaluated.

Make sure to comment this post if you’re attending WCEU and plan on going to WCEU contributor day.

Also related to WCEU – Community summit topics & representative nominees were posted.

Open Discussion


That’s all for this week!

Cheers,
Naoko & Pascal.

#weekly-meeting-notes

Notes from the Polyglots chats on January 25

Locale stats

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

Releases: 164 (±0) locale, 68 (+3) up to date, 1 (-2) behind by minor versions, 12 (±0) behind by one major version, 16 (-1) behind more than one major version, 58 (±0) have site but never released, 9 (±0) have no site.
Translations: 164 (±0) total, 64 (±0) at 100%, 4 (±0) 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 21 unresolved editor requests out of 597 (+12) total and 10 unresolved locale requests out of 42 (+1) total.

Translators: There are 483 (±0) GTE, 1 261 (+10) PTE and 12 434 (+139) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

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

Outreach Campaign on Rosetta sites

  • See detailed notes on https://make.wordpress.org/polyglots/2017/01/18/notes-from-the-polyglots-chats-on-january-18/
  • Rosetta sites come very high in search results when people search for WordPress in a specific location and keeping those sites updated with both the localized WordPress important announcement (new versions, basically the content of wordpress.org/news) and local content – events, discussions, etc, can be very beneficial
  • #gu locale manager and translators (@chandrapatel, @afzalmulatani, @mayur) & #ja locale manager (@naokomc) said they plan on posting more about meetups to the blog
  • #hi locale manager (@ankit-k-gupta) added a new editor (@juhise) to help with posting more news to the Rosetta site
  • You want to help us in this campaign ? Please let us know in a comment or on #polyglots

Open Discussion

  • WP for iOS app release is coming up soon, so please check Waiting translations for those locales with the app : https://translate.wordpress.org/projects/apps/ios
  • Italia (@lasacco) is organizing a PTE day to review pending strings. More info in the next weeks
  • The Greek WordPress Community (@dyrer) has redesigned the website

 

#weekly-meeting-notes

Notes from the Polyglots chats on January 18

Locale stats

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) GTE, 1 251 (+18) PTE and 12 295 (+62) translation contributors.
(A 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)).

  • Armenian (#hy), Persian (#fa_IR) and Welsh (#cy) seem to still be at 4.7 . @luisrull will contact them to see if they need help with the release

Tech update

Outreach Campaign on Rosetta sites

  • @petya proposes a review of the Rosetta sites for the released/active locales and reaching out to communities in different countries on the possible use of Rosetta because some might not be aware that they are welcome to use their Rosetta sites to announce events and discuss local community topics. So to focus on working with the community team and make Rosetta sites more useful.
  • Volunteers are needed to help make this happen. The job is mostly talking to people here on Slack.
  • Actions would consist of:
    • Review all Rosetta sites and see who are not updated regularly
    • Check if there are meetups/WordCamps in the location the site is built for
    • Reach out to those organisers and ask them if they’d be ok with announcing the events on the Rosetta site as well
  • Communities that seem to be really using Rosetta already are Romania, Italy and Bulgaria
  • Contents that can go on Rosetta:
    • Translations of the release posts
    • Announcements for events
    • Local contributor updates starting with a page on how to join the translation team
  • @francina already wrote a first page in the handbook: https://make.wordpress.org/polyglots/handbook/rosetta/setting-up-your-local-site/rosetta-for-the-community/

Open Discussion

  • Some plugin authors from the top plugin list were contacted and informed how easy it was to get on translate.wordpress.org.
  • @juhise is looking for volunteers to help with #hi_IN translation
  • @petya would like to have a page on Rosetta displaying all local users and their roles. @tobifjellner was proposing to maybe also add an opt-out.
  • The Camptix for WordCamps plugin is since yesterday available on https://translate.wordpress.org/projects/wp-plugins/camptix . Please review your language or assign a PTE where and if possible.

Action items

  • @petya : chat to the community team about making organisers aware of the Rosetta review
  • @luisrull : contact the 3 locales to see if they need help with releasing (@casiepa)
  • @casiepa : Propose spreadsheet for the Rosetta review
  • @casiepa : Check for volunteers and lead of the Rosetta review during next meeting (@casiepa)
  • @casiepa : Check for existing trac tickets about a Rosetta page displaying local users and roles

 

#weekly-meeting-notes

Notes from the Polyglots chats on Jan 4th

Locale stats

Releases

164 (±0) locale, 66 (+1) up to date, 0 (±0) behind by minor versions, 13 (±0) behind by one major version, 17 (-1) behind more than one major version, 59 (±0) have site but never released, 9 (±0) have no site.

Pinging the GTEs of locales that are translated more than 70% but behind more than one major version. It would be good to get in touch so we can help you release for the latest version. You can catch up on translations after that.

Translations

164 (±0) total, 63 (+2) at 100%, 3 (±0) over 95%, 4 (-1) over 90%, 32 (-1) over 50%, 55 (±0) below 50%, 86 (+1) have a language pack generated, 7 (±0) have no project.

Locale requests

12 unresolved locale requests out of 41 (+2) total.

Editor requests

There are 34 unresolved editor requests out of 561 (+7) total

Technical update

  • 4.7.1 might come in the next couple of days
  • Planned GlotPress releases in 2017 – the first GlotPress meeting will be on Jan 10th – everyone’s welcome to attend https://glotpress.blog/2017/01/03/2017-kick-off-meeting-on-january-10th-1700-utc/

Goals for 2017

For locale teams

  1. Translate WordPress to 100%
  2. Prepare your locale style guide and glossary
  3. Translate the top 10 plugins and themes to 100% in your language
  4. Expand your local teams with more project translation editors.

For the global Polyglots team

  • 100 locales at 100% by the end of 2017
  • Top 10 plugins translated to 100% for the top 12 languages
  • Global glossaries and reject with feedback (among many improvements) for GlotPress
  • Expand the Polyglots leadership team
  • Organise at least one WordPress Translation Day

 

#weekly-meeting-notes

Notes from the Polyglots Chats on December 7

Locale Stats

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

Releases: 164 (±0) locale, 47 (-27) up to date, 0 (±0) behind by minor versions, 27 (+22) behind by one major version, 21 (+5) behind more than one major version, 60 (±0) have site but never released, 9 (±0) have no site. Translations: 164 (±0) total, 53 (+26) at 100%, 6 (-8) over 95%, 4 (-9) over 90%, 37 (-9) over 50%, 57 (±0) below 50%, 84 (+1) have a language pack generated, 7 (±0) have no project.

Requests: There are 27 unresolved editor requests out of 520 (+10) total and 8 unresolved locale requests out of 35 (±0) total.

Translators: There are 482 (+6) GTE, 1 165 (+8) PTE and 11 781 (+165) translation contributors. (A wordpress.org account could have multiple roles over different locale)

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

Manual releases

If your locale is translated at more than 95% you might want to do a manual release and finish the translations later. That’s valid especially if you are currently behind one or more major versions, which disables the download button on your Rosetta site.

To release manually, please follow these instructions:

Releasing WordPress Packages

If you require assistance, ping @petya or @ocean90 here on in #Polyglots on Slack.

Release Video Subtitle

  • How to subtitle the video
  • 42 subtitles uploaded, 2 currently not working (zh-cn and zh-tw: both are in process of being fixed), 1 incomplete (Telugu) (via @casiepa)

Post-release To-do’s

  • Translate the release post and publish it on your Rosetta site.
  • Important: When you translate the release post, please do not include the names of all the contributors to it, instead, link to the original post for the full list of contributors. Including the names of all contributors pings them every time on WP Slack as they get a mention. Linking to the original post is a good alternative.
  • A good idea is to include a list of your translators to the release post in your language, especially if the translation team completed the translations before the release. Example: https://goo.gl/HT36XN
  • WordPress installation requirements are updated. Let’s make sure the Rosetta & documentation site are current
  • Translate or read the master list for 4.7 on English forums

WP for iOS 6.8

And finally, thank you so much to everyone who stepped up and translated WordPress in the 4.7 release cycle. You did an amazing job with a very short notice with both the About page strings and the release video.

Keep up with the amazing work you’re doing.

#weekly-meeting-notes

Notes from the Polyglots chats on November 30

Locale stats

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)).

Tech update

WordPress 4.7 release

  • We are in soft string freeze. All translators are kindly requested to focus on the remaining strings to get all locale to 100%
  • No news on the subtitles for the video
  • Release deadline of 6-Dec seems to be maintained.

Open Discussion

#weekly-meeting-notes

Notes from the Polyglots chats on November 23rd

Locale stats

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) GTE, 1 149 (+17) PTE and 12 469 (+167) translation contributors.
(A 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)).

Tech update

  • No specific updates. Waiting for soft freeze.
  • Strings like ‘resource’ have changed to more appropriate terms.
  • Release deadline of 6-Dec seems to be maintained.

Open Discussion

  • ‘Older’ WordPress releases (like 4.1.x, 4.2.x) will remain on GlotPress, but the most important ones are of course Developement and current 4.6.x. Newer locales don’t have to spend time in translating the old ones.
  • Having a team with different competences brings in the correct balance for translating

 

#weekly-meeting-notes

Notes from the Polyglots chats on November 16th

Locale stats

  • Locale stats before the soft freeze

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) GTE, 1 132 (+33) PTE and 12 302 (+437) translation contributors.
(A 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)).

WP TranslationDay Recap & Stats

Stats:

A detailed post coming soon, but here are some quick updates

  • WPTranslationDay stats are in this spreadsheet – thanks @ocean90 for providing those
  • Translated strings – 60426 for GWTD 2 vs 40350 for GWTD1
  • Number of people translating GWTD 2 – 740 vs GWTD 1 – 448
  • Number of locales translated GWTD2 – 133 vs GWTD1 – 54
  • Number of new translators – 253
  • Most active locales: Ja (9716), es (6176), de formal and informal (5662), it (5270), tr (4362), ru (4308), sr (4257), bg (3181), mr (1287), sk (1220), lo (1178) (All locale info is in the Locale stats tab of the spreadsheet)
  • Number of local events – GWTD 2 – 67 vs GWTD – 39
  • Live streaming viewers – 473
  • Number of translated strings: 60426
  • Number of projects that got new translations: 590
  • Number of locales that got new translations: 133

Takeaways and decisions about the next GWTD

  • Assemble a team with clear responsibilities before starting to organise – organise it like a wordcamp
  • Help local events connect to the GTEs for the locales they’re going to translate
  • Have it once a year
  • Do trial runs with all speakers to avoid technical issues
  • Research Google Live and Hangouts on air as an alternative to CrowdCast to avoid people needing to register to watch the stream

A full recap with takeaways and more stats is coming later today/tomorrow to make/polyglots

WordPress 4.7 development cycle

  • The original WordPress 4.7 development cycle has been changed
  • Soft freeze planned for November 17th
  • Hard freeze planned for November 29th
  • The about page strings ticket on track is live so we should watch it and take part if needed
  • No news on the release video yet, Petya to check with Helen
  • All GTEs will get a ping to prepare their locales on the dates of the soft freeze and hard freeze

iOS App translations

  • WordPress iOS app version 6.7 is up for translation – if your team is translating the apps, give the dev team a hand.

 

#weekly-meeting-notes

Notes from the Polyglots chats on Nov 2nd

  • Locale Stats

Releases

163 (±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, 60 (±0) have site but never released, 8 (±0) have no site.

Translations

163 (±0) total, 4 (-65) at 100%, 5 (+2) over 95%, 17 (+12) over 90%, 75 (+49) over 50%, 55 (+2) below 50%, 82 (±0) have a language pack generated, 7 (±0) have no project.

Requests

There are 23 unresolved editor requests out of 456 (+7) total and 10 unresolved locale requests out of 33 (±0) total.

Translators

There are 466 (+2) GTE, 1 090 (+8) PTE and 11 779 (+69) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language

52,335% (-0,137%) of the WordPress sites are running in en_US (English (US)).

WordPress 4.7 strings are in for translation

As @ocean90 posted earlier this week, the WordPress 4.7 strings are available for translation in the Development branch

Strings for WordPress 4.7 are available for translation

WordPress 4.7 is planned for December 6th. Information about soft string freeze and hard string freeze is coming in the next few days, but the core team is planning them on RC1, November 15th (soft freeze) and the final RC on November 29th (hard freeze).

Petya is talking to Helen about the Release video and will provide information about that as soon as the planning starts there.

Global WordPress Translation Day

  • We have 51 events on the Locale events tab with 10 more days to go, the map is updated with the latest data as well
  • Schedule is ready and published on the site, a couple of slots still missing and to be filled
  • The team is working on community sessions, ping Nao, Luis or Francina if you would like to participate
  • If you haven’t signed up for the live streaming, you can do it at  https://www.crowdcast.io/e/gwtd2

 

#weekly-meeting-notes