Agenda for the Polyglots chat on July 6th

Dear Polyglots,

Here’s the agenda for the chat today, see you on Slack!

See you there!

Agenda for the Polyglots chat on June 29th

Dear Polyglots,

Here’s the agenda for the chat today, see you on Slack!

  • Locale stats
    • Releases
    • Translations
    • Pinging GTEs of unreleased locales for latest versions
  • Technical updates
  • Résumé of WordCamp Europe and the Contributor Day
    • Please share your achievements for yourself and your locale
  • Open discussion

See you there!

#weekly-meeting-agenda

Contributor Day WCEU 2016 

The WordCamp Europe was a blast. After two days with great talks, chats and a remarkable party called WCEUball we attended to the Contributor Day on Sunday. We’d love to share our achievements with you and for the records.

In the Polyglots meetings of May 11th and May 18th, 2016 the preparations for the WCEU contributor day were on the table. We agreed that we’d identify a couple of goals for the Polyglots team at WordCamp Europe.

So far, 20% of the attendees have “signed up” to help the Polyglots team at WordCamp Europe 2016.
The contributor day organization confirmed these team leads for the Polyglots team:

Additionally, Bego (@pixolin), Francesca (@francina), Raffaella (@zetaraffix), Sergey (@sergey), Luis (@luisrull), Peter (@savione) were there to answer questions and helping to onboard on translations.

Preparation of our goals

To be able to prepare for the contributor day well, we’ll define a couple of goals for the day. They’ll be listed here and explained below.

  • Onboard new translators
  • Translate
  • Find (new) Translation Editors for locales that need them
  • FAQ page in the Polyglots handbook
  • Global translation day videos in the Polyglots handbook

Onboard new translators

Lead: Naoko Takano
Assistants: Bego Mario Garde, Denise VanDeCruze

Given the size of the WordCamp Europe 2016 contributor day, it’s highly likely that we’ll have new translators in our team. Our goal is to show them the basics, get them started as a translator, and make sure they leave the day proud of their achievements.

Conditionally the great venue for the Contributor day we had two rooms for the Polyglots team provided.
In one room we could onboard new translators with the help of live presentation via beamer. Bego did a great job and used our prepared slides from the Global WordPress Translation Day to demonstrate how translations and related tasks like approval process, Glossary, and Translation Style Guide are defined and where to find. Nao held a workshop after lunch and talked about translation tips and how to get involved.

While new polyglots got onboarded, the more experienced contributors worked on the translations in their own locale.

Translations in numbers

Over 6495 strings in total were translated, 4587 of those got approved, 1720 had the status “waiting”. Only 17 Strings were rejected which is tremendous in terms of the quality.

We had 71 signups for the translations team on the Contributor Day and the counts above got done by 142 users in total because of many remote working polyglots during the day.

(Thanks for the stats, @ocean90 !)

It’s absolutely awesome! Thank you all very much for that! You rock the game!

Find (new) Translation Editors for locales that need them

We tried to get some more numbers. Following numbers about participants broken down by locale are doubtless incomplete, but they show what we achieved.

Counted participants via announcement on Slack to @CoachBirgit:

  • Finnish (fi): 5
  • Turkish (tr_TR): 1
  • German (de_DE): 7 (+ 4 new translators and 1 PTE gained)
  • Japanese (ja): 1 (+ 2 new translators)
  • Italian (it_IT):5
  • Spanish (es-ES): 3
  • Hungarian (hu_HU): 1
  • Romanian (ro_RO): 1
  • Polish (pl_PL): 1
  • Malayalam (ml_IN): 1
  • Dutch (nl_NL): 2 (+1 new translator)
  • Danish (da_DK): 1
  • Russian (ru_RU): 1
  • Basque (eu): 1
  • Montenegrin (me_ME): 1
  • Dutch (Belgium) (nl_BE): 1
  • French (fr_FR): 1 new translator

We would like to complete this list. Please share your personal achievement at Contributor Day in the comment of this post. And one more request to the existing GTEs – please share your counts, how many new TE or PTE your locale gained on the Contributor day.

FAQ page in the Polyglots handbook

By virtue of the great preparatory work from @casiepa the FAQ draft is now as page transferred to the Polyglots handbooks. So there was no pressure to do this on the contributor day.

Global translation day videos in the Polyglots handbook

During the Global Translation Day, we recorded a fair number (24) videos about helping the polyglots. The more general videos can be included in the handbook, the specific ones on the rosetta sites. We’ll need some people to coordinate and do this. Unfortunately the task leader @francina couldn’t work on this on the Contributor Day. So she created a task list to add the recorded material to the related handbook pages.

Open discussion / round table

The Polyglots mentor team had some topics on the list to discuss.

  1. The Persian situation
  2. Cross PTE trial

Results of this discussion

  1. The requests from Farhad Sakhaei to become one of the GTE for fa_IR are on the review list from Samuel Sidler. He will mediate between the counterparties. We would appreciate if every discussion on Slack about this topic now stops until the situation is not cleared via escalation process.
  2. We will do a trial for the Cross PTE request. Details will follow in a separate post in the near future when the benchmark data is figured out.

UX Design for GlotPress

Some polyglots participated in the discussions for the UX Design for our beloved (sometimes annoying) translation platform and WordPress plugin GlotPress, which was lead by @akirk and @isaackeyet. The GlotPress team did a lot of brainstorming. The results will be posted as soon as possible on blog.glotpress.org.

Words of gratitude

Dear friends, you all did a great job. Please stay tuned with your contributions. An open source project like WordPress needs a lot of love from passionate people like you are.

I thank you so much, I can´t find the right words how impressed I am about our beloved community especially the polyglots!

And I want to thank every single organizer and volunteer that made WCEU an unforgettable event, so THANK YOU!

See you soon – at latest on WordCamp Europe 2017 in Paris!

#wceu, #wordcamp, #wordcamp-europe

Agenda for the Polyglots chat on June 22nd

Dear Polyglots,

Here’s the agenda for the chat today, see you on Slack!

See you there!

P.S. Wishing everyone who is traveling to WordCamp Europe a safe trip.

#weekly-meeting-agenda

Agenda for the Polyglots chat on June 15th

Dear Polyglots,

Here’s the agenda for the chat today, see you on Slack!

See you there!

#weekly-meeting-agenda

Agenda for the Polyglots chat on May, 18th

Dear Polyglots,

Here’s the agenda for the chat today, see you on Slack!

  • Locale stats after the 4.5.2 maintenance release
    • Taking care of 100% translated locales that haven’t released
    • Pinging GTEs of locales that are at 95%+ for manual release
  • Technical update (GlotPress releases and changes, WordPress releases)
  • Handbook FAQ page status
  • Brainstorm about credits for translation contributors on plugins/themes directory
  • Shiny updates review (@obenland https://make.wordpress.org/polyglots/2016/05/16/shiny-updates-review/)
  • WordCamp Europe contributor day – task list / focus list
  • Open discussion

See you there!

#weekly-meeting-agenda

Agenda for the Polyglots chat on May, 11th

Dear Polyglots,

Here’s the agenda for the chat today, see you on Slack!

  • Locale stats after the 4.5.2 maintenance release
    • Taking care of 100% translated locales that haven’t released
    • Pinging GTEs of locales that are at 95%+ for manual release
  • Technical update (GlotPress releases and changes, WordPress releases)
  • Handbook FAQ page status
  • WordCamp Europe contributor day
    • We will have an unprecedented number of contributors and many polyglots – let’s make a plan for onboarding them
    • We will have a lot of seasoned contributors – let’s decide what we want to discuss / work on
  • Open discussion

See you there!

 

#weekly-meeting-agenda

Notes from the Polyglots chat on Jan 27th

Locale stats

Releases: 158 locales. 56 locales up to date. 2 locales behind by minor versions. (#lv, #te)  11 locales behind by one major version.(#vi, #tl, #es_VE#sl_SI, #gd, #fa_IR, #ka_GE,#cs_CZ, #bs_BA, #bn_BD,#hy19 locales behind more than one major version. 55 locales have a site but never released. 15 locales don᾿t have a site.

Translations: 158 locales. 56 locales at 100%. 3 locales have more than 95%. 4 locales have more than 90%. 27 locales have more than 50%. 55 locales have less than 50%.

5 locale requests waiting.

ToDo:

  • Taco will post a comment and mention the GTEs of the behind locales below these notes

Tech updates

no updates for today.

Let’s talk communication

– how to address plugin author and translation contributor requests on the P2

Suggested places to improve information about translating your plugin:

Please include other links to pages in the ecosystem where adding information regarding plugin translations would be good. Improving documentation will help (see last week’s steps) but we should also try and be a bit more patient with demanding plugin authors.

Suggestions for the requests:

One page, one form, the necessary info in short, linked to the full handbook posts, one simple URL to refer people to (by @eyesx

About Expectations

As @tacoverdo mentioned, the problem is expectation management. We obviously fail in setting the right expectations. @casiepa added that we are all human and volunteers, but indeed, expectations and ‘responsibilities’ need to be clearer.

@chantalc created a Doc, with the first draft about Polyglots expectations. https://docs.google.com/document/d/1ON4DCjQP-le2GCeMgov2aO7exCljWZILHmKX0aTfcvg/edit#

ToDo

  • Create standard responses for plugin/theme authors demanding you translate their projects
  • Create a workflow diagram for the request process
  • Expand the handbook section ‘How to become a translation editor‘ to explain how and when translation contributors should contact GTEs, and how GTEs should handle PTE requests.

Translation sprints

– the poll is already open (until January 31st) – let’s send it to our communities

ToDo

Open discussion

No special topic to discuss today. If you have further questions, please feel free to leave a comment below.

Next meeting will be on Wednesday, February 3d, at 11 am UTC in the #Polyglots channel on Slack.

See you there!

#notes, #weekly-meeting-notes

Agenda for the Polyglots chat on January 27th

Hey everyone,

Here’s a short agenda for the chat this week. Add anything you’d like to discuss in the comments below

  • Locale stats
  • Tech update
  • Let’s talk communication – how to address plugin author and translation contributor requests on the P2
  • Translation sprints – the poll is open until 31st – let’s send it to our communities
  • Open discussion

See you on Slack!

Agenda for the Polyglots chat on Jan 6th

Hey everyone & happy new year!!

Are you good started into the new year?

Here’s the agenda for the Polyglots chat today, 11 am UTC:

  • Locale stats
  • Tech update and release help
  • Goals for 2016 – let’s line them up and figure out how to reach them
  • Contributor survey for 2015 – http://wordpressdotorg.polldaddy.com/s/2015-wordpress-contributor-survey
  • Open discussion
    • Legal consequences while translating
      • What if a translation contributor finds some legal critical phrases in a theme or plugin?
      • Who is legally responsible for statements and texts in themes and plugins that are legally dubious? – developer, translation editor or translation contributor?

If you’d like to add anything to the agenda, please comment below or show up for the open discussion at the end of the chat.

I’ll see you all in Slack!

Cheers,

Birgit

#weekly-meeting-agenda

Off for holidays

wpmas

Wapmas

Hello everyone,

As most of you know, holidays are coming. Time to be thankful and to reflect on ourselves. It’s also time to take a break.

The next weekly Polyglots chat will be on Jan, 6th.

Please allow for a bit more time for requests on both the Polyglots P2 and on Slack, as there will be fewer of us around before the New Year.

Thank you!

We would like to say THANK YOU to everyone, who has contributed to the WordPress project and we wish you and your family a peaceful time and a good start of the new year.

See you in 2016!

Kind regards,
Birgit

Image Credits: Gemma Garner & Scott Evans

#announcement

Agenda for the Polyglots chat at Dec 3/4

Agenda for the Polyglots chats Dec 3/4

Hello dear polyglots,

Almost time for the scheduled Wednesday and Thursday Polyglots chats. Here’s the proposed agenda:

What happened last week

We are waiting for the string freeze and the translation project for the new theme Twenty Fifteen

Agenda

  • get informed about the status to WordPress 4.1
  • other discussions

For today, we have a short agenda.

Cheers

#polyglots-meeting, #week, #weekly-meeting-agenda

Notes from the Polyglots meetings Nov 26th & Nov 27th

Notes from the Polyglots meetings Nov 26th & Nov 27th

Here you´ll find the notes from the last #polyglots weekly chat meeting

Agenda

Slack Chat Archive

Disussed topics

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.

Current stats

  • 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

 Other Questions/Suggestions

  • 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:

Dec 3d, Wednesdays at 11:00 UTC and Dec 4th, Thursdays at 2:00 UTC.

Sidenote: We wish our american friends great Thanksgiving holidays!

#weekly-meeting-notes

Discussion: Using translation tools with GlotPress?

Discussion: Using translation tools with GlotPress?

In our weekly chat meeting today, we´ve discussed over a feature request, to implement Google Translator into GlotPress. A feature, that was build in in the past, but was removed after another discussion. (s. here) Sidenote: Some very ambitious validators were misusing it to get their language at 100% and it resulted in very poor translations  Since API keys are needed and if those aren’t passed it will not be displayed and not  because of misusing it.

 

Upcoming concerns from chat

  • Is it useful, to let the locale editor decide, if translation tools are in use
  • it would maybe useful to get a first raw translations for new locale, but for using it needs proofreading
  • a validator for a locale should be a good native speaker, so doesn´t need a Google Translator
  • If a validator decides to misuse the tool, there’s a very little chance anyone will be able to notice unless a user speaks up.
  • Keep in mind that the Google Translate API is a paid service
  • Maybe part of solution, or just making easier for translators is to list on local site links to online tools for translating and checking spell

Let´s discuss

  • What are your best practices as translator / validator?
  • Do you use any translation tools for raw translations?

 

#google-translate, #machine-translation, #translation-tools

Agenda for the Polyglots chats Nov 26/27

Agenda for the Polyglots chats Nov 26/27

Hello dear polyglots,

Almost time for the scheduled Wednesday and Thursday Polyglots chats. Here’s the proposed agenda:

What happened last week and why

There were a series of bugs in GlotPress due to some temporary changes in the database connection code on WordPress.org.

We ended up with a lot of empty string values instead of NULLs for columns like `context` and `plural`. GlotPress expected `null` specifically in few places in the codebase. The specific consequences were duplicate originals, few incorrectly updated originals, and extra PO file fields for some strings (context and plural).

The duplicated originals were removed, the team made sure that we no longer allow duplicates. We also made the translations of incorrectly updated originals fuzzy, so that translators could verify the translations were right. Today we fixed PO exports.

So a few things worth mentioning:

  • Kudos to everyone who reported, tested and participated in isolating and fixing the issues. Team work!
  • 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. We’re working with the core team on retroactively pushing language packs to those who already updated their installs.

Current stats:

  • Locale state (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.)
  • Locales that are up to date with incomplete packages (Admin’s not at 100%) – how can we help them build their packages (Arabic, Catalan, Chinese (China), Chinese (Taiwan), Danish, Estonian, Finnish, Hungarian, Icelandic, Indonesian, Macedonian, Norwegian (Bokmål), Serbian, Spanish (Mexico), Thai)
  • We have two brand new locales (Oriya and Lingala), now let’s get those guys started. At the #wcldn contributor day we also rebooted a locale that was half done (was never properly added) and found a validator for it – Kinyarwanda.

Technical chat recap

  • We had a technical chat for Polyglots last night. What happened:
  • We have a lot of people who stepped up to help: @japh, @CoachBirgit, @ocean90, @miyauchi, @eathanasiadis.
  • Next steps: The technical crew should hang out on the P2 and on Slack more, technical list with all the responsibilities documented, partnering up technical leads with community leads so they can work together in their region

Cheers!

#polyglots-meeting, #weekly-meeting-agenda, #weekly-meetings