Polyglots weekly summary / chat notes May 16, 2018

Weekly stats

Releases:

  • 179 (+0) locales
  • 56 (±0) up to date
  • 15 (±0) behind by minor versions
  • 6 (±0) behind by one major version
  • 34 (±0) behind more than one major version
  • 52 (±0) have a site but never released
  • 16 (±0) have no site.

Translations:

  • 179 (±0) total
  • 12 (+1) at 100%
  • 61 (-1) over 95%
  • 5 (±0) over 90%
  • 29 (±0) over 50%
  • 57 (±0) below 50%
  • 109 (±0) have a language pack generated
  • 15 (±0) have no project

Requests:

There are 65 unresolved editor requests out of 1 566 (+26) total and 24 unresolved locale requests out of 85 (±0) total.

Translators:

There are 547 (+1) GTE, 2 413 (+21) PTE and 23 605 (+288) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language:

51,934% (+0,006%) of WordPress sites are running a translated WordPress site.

Discussion topics:

  • 4.9.6 status: final release is excepted this week. Global ping for translation has been posted.
  • GDPR translation: P2 post was published with resources & tips for translating GDPR

1st meeting, 2nd meeting (office hour)

#weekly-meeting-notes

#weekly-meetings

Polyglots weekly summary / chat notes May 9, 2018

Weekly stats

Releases:

  • 179 (+0) locales
  • 56 (±0) up to date
  • 15 (±0) behind by minor versions
  • 6 (±0) behind by one major version
  • 34 (±0) behind more than one major version
  • 52 (±1) have a site but never released
  • 16 (-1) have no site.

Translations:

  • 179 (±0) total
  • 11 (+11) at 100%
  • 5 (-1) over 90%
  • 29 (+4) over 50%
  • 57 (+1) below 50%
  • 109 (±0) have a language pack generated
  • 15 (-1) have no project

Requests:

There are 54 unresolved editor requests out of 1 540 (+12) total and 24 unresolved locale requests out of 85 (+1) total.

Translators:

There are 546 (+2) GTE, 2,392 (+8) PTE and 23,317 (+218) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language:

51,928% (+0,010%) of WordPress sites are running a translated WordPress site.

Discussion topics:

  • The pirate locale was added and 4.9.x is at 13%
  • 4.9.6 status: both RC & final release scheduled dates are delayed by 2 days each. Details of the schedule can be found here.
    • Petya to publish a global ping for GTEs after RC gets out on May 10th
  • GDPR translation: try to find reliable translation resources (government, organization, etc) and create glossary items as necessary
    • Polyglots leads to work on a P2 post listing resources for translating GDPR terms and other complicated terms in the new batch of strings. And reminding GTEs to update their glossaries with necessary terms
    • Resources list:
      • http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2016.119.01.0001.01.ENG
      • https://www.ppc.go.jp/enforcement/cooperation/cooperation/GDPR/
      • https://www.jetro.go.jp/world/reports/2016/01/dcfcebc8265a8943.html
    • Useful term descriptions list (thx @presskorp) https://wordpress.slack.com/archives/C02RP50LK/p1525862349000103
  • Improvement suggestions for viewing translators activity: https://meta.trac.wordpress.org/ticket/3613
  • Hint to locale translation rules instead to handbook https://meta.trac.wordpress.org/ticket/3522
  • WCEU contributor day leads needed: https://make.wordpress.org/polyglots/2018/05/02/wceu-wordcamp-europe-2018-contributor-day-mentors-and-projects/

1st meeting, 2nd meeting

#weekly-meeting-notes

Polyglots weekly summary / chat notes May 2, 2018

Weekly stats

Releases:

  • 179 (+7) locales
  • 56 (±0) up to date
  • 15 (±0) behind by minor versions
  • 6 (±0) behind by one major version
  • 34 (±0) behind more than one major version
  • 51 (±0) have site but never released
  • 17 (±0) have no site.

Translations:

  • 179 (+7) total
  • 0 (-62) at 100%
  • 76 (+61) over 95%
  • 6 (-1) over 90%
  • 25 (+1) over 50%
  • 56 (+1) below 50%
  • 109 (±0) have a language pack generated
  • 16 (+7) have no project.

Requests:

There are 56 unresolved editor requests out of 1,528 (+15) total and 23 unresolved locale requests out of 84 (±0) total.

Translators:

There are 544 (+3) GTE, 2,384 (+13) PTE and 23,099 (+221) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language:

51.918% (+0,021%) of WordPress sites are running a translated WordPress site.

Discussion topics:

  • Beta 4.9.6 status: Delayed by 2 days – the new date for beta is May 3rd. Lots of new strings (GDPR etc) are added in core and they should be relatively stable now. Details of the schedule can be found here.
  • JavaScript i18n: @swissspidy invites everyone to a meeting in #core-i18n on how to best handle translations of JavaScript functionality (May 8 17:00 UTC). For more info, see https://make.wordpress.org/core/2018/05/01/javascript-internationalization-the-missing-pieces/
  • WCEU contributor day polyglots team: call for mentors
  • WP15: Reminder to translate the celebration site and help local groups organize events

1st meeting, 2nd meeting

#weekly-meeting-notes

Polyglots weekly summary / chat notes April 11, 2018

Weekly stats

Releases:

  • 172 (±0) locales
  • 55 (+52) up to date
  • 16 (-52) behind by minor versions
  • 6 (±0) behind by one major version
  • 34 (±0) behind more than one major version
  • 51 (±0) have site but never released
  • 10 (±0) have no site.

Translations:

  • 172 (±0) total
  • 62 (+2) at 100%
  • 15 (-2) over 95%
  • 7 (±0) over 90%
  • 24 (±0) over 50%
  • 55 (±0) below 50%
  • 109 (±0) have a language pack generated
  • 9 (±0) have no project.

Requests:

There are 65 unresolved editor requests out of 1 475 (+21) total and 27 unresolved locale requests out of 85 (+1) total.

Translators:

There are 542 (+1) GTE, 2 321 (+26) PTE and 22 597 (+141) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language:

51,757% (-0,003%) of WordPress sites are running a translated WordPress site.

Discussion topics:

  • Weekly focus: About page new strings up for translation – https://translate.wordpress.org/projects/meta/wordpress-org
  • The WordPress Jargon Glossary is out – it’s a good source to reference in local style guides and instructions for translating. It’s been added to the Handbook.
  • Volunteers for locale research are needed. See this handbook page for details. Here’s a list of the waiting locales. If you’d like to get involve and help and you haven’t done locale research before, please reach out to @petya

#weekly-meeting-notes

Weekly update: April 4th, 2018

Stats

These are the polyglots stats of the week + notes from the polyglots chats on April 4th.

*Releases*: 172 (±0) locale, 3 (-56) up to date, 68 (+57) behind by minor versions, 6 (-1) behind by one major version, 34 (±0) behind more than one major version, 51 (±0) have site but never released, 10 (±0) have no site.

*Translations*: 172 (±0) total, 60 (+6) at 100%, 17 (-5) over 95%, 7 (-1) over 90%, 24 (±0) over 50%, 55 (±0) below 50%, 109 (±0) have a language pack generated, 9 (±0) have no project.

*Requests*: There are 67 unresolved editor requests out of 1 454 (+21) total and 26 unresolved locale requests out of 84 (+2) total.

*Translators*: There are 541 (+1) GTE, 2 295 (+12) PTE and 22 456 (+8035) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

*Site language*: 51,760% (+0,017%) of WordPress sites are running a translated WordPress site.

WordPress 4.9.5

WordPress 4.9.5 Security and Maintenance Release

Looks like automatic language packs haven’t kicked in yet, they’re expected to roll out today.

Other topics:

  • About page strings – let’s make it a priority project for the next few months – https://translate.wordpress.org/projects/meta/wordpress-org
  • Expanding your local translation community – join the discussion https://make.wordpress.org/polyglots/2018/03/09/do-you-have-tips-to-share-on-growing-your-translation-community/

Agenda for the Polyglots chat on November 15th

Dear polyglots,

We missed our slot for an Asia/Pacific chat this morning due to unavailability of anyone to lead it but we’ll have a chat at 11 UTC. Here’s a very short agenda for it, given we have one major priority today and that’s the release of 4.9 and having as many locales ready for it as we can.

  • Locale stats before the 4.9 release
  • WordPress 4.9 will be released today – prepare your locales
  • Open discussion

See you in #polyglots

#weekly-meeting-agenda, #weekly-meetings

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

Agenda for the Polyglots chat on Oct 18

Dear polyglots,

Here’s the agenda for the Polyglots chat today, October 18th:

  • Locale stats
  • WordPress 4.9 release schedule – soft and hard string freeze, alpha project
  • WCUS Polyglots team lead
  • Cross Locale Project Translation Editors – official start of the program
    • Documentation – criteria for Cross Locale PTEs
    • Who can create Cross Locale PTEs
    • How does importing work and what are the special CL PTE’s functions
    • How will the trials be evaluated

Quite a few important points to be discussed so it would be great to see more of you there.

Chat time:

Cheers,

Petya

#weekly-meeting-agenda

Agenda weekly Polyglots chat Oct 4, 2017

Agenda Polyglots chats Oct 4, 2017

Here’s an agenda for the chats this week. If you have anything you’d like to add, please leave a comment.

  • Weekly locale stats
  • Global WordPress Translation Day 3
  • Reminder: Keep up with editor requests
    • Regularly check if you’ve got any pending editor requests. As always, you can find them here (replace [YOUR_LOCALE] with your locale slug): https://make.wordpress.org/polyglots/tag/[YOUR_LOCALE]/?resolved=unresolved
    • Add your locale name as a notification at https://profiles.wordpress.org/[USERNAME]/profile/notifications/ and enter #yourlocale for automatic notifications.
  • translate.wordpress.org/stats
    • Due to database timeouts, the number of waiting strings per locale is not being updated since some 10 days (all other numbers on the page are still valid). Follow #3155-meta for updates.
  • WP 4.9 Beta 1 – Oct 4 is the tentative date. Expect new strings for translation to be released soon!
  • Open discussion

Chat times:

See you there!

#weekly-meeting-agenda, #weekly-meetings, #gwtd

Notes from the Polyglots Chats on July 26

Weekly locale stats

Releases: 169 (±0) locale, 61 (+2) up to date, 0 (±0) behind by minor versions, 34 (-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, 12 (-36) at 100%, 60 (+36) over 95%, 2 (±0) over 90%, 30 (±0) over 50%, 57 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 32 unresolved editor requests out of 914 (+12) total and 11 unresolved locale requests out of 59 (+1) total.

Translators: There are 503 (±0) GTE, 1 734 (+4) PTE and 14 472 (+91) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

Site language: 50,034% (+0,030%) of WordPress sites are running a translated WordPress site.

New strings for WordPress 4.8.1

Global WordPress Translation Day

Notes from the WP Translation Day Chat on July 19

Below you can find a recap of the GWTD3 (Global WordPress Translation Day) meeting.

Items

  • Global/Schedule
    • Defines goals for the event (GWTD1 : onboard translators and expand the team, GWTD2 : increase PTE and bridge between plugin authors and translators)
    • Review the outcome of community summit and contributor day goals as starting point to help with setting the schedule
    • Other proposals:
      • Streamline onboarding experience for new translators and PTE
      • Reduce the translation waiting list
      • Give the team a stronger presence
  • Website
    • First meeting was held and design started
    • The previous GWTD1 and GWTD2 websites will be archived so they can still be accessed later
  • Comms
    • An announcement post on make/polyglots is being drafted
    • Call for speakers poll needs review, check google docs or on the website. Should stay open until 1-Sept.
    • A handbook page for onboarding local events is being prepared
    • The TranslateWP Twitter account is now accessible by Comms
    • @petya will support comms for the content plan
  • Design
  • Livestream/speakers
    • Some speakers should be invited
    • The crowdcast account has been received

Next meeting

  • Wed 26 July, 09:00 UTC on the global wordpress.slack.com (so just before the 2nd polyglots meeting)

Action items – New

  • @tobifjellner Collect all links to summaries and other useful information of the previous events. Add them in the handbook or on the site
  • @casiepa reachout to organizer that have a meetup on a different date (@casiepa)

Action items – Open from last week

  • @nao to find out about the ‘local mentors’
  • @casiepa to link with ‘Processing’ for live data during the event

 

#gwtd, #polyglots

Agenda for the Polyglots chats on July 19th

Hello polyglots,

Here’s an agenda for the chat today.

  • Weekly locale stats
  • Please respond to your editor requests: there are 24 open editor requests. You can find them here (replace YOUR_LOCALE): https://make.wordpress.org/polyglots/tag/YOUR_LOCALE/?resolved=unresolved
  • Global WordPress Translation Day 3 Planning: The next meeting for organizers will take place between the first and the second Polyglots weekly meeting Wednesday 09:00 UTC on #polyglots-events – *NOTE, There is a new channel on wordpress.slack.com instead a separate Slack team!*
  • Open discussion

Chat times:

Global WordPress Translation Day – Chat times:

See you there!

#weekly-meeting-agenda, #weekly-meetings, #gwtd

Notes from the WP Translation Day Chat on July 12

Below you can find a recap of the first GWTD3 (Global WordPress Translation Day) meeting.

Date

  • Date: Agreed for Sat 30-Sept-2017
  • 24 hours from 00:00 to 23:59 +1 min UTC
  • 30-Sept is International Translation day and this year it’s on a Saturday too
  • Proposal for next years is to have GWTD the first Saturday on or after 30-Sept
  • 2.5 months should be sufficient to make it all happen

Teams and roles

  • Everyone is invited to help in any team where you think you fit in. The more hands, the less work! The spreadsheet is still here.
  • Team ‘leads’ are @zetaraffix for design, @coachbirgit for comms, @nao for outreach, @tobifjellner for website and @casiepa as overall GWTD lead and livestream

Next meeting

  • Wed 19 July, 09:00 UTC on the global wordpress.slack.com (so just before the 2nd polyglots meeting)

Extra items

  • Refrain from using abbreviation when making public statements, use WordPress Translation Day or WP Translation Day.

Action Items

  • @nao to find out about the ‘local mentors’
  • @casiepa to link with ‘Processing’ for live data during the event
  • @casiepa to check if the meetings can be held on wordpress.slack.com

 

Notes from the Polyglots Chats on July 12

Locale Stats

Releases: 169 (±0) locale, 58 (+1) up to date, 0 (±0) behind by minor versions, 37 (-1) 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, 46 (+2) at 100%, 26 (-2) 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 51 unresolved editor requests out of 887 (+6) total and 11 unresolved locale requests out of 57 (+2) total.

Translators: There are 503 (-1) GTE, 1 682 (+12) PTE and 14 284 (+86) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

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

Editor Requests

New support theme

GlotPress next release

GWTD 3

  • Weekly meeting and all subchannels on http://wptranslationday.slack.com/
  • A recap will be given in the weekly Polyglots meeting on the organization and a post will be published here on make/polyglots
  • Main items for this week’s meeting are the Date and the review of the Teams

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