Hello Polyglots,

I am the theme author of following WordPress Themes


Please add the following WordPress.org user as translation editor for their respective locales:


If you have any questions, just comment here. Thank you!


Hello Polyglots, I am the…

Hello Polyglots, I am the plugin author for Charitable. We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:


If you have any questions, just comment here. Thank you!


Hello Polyglots!

I am the user and the tester of WordPress for iOS, and I want to be able to approve translation for it.

I am also interesting in Themes and Plugins translations (e.g. Semicolon, Yoast SEO, WooCommerce).

Please add me as translation editor.

Thank you!


WooCommerce 2.7 de_DE and de_CH

Hi there, I’m GTE for de_CH core and WooCommerce. Wanted to start a discussion with my de_DE WooCommerce colleagues to coordinate translations for WooCommerce 2.7 release which we’re getting close to.

Not sure how this was done for 2.6, but right now the development trunk is at 76% (1121 untranslated strings seems to be too many), the latest stable release at 99%, but I guess the new 2.7 strings are not yet available in the latest stable release?

Trying to ping some of the editors and contributors to see if anyone’s available for discussion and contribution 😁

Translation editors: @fludwig-1 @gerdneumann @nachtigall
Translation contributors: @puncktcom @danielturgay @transl8or @keypi @dotnetdev @cpier @stefannagy @cpier @stefannagy @cuberasan @woodpresser @soean @domcie @mobotter


Hello Polyglots, I am the…

Hello Polyglots,

I am the plugin author for JoomSport (https://wordpress.org/plugins/joomsport-sports-league-results-management/). I would like to add my account as a PTE for Polish locale:

If you have any questions, just comment here. Thank you!


Notes from the Polyglots chats on February 22

Locale stats

Below stats are dated 2017-02-22 compared to 2017-02-15 (differences between brackets)

Releases: 164 (±0) locale, 96 (+1) up to date, 0 (±0) behind by minor versions, 0 (±0) behind by one major version, 14 (±0) behind more than one major version, 45 (-1) have site but never released, 9 (±0) have no site.
Translations: 164 (±0) total, 63 (±0) at 100%, 6 (±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 639 (+8) total and 12 unresolved locale requests out of 44 (+1) total.

Translators: There are 492 (+4) GTE, 1 319 (+13) PTE and 12 899 (+117) translation contributors.
(A wordpress.org account could have multiple roles over different locale)

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

Technical Updates

  • @ocean90 informed that the site translate.wordpress.org received updates:
    • WordPress toolbar active for all (with links to login and register)
    • Color scheme changed to blue
    • Translate settings in the profile menu
  • Cross-Locale PTE testing ongoing:
  • GlotPress updated to 2.3.0 on translate.wordpress.org
  • Rosetta Showcase: If you locale site uses the showcase feature, you can now use custom screenshots. (see https://meta.trac.wordpress.org/changeset/4937)

Community Summit

Rosetta Outreach

Open Discussion

  • New GlotDict now detects missing end of strings (like … . ? ! )
  • Strings have been added in the last 2 weeks for iOS, forums, Rosetta, WordCamp, etc. Please have a look with your team
  • @mte90 reminded the PTEbot for people willing to receive a plugin with waiting strings on a regular bases and the BulkRejectGP for GlotPress

#polyglots, #weekly-meeting-notes

Hello Polyglots, I am the…

Hello Polyglots,

I am the plugin author for RunPress (https://wordpress.org/plugins/runpress/).

I have a great translation editor that I would like to be able to approve translation for my plugin. Please add the following WordPress.org user as translation editor for their respective locales:

If you have any questions, just comment here. Thank you!


Hello Polyglots, I am the…

Hello Polyglots, I am the theme author for the Customizr theme. I have a number of great translation editors that I would like to be able to approve translation for my theme. Please add the following WordPress.org users as translation editors for their respective locales:

If you have any questions, just comment here. Thank you!


Hi @bjornjohansen, I use “Theme…

Hi @bjornjohansen, I use “Theme My Login” and need Norwegian translation. I see it has lots of suggestions waiting to be approved (for 8 months or more). It seems more translation editors are needed. What can I do to help?

Simen Røkaas
(native Norwegian but sticks to English in an English forum)


Hi Polyglots! I’m following-up to…

Hi Polyglots! I’m following-up to my request for a new locale from December, our org is kind of anxious to get this project started. Can someone look at it for us? thanks! https://make.wordpress.org/polyglots/2016/12/29/hi-id-like-to-request/


Hi Polyglots, I’m the author…

Hi Polyglots, I’m the author of following WordPress Themes

and would like to make the following user editor for Italian Locale




Hello Polyglots, I am the…

Hello Polyglots,

I am the plugin author for JoomSport (https://wordpress.org/plugins/joomsport-sports-league-results-management/). I would like to add the following user as a PTE for respective locales:

If you have any questions, just comment here. Thank you!


Local WordPress.org sites content – let’s gather the data

For a while now we’ve been talking about something we call Rosetta outreach. As most of you know the WordPress Rosetta sites are the local sites for WordPress, associated with a specific locale. Example: es.wordpress.org (Spain), ro.wordpress.org (Romania), bg.wordpress.org (Bulgairia), etc. A full list of the WordPress Rosetta sites can be found on our Teams page.

Historically the people who took care of translations also took care of updating the content of the Rosetta site. But as translation work grows and local communities grow, the roles on a local team are now separated and we can have translation teams (who take care of localizing WordPress) and editorial teams (who publish important WordPress news on the local WordPress.org sites in their native language).

Since having an editorial team is new, but having local teams who organise meetups and WordCamps outside the localization efforts is not that new, the Rosetta outreach project aims to create a bridge between the translation community and the local community teams in order to provide more value to WordPress users all over the world in their own language.

Objective: provide more valuable localized content on local WordPress.org sites

To achieve that we’re focusing the initial efforts on three main things and we need the help of the existing teams for both:

  1. Gather data about the current status of local Rosetta sites
  2. Reach out to event organising local teams to invite them to join the local editorial teams.
  3. Figure out a way to attract people from outside both the polyglots and community teams to become local .org editors

What content should a complete Rosetta site have?

Each team can decide what content their local site should have, but after several discussions during weekly meetings this is what the team recommends:

  • Translated announcements for each WordPress release (the content of https://wordpress.org/news, but localised)
  • Updated showcase with fresh samples of good WordPress work in your language (be careful about the guidelines here, doing a call for showcase examples on a broader community level is your best approach here)
  • Event announcements – local meetup announcements, local WordCamp announcements, calls for speakers, sponsors, volunteers and what not for local events
  • Anything that you feel needs a local community discussion or is an important local topic related to WordPress

What do you can do to help?

  • If you are a Locale manager or a part of a local team, please fill out the data about your local Rosetta site in the “Data” tab of this spreadsheet
  • If the content of your local site is not regularly updated, you can reach out to event organisers in your country and talk to them about being editors in your local Rosetta site and publish content like:
    • WordCamp announcements
    • Meetup announcements
    • Create an events/meetups page
  • If you don’t translate and publish WordPress release announcements regularly, you can think about creating a page on the website that tells people how they can get involved with contributing content in your local language.
  • Volunteer for a regional outreach – you can help us reach out to local teams whose sites are a bit stuck and find contributors who would be willing to help update the content on their Rosetta sites.

Sound interesting? Leave your thoughts in the comments and let’s do this.



#local-sites, #local-sites-content, #rosetta

WordPress Community summit 2017 – representation and Polyglots topics

For those of you unfamiliar with the concept, the community summit is a global gathering of contributors from all make.wordpress.org teams from all over the world for a few days of discussions and coworking on topics that are closely related to the future of WordPress.

This year’s community summit will be in Paris on June 13-14, before WordCamp Europe contributor day (June 15) and WordCamp Europe 2017 (June 16-17). The previous community summits were in the US – Philadelphia in 2015 and San Francisco in 2014. The first ever community summit was in 2012 in Tybee, GA.

Polyglots representatives and topics for the 2017 community summit

A couple of weeks ago the Community team posted about the 2017 community summit and requested all teams to step up with a couple of things:

  1. A list of topics/issues which are relevant for the progress of the team and the WordPress open source project as a whole, prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion.
  2. A list of representatives to attend the Community Summit (not limit-determined, but please keep in mind that our venue capacity limit is of 190 attendees), with selections based on several factors, including: representation of a wide, diverse range of opinions (based on the agreed-upon topics selected by each team), diversity, inclusion, and activity of the contributors.
  3. One or two contributors who are willing to help with the organization of the event: posts, communication, travel assistance, finding sponsors, etc. The intention of this approach is to propose a more open and team-focused Community Summit with transparent participation from all active contributors and reps of each team. This way we can hopefully anticipate barriers and cross-team difficulties that might come up, and avoid them.


Every Locale manager/General Translation Editor who is interested in going to the community summit can step up and volunteer/nominate themselves. Don’t be shy to step up to represent the team – it doesn’t matter how involved you have been with meetings or discussions so far. If you have opinions and are willing to help with some of the topics listed below, you would be a great asset during the community summit.


After discussing things during weekly chats for a couple of weeks, this is the official post where you can nominate yourself or a fellow contributor to represent the team during the community summit and you can comment on the topics that we have singled out for the two day event:

Topics related to the Polyglots team working with the community team

  • Increase outreach (Rosetta sites outreach, jump starting and upgrading our locale sites to best fit the community)
  • Organise local contributor days

Topics related to the team working with the meta team

  • Improvement of translation and communication tools 2.0 (we’ve already got the first phase of this going with the O2s, GlotPress improvements, etc).
  • Cross locale PTEs implementation discussions and
    brainstorming ways of getting rid of the current bottleneck of improving plugin/theme translations

Polyglots Processes

  • New General Translation Editors onboarding/ Mentorship program
  • New translation contributors onboarding
  • Handbook review / updates

Polyglots Leadership team growth plan

  • We need more people representing different regions to get involved
  • A plan to attract and keep them
  • Grow the communication side of the polyglots leadership team
  • Grow the technical side of the leadership team

Volunteers to help organise the community summit

If you would like to help the organising team of the community summit, please put your name forward. Tasks expected from volunteers would include posts, communication, travel assistance, finding sponsors, etc. but at this point, we don’t know many details.

Please get involved with this as this is a chance for our team to single out the important issues we currently have and to brainstorm and find solutions for them. We need as many people as possible to give an opinion on topics and even if you can’t make it to the event, your position is valuable and will be taken into consideration.

Thank you!


#community-summit, #community-summit-2017

Hi Polyglots, I’m the author of WallStreet Theme


and would like to make the following users editors of their languages: