Agenda weekly Polyglots chat Aug 9, 2017

Agenda Polyglots chats Aug 9, 2017

Here’s an agenda for the chats this week.

  • Weekly locale stats
  • There have been small changes to several of the core/meta projects lately. A convenient way to check if you need to catch up on a few strings for WordPress core, Browse Happy, Plugin and Theme directory, etc. is to visit https://translate.wordpress.org/stats
  • Remember to 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
    Also remember to enable notifications for mentions of your locale on https://profiles.wordpress.org/YOUR-ORG-USERNAME/profile/notifications/
  • Global WordPress Translation Day 3
  • Open discussion

Chat times:

Global WordPress Translation Day – Chat times:

See you there!

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

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

Agenda weekly Polyglots chat Aug 2nd 2017

Hello polyglots,

Here’s an agenda for the chat today.

  • Weekly locale stats
  • Please respond to your editor requests: there are 36 open editor requests. You can find them here (replace YOUR_LOCALE): https://make.wordpress.org/polyglots/tag/YOUR_LOCALE/?resolved=unresolved
  • String freeze for WordPress 4.8.1. The release should have happened yesterday, but was postponed by one day. Many locales are already at 100% on the dev project, but quite a few still need to catch up. There are only some 10 strings new, so if you released 4.8, then this is a relatively quick task. Make sure that your locale is at 100%!
  • Global WordPress Translation Day 3: Call for speakers is open! Time to start planing your local translation event! Welcome to take part in the preparation work and planning. The next meeting for organizers will take place between the first and the second Polyglots weekly meeting Wednesday, August 2, 2017, 11:00 AM GMT+2 on #polyglots-events
  • Open discussion

Chat times:

Global WordPress Translation Day – Chat times:

See you there!

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

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

Agenda for weekly Polyglot chats on July 26 2017

Hello polyglots,

Here’s an agenda for the chat today.

  • Weekly locale stats
  • Please respond to your editor requests: there are 34 open editor requests. You can find them here (replace YOUR_LOCALE): https://make.wordpress.org/polyglots/tag/YOUR_LOCALE/?resolved=unresolved
  • String freeze for WordPress 4.8.1. There are a few new strings in WordPress that need to be translated before launch of WordPress 4.8.1. Make sure that your locale is at 100%!
  • 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
  • Open discussion

Chat times:

Global WordPress Translation Day – Chat times:

See you there!

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

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

Agenda for the Polyglots chats on July 12th

Hello polyglots,

Here’s an agenda for the chat today.

  • Weekly locale stats
  • Global switch of the new support theme for all remaining support sites is coming soon (details). Translate these meta projects:
  • Proposal for the next release of GlotPress published
  • Please respond to your editor requests: there are 51 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 step is to decide on the event date. The first meeting for organizers will take place later today Wednesday 17:00 UTC on http://wptranslationday.slack.com/ – *NOTE, I had wrong time when I posted this. Fixed.*
  • Open discussion
  • Chat times:

    See you there!

    #weekly-meeting-agenda, #weekly-meetings

    Agenda for the Polyglots chats on June 7th

    Hello polyglots,

    Here’s a short agenda for the chat tomorrow.

    • Locale stats prior to 4.8
    • WordPress 4.8 release plan and remaining locales to be prepared – upcoming global ping
    • WordPress community summit goals for Polyglots – recap and last minute additions
    • WordCamp Europe Contributor day goals – recap and final fine tuning
    • Open discussion

    Chat times:

    See you there!

    #weekly-meeting-agenda, #weekly-meetings

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

    Dear Polyglots I have my hands full with…

    Dear Polyglots,

    I have my hands full with WordCamp Europe for the next two weeks. Dominik is busy with core and also coming to Seville next week.

    We don’t have an agenda for today’s chat, but will be in Slack from 10:00 UTC for an hour, as per usual, to answer questions if you want to bring any to the table.

    If anyone would like to host next week’s chat and collect notes, we would highly appreciate the help. Just ping us on Slack or raise your hand here.

    Cheers!
    Petya

    #weekly-meetings

    Agenda for the Polyglots chats on Jan 7 and Jan 8

    Happy 2015, dear polyglots!

    Wishing all of you a lot of inspiration, tons of energy and exciting new projects in 2015. Thank you so much for all the precious time you are dedicating to making WordPress global.

    As our first weekly meeting for 2015 is in a few hours, here are some things we could talk about today:

    • The wins of 2014 – some stats and a quick overview of what we achieved in 2014
    • Goals for 2015
      • People – let’s get more people excited about helping with translations
      • Let’s get more developers excited about making their code translatable
      • Tools – expectations, realities, dreams
    • Locale specific code will be retired in 2015 – let’s discuss which locales have it and if it’s essential as it can prevent the locale from the ability to have automatically generated language packs.
    • General discussion

    As always, suggestions for topics to discuss are welcome in the comments.

    This week’s chats are on Wed, 7th Jan, 11:00 UTC and Thu, 8th Jan, 02:00 UTC
    on the #Polyglots channel on Slack.

    Cheers!

    Petya

    #weekly-meeting-agenda, #weekly-meetings

    Dear polyglots Just a quick note We will…

    Dear polyglots,

    Just a quick note: We will skip the weekly chats this week as a lot of people are off for the holidays. If anyone still wants to chat, I will be around in the slack channel the whole afternoon (GMT).

    Enjoy your time off, happy holidays to everyone!

    Cheers,
    Petya

    #weekly-meetings

    Polyglots chats Summary Dec 3rd and Dec 4th…

    Polyglots chats Summary: Dec 3rd and Dec 4th

    ArchiveAgenda

    We’re going to try to adopt the structure of core’s chats summaries. Here goes.

    Hits:

    • Tagalog has a new translator team thanks to a call for new translator on slack worked well. @krzheiyah, @kel and @druesome joined the effort
    • 41 locales are up to date
    • We have some of the new strings in GlotPress ready to translate.

    Misses:

    • We still don’t have a 4.x Project on GlotPress
    • No string freeze yet and no information on when it or RC1 is happening (it’s obviously late)
    • 15 locales still behind on 4.0.1. (at the time of the meeting they were 16). @netweb has created a list of locales that are packaged still with 4.0

    ToDos:

    • Research how different teams approach communication of translations and create a recommended process for new teams (@petya will work with @vanillalounge and @coachbirgit and post on the P2)
    • Work with core to create the 4.x project on GlotPress (that’s on @ocean90 and @nacin)
    •  Think about a way to alert validators and translators that there are new strings to translate and help them with packaging (Thanks to @netweb for raising the question)
    • @petya will add instructions on creating and importing/exporting Glossaries to the Handbook (Thanks to @deconf for pointing out we actually can)

    Open discussion topics:

    • GlotPress improvements: suggest translation button, communication tools for validators and translators, Glossary
    • Language style guide and how to build them
    • Communication channels for translators and validators and different approaches to discussing translations
    • How we can help a locale that lacks translators/validators: we ask the current validators if they have anyone, then try everything we can
    Next Polyglots chats: Wed, 10th Dec, 11:00 UTC and Thu, 11st Dec, 02:00 UTC

    #polyglots-meeting, #weekly-meeting-notes, #weekly-meetings

    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

    Agenda for the Polyglots chats Nov 19th & 20th

    Agenda for the Polyglots chats Nov 19th & 20th

    Hello dear polyglots,

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

    1. Update on existing l10n
      • 53 locales up to date
      • 6 locales down by one major version
      • 15 locales down by two major version or more
    2. How can we get more localizations active?
      • Contacting validators from the locales down-by-one (mk, nn, es-mx, tl, ta-lk, vi) and offering support
      • Maybe contact other validators and see if they’re in progress or inactive
      • If a locale is inactive, we need to find new validators
      • @Petya will contact the following locales: de-ch, ka, bel, lv, af
      • Who else wants to help contact locales?
    3. WordPress 4.1
      • Coming soon. About three weeks away.
      • String freeze is at RC, but when is RC? Schedule in flux.
      • Let’s get this on the agenda of the core team. @johnbillion @nacin
    4. Technical Chat
      • We need to schedule a “technical” chat to go over the technical responsibilities of the polyglots team.
      • Role includes things like Rosetta, deploy requests, and dealing with make/polyglots requests.
      • Let’s try for Monday or Tuesday. Who’s interested and when can you attend?
    5. GlotPress redesign status
      • Do we know what the current status of the UI changes for GlotPress is? Would be great if @teamadesign could join one of the chats and let us know.
    6. Open Discussion

    If you have any suggestions for the agenda, please add them in the comments below.

    Cheers!

    Petya

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

    Weekly Polyglots Meeting Schedule Hey dear Polyglots Let’s set…

    Weekly Polyglots Meeting Schedule

    Hey dear Polyglots,

    Let’s set up the time for our weekly meeting(s). We’ll use these meeting to help new validators / translators with questions, get stats from localizers, get updates on how teams are performing, learn about any trouble they may have and help get their locales to 100%.

    Please fill out this Doodle and choose the hours that suit you

    (Make sure you’ve selected the right time zone in your Doodle profile)

    Continue reading

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