Hi Polyglots, I’m the author…

Hi Polyglots, I’m the author of Front End PM (https://wordpress.org/plugins/front-end-pm/)
I see some of locales get translated but not approved yet, Can you please review and approve following locales translations
#es_ES
#sv_SE
#fr_FR
#bs_BA
#pt_PT
#fa_IR
#da_DK

#request

PTE request for Yoast plugins

Hello Polyglots,

I am working at Yoast, the company behind the plugins listed below. We have a number of great translation editors that we’d like to be able to approve translation for our plugins. They all have been validating the translations of our free and premium plugins on https://translate.yoast.com for years, so all of them are experienced. If you need proof, please feel free to ping me on Slack (@TacoVerdo).

Plugins:

Please add the following WordPress.org users as translation editors for their respective locales, if they don’t have rights yet:

If you have any questions, ping me on Slack or comment here. Thank you!

#editor-requests

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

Hi, I am the plugin…

Hi, I am the plugin author for LiteSpeed Cache for WordPress. We have a number of 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:

Thanks!

#editor-requests

We’re in hard string freeze for 4.7 – Prepare your locales for the the release

Dear Polyglots,

The last strings for 4.7 (the about page strings) have been imported to the development project and that means no strings will change anymore before Tuesday, December 6th, the expected release date for WordPress 4.7.

That means there are two things for all GTEs to do now:

1. Translate the 4.7 project, Admin and Network admin

It’s time to head to translate.wordpress.org and finish translating the last batch of new strings.

Please don’t forget that in order to qualify for an automatic release, you need to have all strings in the following projects translated 100%:

There is also a new default theme that comes with 4.7 – Twenty Seventeen which can also use some of your time.

2. Prepare the SVN directory for your locale for automated packages

Handbook page for reference: Automated release packages

Does my locale qualify for automated release?

  • If all you have is a license, readme, and wp-config-sample.php (or no custom changes at all), everything will be automated for you if you follow the instructions above. Both language packs and release packages will automatically be created. If you are not at 100% at that time, then language packs and release packages will be created when you reach 100%. If you later modify a translation (to fix a typo, for example), your language pack and release package will be regenerated.
  • If you have extensive custom changes, you will need to manually create a package via Rosetta as you have done in the past.

On Slack, watch out for messages like this one:

translation-bot

Your locale is good to go if you see your locale in the “x release packages for y were built” message.


This is also a global ping for GTEs for locales that are currently at more than 50% and less than 100%.

4 locales are already at 100% – thank you!

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

The release is due on Tuesday, which makes this a little bit of a short notice so thank you in advance to everyone who makes time to get their locale to 100%.

Happy translating <3

Petya

#announcement

#hard-freeze, #wordpress-4-7

Please could the following user…

Please could the following user be added as a translation editor for my PDF Embedder plugin:

#fa_IR@moccc

https://translate.wordpress.org/locale/fa/default/wp-plugins/pdf-embedder

Thank you!

Dan

#editor-requests

WordPress 4.7 is in soft string freeze

Hello everyone,

WordPress 4.7 RC1 was announced on Friday and with it, all the strings in this release with the exception of the About page strings are now effectively frozen. A soft string freeze means they won’t be changed and no new ones will be added before the release in the first week of December.

Translate the 4.7 project, Admin, Network admin, Continent & cities and Twenty Seventeen

If your Development project is not translated to 100%, this is a good time to take care of that. Head to translate.wordpress.org and translate:

20 locales are already at 100%, very well done! Here’s a ping for the GTEs of locales that are at more than 50% right now.

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

Upcoming hard string freeze

According to the development schedule, hard strings freeze should come on November 29th (+1d) and the release is expected on December 6th (+1d). There will be another post here and a global ping when that happens.

Thank you all for your hard work!

#soft-string-freeze, #wordpress-4-7

Hello! A volunteer has submitted…

Hello! A volunteer has submitted some strings in #fa_IR for my plugin:

https://translate.wordpress.org/locale/fa/default/wp-plugins/pdf-embedder

Would it be possible for a GTE to check and approve these?

Thanks,

Dan

Hello Polyglots,

I’m the theme author of GeneratePress (https://wordpress.org/themes/generatepress/).

It would be great if the following users could be made editors of their languages.

Thanks!

#editor-requests

Hello Polyglots, I am the…

Hello Polyglots, I am the plugin author for https://wordpress.org/plugins/wp-wiki-tooltip/. Please add the following WordPress.org users as translation editors:

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

#editor-requests

New Team o2s

Two weeks ago we’ve rolled out 11 team o2s for testing. Today we’re pleased to announce that all 71 locales with a current release now have a team o2.

What should you use the o2 for?

A team o2 can be used for whatever your local community needs. For example, you can use it to talk about WordCamps, meetups, translations, support, documentation, meeting summaries, discussions about new ideas and the likes – in your language.

It can be a great platform for new people who would like to join your translation team. Or a great place to post about upcoming events and invite people to suggest topics. Basically, it’s an open wall for your community to discuss local issues. An official one, on your official local WordPress.org site.

How does your team get an o2?

Every Rosetta site should have one and every team can get one. If your locale is currently released for 4.6, your o2 is already created. You can check if you have one by adding “/team” to the address of your Rosetta site. If you don’t already have one, please feel free to request one in a comment below this post.

The following 60 62 sites were created:

team-site

  • #ary: https://ary.wordpress.org/team/
  • #az: https://az.wordpress.org/team/
  • #bn_BD: https://bn.wordpress.org/team/
  • #bo: https://bo.wordpress.org/team/
  • #ca: https://ca.wordpress.org/team/
  • #cs_CZ: https://cs.wordpress.org/team/
  • #cy: https://cy.wordpress.org/team/
  • #da_DK: https://da.wordpress.org/team/
  • #de_CH: https://de-ch.wordpress.org/team/
  • #el: https://el.wordpress.org/team/
  • #en_AU: https://en-au.wordpress.org/team/
  • #en_CA: https://en-ca.wordpress.org/team/
  • #en_GB: https://en-gb.wordpress.org/team/
  • #en_NZ: https://en-nz.wordpress.org/team/
  • #en_ZA: https://en-za.wordpress.org/team/
  • #eo: https://eo.wordpress.org/team/
  • #es_AR: https://es-ar.wordpress.org/team/
  • #es_CL: https://cl.wordpress.org/team/
  • #es_GT: https://es-gt.wordpress.org/team/
  • #es_MX: https://es-mx.wordpress.org/team/
  • #es_PE: https://pe.wordpress.org/team/
  • #es_VE: https://ve.wordpress.org/team/
  • #eu: https://eu.wordpress.org/team/
  • #fa_IR: https://fa.wordpress.org/team/
  • #fi: https://fi.wordpress.org/team/
  • #fr_BE: https://fr-be.wordpress.org/team/
  • #fr_CA: https://fr-ca.wordpress.org/team/
  • #gd: https://gd.wordpress.org/team/
  • #gl_ES: https://gl.wordpress.org/team/
  • #gu: https://gu.wordpress.org/team/
  • #hau: https://hau.wordpress.org/team/
  • #hi_IN: https://hi.wordpress.org/team/
  • #hr: https://hr.wordpress.org/team/
  • #hu_HU: https://hu.wordpress.org/team/
  • #hy: https://hy.wordpress.org/team/
  • #id_ID: https://id.wordpress.org/team/
  • #is_IS: https://is.wordpress.org/team/
  • #ka_GE: https://ka.wordpress.org/team/
  • #km: https://km.wordpress.org/team/
  • #ko_KR: https://ko.wordpress.org/team/
  • #lt_LT: https://lt.wordpress.org/team/
  • #lv: https://lv.wordpress.org/team/
  • #mr: https://mr.wordpress.org/team/
  • #ms_MY: https://ms.wordpress.org/team/
  • #nb_NO: https://nb.wordpress.org/team/
  • #nn_NO: https://nn.wordpress.org/team/
  • #oci: https://oci.wordpress.org/team/
  • #pl_PL: https://pl.wordpress.org/team/
  • #pt_PT: https://pt.wordpress.org/team/
  • #ro_RO: https://ro.wordpress.org/team/
  • #sk_SK: https://sk.wordpress.org/team/
  • #sl_SI: https://sl.wordpress.org/team/
  • #sq: https://sq.wordpress.org/team/
  • #sr_RS: https://sr.wordpress.org/team/
  • #sv_SE: https://sv.wordpress.org/team/
  • #szl: https://szl.wordpress.org/team/
  • #te: https://te.wordpress.org/team/
  • #th: https://th.wordpress.org/team/
  • #tr_TR: https://tr.wordpress.org/team/
  • #uk: https://uk.wordpress.org/team/
  • #vi: https://vi.wordpress.org/team/
  • #zh_TW: https://tw.wordpress.org/team/

How does o2 work?

A new handbook page “Team o2” has been added to provide some details about the new site, how to manage and use it. Read it and ask any questions that remain in the comments here.

Who has access to the new o2s?

All locale managers get an Editor level access to the new o2s which allows them to customize the site and moderate content. o2s are separate WordPress installs from your Rosetta site, but all your current Locale Managers and Editors are added as users by default. All WordPress.org users can post and comment on locale o2s.

We’re delighted to finally be able to add this feature for all teams and we hope you find it useful to get new contributors and make communication about contributing to WordPress easier in your language.

#announcement, #dev-update

We’re in hard string freeze for 4.6 – Prepare your locales for the the release

Dear Polyglots,

A little while back the WordPress 4.6 hard string freeze was announced and that means no strings will change anymore before August 16th, when WordPress 4.6 will be released.

That means there are two things for all GTEs to do now:

1. Translate the 4.6 project, Admin, Network admin and Continent & cities

The release will hit on Tuesday, August 16th. It’s time to head to translate.wordpress.org and finish translating the last batch of new strings.

Please don’t forget that in order to qualify for an automatic release, you need to have all strings in the following projects translated 100%:

2. Prepare the SVN directory for your locale for automated packages

Handbook page for reference: Automated release packages

Does my locale qualify for automated release?

  • If all you have is a license, readme, and wp-config-sample.php (or no custom changes at all), everything will be automated for you if you follow the instructions above. Both language packs and release packages will automatically be created. If you are not at 100% at that time, then language packs and release packages will be created when you reach 100%. If you are later modify a translation (to fix a typo, for example), your language pack and release package will be regenerated.
  • If you have extensive custom changes, you will need to manually create a package via Rosetta as you have done in the past.

On Slack, watch out for messages like this one:

translation-bot

Your locale is good to go if you see your locale in the “x release packages for y were built” message.


 

This is a global ping for all General Translation Editors whose locales are more than 50% and less than 100% translated:

18 locales are already at 100%, well done and thank you!

Dev between 95% and 100% (35)

Dev between 90% and 95% (15)

Dev between 50% and 90% (29)

Thank you to everyone who’s already helping bring WordPress to more than 100 languages worldwide.

We’re not allowed to be biased but this release is really special because we’ve got this guy leading it. Let’s make him proud and break a new record releasing on Tuesday, Aug 16th, with 60+ locales. I know we can do it.

Happy translating ❤️

Petya

#announcement

Hello Polyglots Could you be so kind to…

Hello Polyglots!

Could you be so kind to add the following translation editors to our plugin: https://wordpress.org/plugins/tiny-compress-images/

Thanks! 🙂

#editor-requests, #request

Hello Poly We as Persian WordPress users have…

Hello Poly,

We as Persian WordPress users have not seen any new translations after WP 4.3.1 came out.

Translation team works are almost totally dead and their website (wp-persian.com) is inactive for months and they (@gonahkar and @mani_monaj) don’t provide any response to the users in their forums.

Sometimes around 5 years ago I was contributing to fa.wordpress.org but then got removed by current moderators and opted out from being able to publish new translations of later WP releases.

I acknowledge current team members for all the things they’ve done to Persian WP. However I’m here now to request for being granted access to fa.wordpress.org dashboard and keep Persian WordPress alive.

Thanks, Mohammad

#farsi, #fa_ir, #persian, #request