WordPress.org

Translate WordPress

Updates from February, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 8:50 pm on February 24, 2015 Permalink |
    nacin
    Tags:   

    Thought it might be fitting to post this as today marks five years since @ocean90‘s first patch to WordPress. As has been obvious to some of you, I have stepped back from i18n in the past few months, especially after 4.1’s release and as WordCamp Europe, WordCamp SF, the community summit, and Slack have empowered so many of you. I am stretched across a lot of projects, and Dominik very willingly stepped up to take on a lot of responsibility for improving Rosetta, core language packs, and related projects. He’s a highly respected WP core developer, he’s previously helped me on a number of i18n projects, and he’s slid into this role with ease. It’s also time for the technical point of contact to be a polyglot again. :-)

    @stephdau has also been instrumental for the massive project to translate plugins and themes (including language packs, localized plugin/theme directories, and the like). Also, you may have noticed a lot of coordination across these initiatives now happens in a #meta-i18n channel on Slack.

    While I haven’t gone anywhere and I’m still helping a bit behind the scenes, please consider @ocean90 the new @nacin and the primary point of contact core/dotorg i18n and the like!

     
  • Kazama 6:27 am on January 29, 2015 Permalink |
    kazama • th.wordpress.org editor  

    It seem to me that the complete status of this page are wrong.
    https://translate.wordpress.org/projects/wp/dev/admin
    Anyone can confirm or just me to see this error. It shows 100% completed in some languages but when you look inside there are many strings (10 page at least) that aren’t translated.

     
  • pavelevap 1:10 pm on January 16, 2015 Permalink |
    pavelevap • cs.wordpress.org editor  

    This string is not available in GlotPress: https://core.trac.wordpress.org/browser/tags/4.1/src/wp-admin/includes/schema.php#L361

    It should be in Administration project, but it is missing.

    All localized versions are missing this string and that is why there is default zero offset.

    Maybe @nacin should look at it?

     
  • Andrew Nacin 12:25 pm on December 18, 2014 Permalink |
    nacin
    Tags: , ,   

    WordPress 4.1 instruction manual

    Hello polyglots! In the next 3 hours or so, @johnbillion will be starting the release process (in #core in Slack). Please make sure you are 100% translated for WordPress 4.1 and all subprojects, and also do not forget about the Akismet project.

    I’d expect a release somewhere around¬†1600 UTC, but for most locales, the release process¬†is now automated. Please read on.

    Part 1, Language Packs

    If you are 100% translated at the time of 4.1’s release, a¬†language pack will be generated for you. This is a ZIP file consisting of PO and MO files only, and is used for the¬†language chooser¬†during the install process, and for the¬†language switcher on the settings screen.

    If you become 100% translated¬†some time after 4.1’s release, a¬†language pack will be generated for you once the script is run. This will be around every hour.

    If you are 100% translated, a language pack has been created, and then you modify a translation to fix a typo or whatever, a language pack will be regenerated for you once the script is run. Please do not do this with unnecessary frequency, as it triggers an update across all WordPress sites.

    Part 2, Release Packages ‚ÄĒ IMPORTANT CHANGES AHEAD

    A¬†release package¬†is what you’re used to building using the form on Rosetta’s dashboard. This is a ZIP file consisting of WordPress in its entirety, along with PO and MO files for core, the PO and MO files of default themes and Akismet, and any custom changes you have.

    Do you have custom changes? For the purposes of this exercise, your locale falls under one of these four groups:

    • You have never had any custom changes¬†and i18n.svn.wordpress.org is entirely empty for your locale.
    • You have¬†no custom changes for 4.1.
    • You have¬†minor custom changes consisting of, at most, a translated readme, license file, and wp-config-sample.php.
    • You have¬†extensive custom changes consisting of other files, such as wp-content/languages/$locale.php or core modifications.

    Here are the details on each:

    • If you have¬†never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale, you do not need to do anything.¬†Your release package will be created automatically for you.¬†An example locale is en_GB.
    • If you have¬†no custom changes for 4.1, please ensure you have an empty branches/4.1/dist or tags/4.1/dist directory at¬†i18n.svn.wordpress.org. (Having an empty trunk/dist directory does not help you.) You do not need a¬†dist¬†directory if branches/4.1 or tags/4.1 is empty. An example would be nl_NL.¬†Your release package will be created automatically for you.
    • If you have¬†minor custom changes¬†consisting of, at most, a translated readme, license file, and wp-config-sample.php, please ensure these files exist in a¬†branches/4.1/dist or¬†tags/4.1/dist directory at i18n.svn.wordpress.org. (Having your stuff in only trunk/dist does not count.) An example would be eo¬†or fr_FR.¬†Your release package will be created automatically for you.
    • If you have¬†extensive custom changes consisting of other files, such as¬†wp-content/languages/$locale.php or core modifications, you will need to create a package via Rosetta as you have done in the past. For this,¬†We are phasing out the ability to ship¬†any customizations beyond license, readme, and¬†wp-sample-config.php. This means you need to reach out to the WordPress core contributors to fold your modifications into WordPress core. You can start this process¬†by creating a Trac ticket.

    To summarize:

    • 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 for WordPress 4.1 if you follow the instructions above.¬†Both language packs and release packages will automatically be created once¬†4.1 is announced. 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. This option is being phased out in 2015.

     

    If you go to the releases screen on your Rosetta dashboard, you’ll see a new notice that explains what the system thinks your status is.¬†If you have any questions, comments, concerns, or issues, please comment here or find me or @ocean90 in #polyglots on Slack.

    If your locale is currently eligible for automatic creation of¬†release packages (which includes being at 100%), you’ll find an RC3 build¬†generated from¬†tags/4.1-RC3 waiting for you on¬†your dashboard. Please inspect these ZIPs. Those locales are:¬†az, bs_BA, de_DE, en_CA, en_GB, eo, fi, fr_FR, it_IT, nb_NO, nl_NL, pt_PT, ro_RO, and sv_SE¬†(zip links).

     
  • Petya Raykovska 12:15 pm on December 18, 2014 Permalink |
    petya • bg.wordpress.org editor
    Tags: , WordPress 4.1   

    Dear polyglots,

    WordPress 4.1 will be released in a few hours.

    I wanted to give you the current status on updated locales and ask some of you for some last efforts so we can have more locales at 100% before the release. Currently we have 66 locales that are above 90% for WordPress, 56 above 90% for Admin and 54 above 90% for the Network Admin.

    The projects and subprojects mentioned below are required for a release in order for a locale to get a language pack and automatically get in the language chooser.

    WordPress is at 100% for 33 locales

    Slovak, Welsh, Albanian, Danish and Rohingya are at 99%

    Icelandic, Lithuanian and Serbian are at 98%

     

    WordPress Administration is at 100% for 33 locales

    Slovak, Welsh, Albanian and Serbian are at 98%

    Burmese, Persian, Danish and Chinese (Taiwan) are at 97%

     

    Network Administration is at 100% for 52 locales

    as there haven’t been any new strings there for this release,

     

    Twenty Fifteen is at 100% for 31 locales

    Slovak, Czech, Korean, Welsh, Albanian and Serbian have between 1 and 3 strings to get to 100%

     

    Akismet is at 100% for 35 locales

    Spanish (Peru), French (France), Scottish Gaelic, Albanian, Spanish (Chile), Chinese (China), Chinese (Taiwan), Slovak and Spanish (Spain) all have just one remaining string.
    It would be great if the validators for the locales mentioned above could step up and translate those last couple of strings that are remaining.

     

    I’m pinging the most active of you,¬†based on the w.org activity.

    Thank you in advance for your work. @nacin will post extended instructions for the 4.1 release for all of us today.

    Cheers!

    Petya

     
  • Peter Holme Obrestad 11:52 am on December 17, 2014 Permalink |
    peterhol • no.wordpress.org editor • nn.wordpress.org editor • nb.wordpress.org editor
    Tags:   

    I have given out our language url (https://translate.wordpress.org/languages/nb) to potential translators. I recently discovered that the “Administration” partial of the WordPress translation isn’t visible there. This led to me not getting any help with that one this time‚Ķ What’s up with that? ūüėČ

     
  • Krzysztof Trynkiewicz (Sukces Strony) 8:54 pm on December 15, 2014 Permalink |
    eclare • pl.wordpress.org validator  

    @nacin We still have a few strings that aren’t translatable.

    https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L94
    https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L99
    https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L103
    https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L124

    What about them for 4.1?

     
  • Petya Raykovska 2:51 pm on December 8, 2014 Permalink |
    petya • bg.wordpress.org editor
    Tags: , ,   

    Polyglots chats Summary Dec 3rd and Dec 4th… 

    Polyglots chats Summary: Dec 3rd and Dec 4th

    Archive | Agenda

    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
     
    • Emre Erkan 3:15 pm on December 8, 2014 Permalink | Log in to Reply

      FYI tr_TR is no longer at 4.0, it’s at 4.0.1 :)

    • Stephen Edgar 11:39 pm on December 9, 2014 Permalink | Log in to Reply

      We have 43 locales now up to date with 4.0.1 :)

      How are we looking for 4.1? Without clicking through each project and sub project (/admin, /network, /akismet et cetera) it’s difficult to get an overview… It would be great if we could extend some type of summary at https://translate.wordpress.org/languages.

      Kind of related and raised in #gotpress on Slack was this from @joostdevalk:

      https://wordpress.slack.com/archives/glotpress/p1417790668000540
      “…overall stats per locale to GlotPress”

      My thinking here is rather than “overall stats per locale” we add a summary of percentage completed for the current release and the next release. For 4.1.x this would include stats from /dev, /admin, /network, /akismet, /twentythirteen, /twentyfourteen, /twentyfifteen yet for 4.0.x the stats would not include /twentyfifteen as that wasn’t an included project for the 4.0.x release if y’all get my drift.

      • Petya 9:20 am on December 10, 2014 Permalink | Log in to Reply

        I use http://wpcentral.io/internationalization/, Marko recently added percentage for core, makes it easy.

        For the rest, if need be, I do by scanning locales one by one. Can’t really afford doing proper stats for everything now, would mean way too much time.

        It would be great to have that here https://translate.wordpress.org/languages along with all the other info that’s currently at wpcentral.io and the percentage for each project that’s required for a locale to get as an option in the initial WP install.

  • Petya Raykovska 7:17 pm on November 18, 2014 Permalink |
    petya • bg.wordpress.org editor
    Tags: , ,   

    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

     
    • Marko Heijnen 7:24 pm on November 18, 2014 Permalink | Log in to Reply

      To have less chaos I rather would like to no discuss GlotPress during the Polyglots chat. Specially if that would involve a complete redesign.

      • Petya 7:30 pm on November 18, 2014 Permalink | Log in to Reply

        How is reporting on progress causing chaos? :)

        • Marko Heijnen 7:31 pm on November 18, 2014 Permalink | Log in to Reply

          Because that reporting should be done on http://blog.glotpress.org and not here.

          • Catiakitahara 1:56 am on November 19, 2014 Permalink | Log in to Reply

            Hey @markoheijnen (what’s your handle?), I was the one who suggested it to @petya. I agree with you GlotPress should be discussed at its own blog, however I don’t agree we can’t have a brief report in our channel. I think it’s reasonable to share this information with us, mainly because it’s not anywhere yet. We don’t need to go into details and as you’ll be there, I guess, you can interfere and politely ask us to change rooms if you think we’re starting to promote chaos. In other words it doesn’t hurt anyone to come to our meeting, make a brief report and use that chance to invite people who are interested to discuss the matter at the appropriate channel. ūüėČ

            • Marko Heijnen 9:00 am on November 19, 2014 Permalink

              It’s in the end my call to make and I would like that if I make a decision to GlotPress that people would respect that. If there wasn’t anything discussed on GlotPress then there is nothing to report on Polyglots.

              It would be weird if teamadesign also needs to show up if someone else with a GlotPress installation would want to know the current redesign status like if another CMS would use it.

    • Daisuke Takahashi 11:26 pm on November 18, 2014 Permalink | Log in to Reply

      I’d like to hear the current status of Plugin&Theme Directory internationalisation and team P2.
      (e.g. https://de.wordpress.org/team/, https://ja.wordpress.org/plugins/)
      And translation schedule of them.

    • Sergey Biryukov 5:07 am on November 19, 2014 Permalink | Log in to Reply

      I’m interested in the ‚Äútechnical‚ÄĚ chat. Monday or Tuesday works for me, any time from 10:00 to 22:00 (UTC).

  • Sithu Thwin 11:00 am on November 18, 2014 Permalink |
    herzcthu • mya.wordpress.org editor
    Tags: , ,   

    I’ve opened a ticket #29664 two month ago. No one response. Today I’ve attached a patch file to support Myanmar script font-family.
    I’m looking for a way to embed google web font for Myanmar.
    I want to know if it is possible to embed in WP core or do I need to release Locale specific Package with embedded fonts.
    Is there a way to add Word Break rules js file in WP core?

     
  • Stefano Aglietti 8:38 am on November 15, 2014 Permalink |
    SteveAgl • it.wordpress.org editor
    Tags: , twentififteen   

    WordPress 4.1 is on Beta stage would be nice to have finally the 4.X branch and having the ne twentyfeifteen theme too, even if there will be changes in strings we could start to translate and not having to rush in the last 2 days before release.

     
  • Stephen Edgar 10:30 pm on November 5, 2014 Permalink |
    netweb • en-au.wordpress.org editor  

    iOS 4.5 translations has funky negative counts for ~12 locales untranslated strings

    https://translate.wordpress.org/projects/ios/45

    Ping @nacin, can you do that DB thing you love to do ūüėČ

     
  • Justina 5:39 am on November 4, 2014 Permalink |
    pokeraitis • lt.wordpress.org editor
    Tags:   

    How to add more projects to locale? For Lithuanian, we have it like this: https://translate.wordpress.org/languages/lt and we would like to have all projects from here available for translation: https://translate.wordpress.org/projects

     
  • Petya Raykovska 7:05 pm on November 3, 2014 Permalink |
    petya • bg.wordpress.org editor  

    Polyglots leads discussion and selection – WP Community Summit 

    Polyglots leads discussion

    Leading the polyglots team isn’t an easy task. Lots of cultures, a lot of diversity. Understanding everyone can be hard. There have been issues in the past with specific communities using their sites to make money, some using it for WordPress, some not. Part of this is cultural, part of it is ignorance, part is just bad performance. Varies from culture and site.

    In light of that, we created a set of expectations for Rosetta sites. Part of leading polyglots is making sure sites meet these expectations.

    Process for handling bad content on Rosetta sites

    • Email the validators of the site (request a response within a week)
    • After a week, email again (“You have 3 days to take care of this”)
    • After three days, email again¬†(“You have 24 hours to clear this or we remove it”)
    • If the content is not removed within 24 hours, login as administrator and remove bad content.
    • Email validators and say if the content comes back without fixing its problems, they will be removed as validators/editors.
    • Check site regularly to ensure the content doesn’t come back.
    • When at all possible, we want validators to be responsive. If they aren’t, that can be an issue.
    • Note that just because a validator is unresponsive, that doesn’t mean they are bad actors. It’s possible for life to get in the way for days, weeks, or months.

    Finding new validators

    • We are going to need more validators as plugins and themes become translatable. A good target is likely 20 active validators per language by mid-2015.
    • That‚Äôs a problem across the community and we need good coordinators for different regions to mentor new validators.
    • We also need to add new languages, which will need good validators. Mentoring them will be important so they can grow fast.

    Things that will help with new translators/validators:

    • Having better documentation
      • Translator handbook
      • Per language guidelines for translation
      • Glossary for every language
    • Better contributor recognition
    • Roles: separate roles for translations vs the local community stuff (Rosetta administration, support, blog, forum moderation)
    • Separate the role of the editor from the validator so validators can focus on translation and mentoring new validators

    Leads

    As Polyglots will get more and more busy following themes and plugins in the repository, there will be a need for more coordination and help to all the new validators. This can be accomplished by splitting locales into different regions and appointing multiple leads for each region. Separating the locales will be done geographically first and then by language so that there is no overload for any of the leads.

    Proposed regions:

    Region 1: Asia & Oceania: Central Asia, South Asia, East Asia, and Oceania. Perhaps does *not* include Australia / New Zealand English, but does include any future local languages. Does not include Russia or Iran. Currently, ~51 locales.

    Region 2: Europe (including Turkey, Russia), Africa (entire continent), Middle East (includes Iran). Currently, ~70 locales.

    Region 3: North, Central, South America, and the Caribbean. Perhaps includes Australia / New Zealand English. Also includes engineered languages (Esperanto, Klingon, Ido). Currently, ~16 locales.

    Part of the goal for these regions is to have them within a reasonable timezone of each other to make coordination easier. Part of the goal is to have “similar” languages together (like the English languages).

    What is a lead?

    A lead is not simply a copy of Z√©. We’ll all get burnt out if we try and emulate everything he did. There’s a lot of responsibilities. Let’s split the role into two.

    As the role is pretty extensive, it is best for it to be split into two separate lead roles:

    “Community” leads

    Essentially, this role is non-technical and involves working with people. Here’s a list of a lot of responsibilities included in¬†this role. (There may be more!)

    • Review and answer “people”-based P2 comments and requests
    • Answer requests for new locals (research and approve, especially using Ethnologue)
    • Weekly meetings (organize, take notes, post updates on how locales are doing)
    • Moderate¬†disputes between validators/translators
    • Mentorships ‚Äď Connect validators with other validators who can help and give pointers.
    • Validators ‚Ästfind and approve validators; communicate¬†with current validators
    • Interface with the community team
    • Interface with legal (as a result of Rosetta contacts)
    • Review Rosetta sites to ensure they meet expectations
    • Contact validators if a Rosetta site does not meet expectations and work to get them fixed.
    • Write and maintain documentation
    • Create and maintain policies (like the Rosetta expectations; new things may be needed in the future)
    • Compile and post stats (on the P2)
    • Generally, find people to do things

    “Technical” leads

    Technical leads are responsible for doing everything needed technically. Here’s a list of things that they may need to do:

    • Answer technical questions on the P2 (deployment, other related things)
    • Deploy Rosetta, including forums and P2s when those exist again.
    • Create locales (after community lead approves)
    • GlotPress ‚Ästinterface with the GlotPress team, including discussing future needs and helping implement those needs where applicable.
    • Interface with the core team about upcoming core changes
    • Interface with the meta team about necessary wordpress.org changes.
    • Work on technical problems that local translations have
    • Create and compile stats (with community leads)
    • Write and maintain technical documentation

    How do we find/appoint leads?

    Everyone here (at the community summit) should be considered a “lead” in the WordPress community. Maybe we shouldn’t have one or two leads, but instead form¬†a leadership team with everyone here who’s interested. The leadership team can work together to ensure no one gets burnt out and that no knowledge gets lost along the way. Today, a leadership team is formed.

    Moving forward, we should look at who wants to be community-focused and who wants to be technically-focused. We have good coverage for community-focused, but we’ll need to bring in people to be technically-focused. We also have great timezone coverage!

    Over time, we should consider having regional leads for each of the three regions described above, both for community and technical sides. (This means a total of six “leads.”)

    Weekly Polyglot meetings

    First things first, we need to start a weekly meeting.

    • Ideally two or three meetings a week, 8-12 hours apart. Same agenda, but this allows people from different timezones to participate.
    • Let’s make a Doodle for choosing the time for weekly meetings.
    • Use this meeting to help new validators / translators with questions.
    • Also get stats from localizers. How are teams doing? What progress are they making? Is a team almost there? How do we get them to 100%?
    • Meetings should be held in¬†#polyglots channel on Slack.
    • Notes from the first meeting of the day can be posted to the P2 in draft form. Other note-takers can update after their meeting. Last meeting of the day publishes post.

    Contributor Recognition

    To start, we need to improve the badges on dot org profiles. How about three polyglots badges?

    • A badge for members of the polyglots leadership team
    • Badge for validators/editors. Potentially use this for moderators too, though can’t they get a support badge?
    • Translators (anyone who’s translated a string and had it approved) get a third badge.

    Final notes / actions

    • Update Handbook
      • Add handbook page with leadership team (including dot org usernames) so people can reach out and get advice.
      • Include timezone information so you can find a local lead.
      • Add a map (image map!) that shows what the regions are and who can help you in your region.
      • Add a list of regions (non-graphic) as well.
    • Talk to support team (Mika) about getting badges for moderators
    • Start holding weekly meetings
    • Find technical leads in each region
    • Document Z√© (and all that he did)

    Participants

    The following people attended this meeting at the WordPress Community Summit: Andrew dela Serna (Philippines), Birgit Olzem (Germany), Catia Kitahara (Brazil), Marko Heijnen (The Netherlands), Mayuko Moriyama (Japan), Petya Raykovska (Bulgaria), Shinichi Nishikawa (Japan), Sam Sidler (USA, wordpress.org), Takayuki Miyauchi (Japan), Xavier Borderier (France).

     
    • Birgit Olzem 8:08 pm on November 3, 2014 Permalink | Log in to Reply

      +1 thank you very much for the detailed recap and notes :)

    • Stephen Edgar 11:08 pm on November 3, 2014 Permalink | Log in to Reply

      Agreed, +1 on this detailed report, thank you :)

    • Lorna Timbah 12:29 am on November 4, 2014 Permalink | Log in to Reply

      Great recap. The handbook issue needs to be tackled pronto.

    • Japh 10:20 am on November 4, 2014 Permalink | Log in to Reply

      Thanks so much for the summary post, @petya. I didn’t get to participate in this discussion at the Summit, unfortunately. So many discussions going on!

      My thinking regarding Australia and New Zealand is that they should be included in the same region as Asia & Oceania. Geography and timezones match up better, and there should be more community cross-over between these countries. Especially as people move between them more freely (many students in Australia from South-East Asian countries). I’ll be doing whatever I can to encourage this too! Your thoughts, @shinichin, @thewebprincess, @mayukojpn?

      I’d also like to put my hand up to help with the technical needs of the polyglots team! I’ve contributed to GlotPress previously, and was involved in some of those discussions in San Francisco this past week. Would love to help wherever I can.

      Thanks again!

      • Mayo Moriyama 9:31 pm on November 4, 2014 Permalink | Log in to Reply

        Yeah, between Australia and South East Asia is easy to go and come. In Cambodia I met a lot of Ausie people.
        By the way, thank you Petya!

      • ShinichiN 4:06 am on November 5, 2014 Permalink | Log in to Reply

        Hi @Japh

        Thank you for mentioning us.

        I don’t know exactly what background the suggestion “English speaking countries going to belong to Region 3″ have. I want to hear more about the thought behind the suggestion. I should have asked at the meeting more.

        It’s very nice to have a mature community such as Australia and New Zealand in Region 1. Right now, it’s not much countries which I (for example) can talk to face-to-face way, while Region 2 and 3 have many who already share the concept. It’s nice that I can hear from you(for example) in the coming real time chats.

        Also, excited to hear that the 2 countries can perform community cross-over roles. I know that many Japanese people also go to Australia and New Zealand.

        In other hand, will there be any issues which English language areas need to talk to each other in long term? I remember that United Kingdoms was also listed in Region 3. So, I want to find out more what this leading the team process will be like.

      • Petya Raykovska 11:42 am on November 5, 2014 Permalink | Log in to Reply

        I see no problem for Australia and New Zealand being in the Asia & Oceania region especially if you all feel it’s a better fit.

        I feel we need to stress a point here though. Separating the regions is an idea with a single purpose to help as much people as possible to participate in the Polyglots discussions.

        This doesn’t mean in any way that conversations will stay within the regions. They shouldn’t :-)
        One of the things we discussed in details during the community summit was tightening bonds between communities so they can get mutual help from all over the world – validators mentoring other validators from different communities no matter the language.

        I hope @samuelsidler can shed some more light on his original idea when he gets back.

        I realise separation is tricky and we need to make sure we keep talking to each other no matter the region we’re in.

        • Samuel Sidler 7:32 pm on November 9, 2014 Permalink | Log in to Reply

          Sure! In general, we’re not talking about *community* issues, but about *language* issues. In the case of language issues, it makes sense to have the English locales grouped together.

          However, I’m not sold on either way and whatever happens to work out best is perfectly fine. I was just proposing the way that seemed to make logical sense from a language stand-point. Whatever works best in practice is what we should do. :)

    • WacŇāaw Jacek 11:29 am on November 4, 2014 Permalink | Log in to Reply

      I’m not sure if anyone else is as interested in this feature as I am, and I know this has to be implemented in GlotPress and not on the Rosetta sites, but per-project validator permissions?

      • Marko Heijnen 9:37 am on November 5, 2014 Permalink | Log in to Reply

        This is how GlotPress normally works ūüėČ so it’s a Rosetta thing. The thing I do want to do is assigning project owners.

      • Petya Raykovska 11:47 am on November 5, 2014 Permalink | Log in to Reply

        I think we will definitely need to do something like that when plugins and themes enter.

        @nacin was talking about a new role for a Rosetta site – a super validator that gives permissions to validators for different projects in GlotPress.

        I can also imagine plugin and theme authors will want to “own” (as Marko mentioned) their projects on GlotPress and to be able to give new validator rights.

        So it will require changes in the way validators are being handled now. I don’t think there’s a decision yet on how exactly to do this. But it will have to come soon if we’re going to have the first 25 plugins and themes in GlotPress by the end of the year (as Matt said in his State of the Word in SF).

    • Adrian Pop 1:59 pm on November 14, 2014 Permalink | Log in to Reply

      Hi Petya,

      a short notice: The new Romanian team just released the complete WP 4.0 in Romanian.
      Happy to contribute!

      • Alex, Alin and Adi :)
  • Daisuke Takahashi 11:22 am on October 30, 2014 Permalink |
    extendwings
    Tags: ja_JP,   

    Some images returns 404 in https://ja.wordpress.org/.
    I guess this may be related to “Rosetta and .org installs are now merged.”(https://make.wordpress.org/polyglots/2014/10/15/notes-from-the-polyglots-chat-on-oct-15/)

    ping: @nacin

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel