Petya Raykovska 10:38 am on December 11, 2014
Tags: , , ,   

Notes – Polyglots chats on Dec 10 & 11

 Notes – Polyglots chats on Dec 10 & 11

Archive: Wednesday chat | Thursday chat

New information on WordPress 4.1 RC1, string freeze and release dates

  • RC1 is coming on Dec 11th – (there will be a post on make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., we will post a channel announcement in slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. too)
  • Final date for WordPress 4.1 release – Tuesday, Dec 16th
  • Keep an eye on Translate.WordPress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. in the next three days, the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for the About page should get in at some point
  • Stats: LocalesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ up to date, locales behind and their progress, localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ requests, new locales:
    • http://wpcentral.io/internationalization/ – let’s aim for at least 43/50 locales to be ready for the 4.1 release, it would be amazing if experienced polyglots kept an eye on the P2 for requests and help build, test and release packages
    • An idea from @nao: maybe we should do a translation sprint for next cycle or something and get translators to get on #polyglots (or even a separate channel exclusively for translation questions)

Hide Windows Phone App from GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.

  • (thanks to @garyj for bringing it up)
  • @garyj‘s original thought: Propose to drop (hide rather than delete) the WordPress for Windows Phone item off of the https://translate.wordpress.org/languages/en-gb and similar pages. The project is no longer listed on https://wordpress.org/mobile/, hasn’t been updated in the Windows app store (http://www.windowsphone.com/en-us/store/app/wordpress/5f64ad85-f801-e011-9264-00237de2db9e) since June 2013, and the official blog at wpwindowsphone.wordpress.com is closed. We shouldn’t be encouraging folks to spend time translating an abandoned project that is never going to incorporate their efforts into a new release.
  • let’s confirm status on the App with the mobile team and then decide if we want to hide or at least unmark the project as active and add a note in the description that the app is no longer being developed
  • We need guidelines for projects that get into GlotPress

Community hub project & Polyglots

  • @miss_jwo is leading the Community Hub project that has a lot in common with the ideas about Rosetta sites, discussed at the community summit. Let’s see who’s already involved and what the Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. can help with. See archives of the Wednesday chat discussion on the subject.
  • A lot of the things on the wish list for the Community hub overlap with ideas about improving Rosetta.
  • A lot of the things are already being done outside the .org ecosystem – on meetup.com and external community sites – let’s help the Community team figure out which features would be needed by voting for them. Is there anyone interested in joining the Community Hub discussion? They can use our knowledge of the existing local sites (RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages.)
  • It’s a must for polyglots to make use of it over/along with whatever local hub they are already using
  • They’re trying to set a meeting to discuss it. For anyone interested, here’s the Doodle. The Polyglots community leads will coordinate with the team creating the hub. Anyone else interested is more than welcome to participate.
  • @mayuko is going to check if the hub itself is going to be localized.

 

Glossary – let’s communicate it and encourage teams to use it

  • Glossary: Talked about a ticket regarding to the glossary #361 (Glossaries should be by locale instead of by project).
  • Japan and en-au sets a master and export/import to other projects when something added/changed, which is pain. It’s much easier if we have it per locale. We pass it forward to the next “Technical Polyglots Meeting”.
  • A new handbook page “GlotPress Glossary Feature” has been added by @nao
  • We can add an instruction for import/export of Glossaries there as suggested by @deconf

Open discussion

Next scheduled chats will be on Wednesday, Dec 17 and Thursday, Dec 18.

Meanwhile if you need help with incoming translations, packaging and releasing translations or GlotPress, there’re always people available for advice at the #Polyglots slack channel. Don’t be shy to ask 🙂

Cheers!

Petya & Shinichin

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