Title: Notes from the Polyglots chat on Wed, Feb 18th Author: Petya Raykovska Published: February 24, 2015 Last modified: June 2, 2020 --- [ ](https://profiles.wordpress.org/petya/) [Petya Raykovska](https://profiles.wordpress.org/petya/) 1:19 pm _on_ February 24, 2015 Tags: [weekly meeting notes ( 122 )](https://make.wordpress.org/polyglots/tag/weekly-meeting-notes/), [weekly meetings ( 480 )](https://make.wordpress.org/polyglots/tag/weekly-meetings/) # Notes from the Polyglots chat on Wed, Feb 18th * WordPress 4.1.1 is coming and you should make sure your 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/](https://make.wordpress.org/polyglots/teams/) is prepared. * Check if wp/dev, wp/dev/admin and wp/dev/admin/network are at 100% * Update version in readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.– This is only for 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/](https://make.wordpress.org/polyglots/teams/) which have /dist directory on i18n.svn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) -  If you have custom changes on i18n.svn.wordpress.org and you are using branches/ 4.1 to release your package you only have to change the version in readme. html. - If you’re using tags/4.1 you have to create a new tag for 4.1.1 first. It’s just a copy of tags/4.1 and the change to readme.html. - If you have tags/4.1 and branches/4.1, but no tags/4.1.1 the build will use branches/4.1. This will affect ar, bs_BA, cy, de_DE, de_CH, en_CA, eo, es_PE, eu, fi, fr_FR, he_IL, it_IT, nb_NO, pt_BR, pt_PT, ro_RO, sv_SE, th, and tr_TR( the list is a bit old, will check it later again.) Please check your own locale and adjust it per above. * Let’s try and come up with a solution for the broken /languages/xx pages * Petya will write a post and mention the validators for locales that have a short way to go to be fully translated * Role permissions for projects – upload Dominik’s PDF * Renaming of the roles: Translation EditorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: [General Translation Editor](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?output_format=md#general-translation-editor) and [Project Translation Editor](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?output_format=md#project-translation-editor) and Translation ContributorTranslation Contributor Translation Contributors ( formerly known as Translators) are volunteers that focus on translating projects into their language. They contribute to improving their language either in a small way, like fixing a typo, or a large way, likes translating entire projects. [@ocean90](https://profiles.wordpress.org/ocean90/) has suggested a way to handle permissions for [translate.wordpress.org](https://translate.wordpress.org/) * Take a look at: [glotpress-permissions](https://make.wordpress.org/polyglots/files/2015/02/glotpress-permissions.pdf) * This gives a possible suggestion to https://meta.trac.wordpress.org/ticket/741 and https://meta.trac.wordpress.org/ticket/519 As per Ze’s suggestion we will rename “translators” and “validators” to “Translation contributors” and “Translation editors”. ### Polyglots Badges: * Suggestion is that we have two badges for Polyglots: One for Translation Editors and one for TranslationContributors. * Translation EditorTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: [General Translation Editor](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?output_format=md#general-translation-editor) and [Project Translation Editor](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?output_format=md#project-translation-editor) is everyone who has earned access to approve translation suggestions * Translation contributor is everyone who has ever suggested a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. to a locale and had that string approved by a translation editror * There is a difference of opinions about how many stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. a contributor needs to have had approved to get a badge. * Petya to create a poll so we can vote on how many approved strings a translation contributor needs to have to get the badge Next polyglots chats are on [Wednesday, Feb 25th, 11am UTC](http://arewemeetingyet.com/UTC/2014-11-12/11:00/w/Polyglots%20Wednesday%20Chat) and Thursday, [Feb 26th, 2am UTC](http://arewemeetingyet.com/UTC/2014-11-13/02:00/w/Polyglots%20Thursday%20Chat) As always, feel free to add anything that’s missing, comment or suggest things for this week’s agenda. Cheers, Petya [#weekly-meeting-notes](https://make.wordpress.org/polyglots/tag/weekly-meeting-notes/), [#weekly-meetings](https://make.wordpress.org/polyglots/tag/weekly-meetings/) ### Share this: * [ Threads ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=threads) * [ Bluesky ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=bluesky) * [ Facebook ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=facebook) * [ X ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=x) * [ Mastodon ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=mastodon) * [ WhatsApp ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=jetpack-whatsapp) * [ LinkedIn ](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fpolyglots%2F2015%2F02%2F24%2Fnotes-from-the-polyglots-chat-on-wed-feb-18th%2F%23respond&locale=en_US) * [To-do](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?output_format=md#) 1. ![](https://secure.gravatar.com/avatar/f177e770b035389ec065534539ac16c73c5e4bf2b41ece68336c7119f0b9c6f5? s=32&d=mm&r=g) 2. [Sergey Biryukov](https://profiles.wordpress.org/sergeybiryukov/) 1:36 pm _on_ February 24, 2015 3. I had some more thoughts on badges after the chat 🙂 4. If we want to mirror the WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. approach to badges, seems like it should be a single badge for validators (editors). Occasional translation contributors are already mentioned on the About page for each release, that should work as an incentive to attract new contributors. 5. The badge means a consistent long-term participation to me, and that’s what validators do. 6. Could we add a “Single badge for validators/editors” option to the poll? 7. * ![](https://secure.gravatar.com/avatar/dad360d6d33cc359ccc77beb0de91ea2ac1c3ccaf28550b1e2727d5f6127ad00? s=32&d=mm&r=g) * [Petya Raykovska](https://profiles.wordpress.org/petya/) 1:43 pm _on_ February 24, 2015 * I don’t think we want to mirror the WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. badges. I wouldn’t want to do that at all. I would much rather mirror the Community badge approach or the speakers badge approach. Once you are a speaker at a WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/)., you get a badge. * There are people on this team who have contributed translations for years without being validators. The opposite counts too. * So if we take on the “only one badge” approach, once we give someone validatorValidator See [translation editor](https://make.wordpress.org/polyglots/glossary/#translation-editor). rights, they get a badge, even though they might not have translated much and their 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/](https://make.wordpress.org/polyglots/teams/) might stay stuck for years. * If we go for the one badge approach for “long term contribution” we need to figure out a way to measure “long term contribution”. Any suggestions how to do that besides just give a badge to someone with a particular user role? - ![](https://secure.gravatar.com/avatar/f177e770b035389ec065534539ac16c73c5e4bf2b41ece68336c7119f0b9c6f5? s=32&d=mm&r=g) - [Sergey Biryukov](https://profiles.wordpress.org/sergeybiryukov/) 10:46 am _on_ February 25, 2015 - You’re right, the WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. approach wouldn’t be ideal here, and the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). speakers approach would fit better. - I wasn’t familiar with the Community badge approach, so I didn’t think of it that way. - Thanks for the clarification 🙂 ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/polyglots/2015/02/24/notes-from-the-polyglots-chat-on-wed-feb-18th/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fpolyglots%2F2015%2F02%2F24%2Fnotes-from-the-polyglots-chat-on-wed-feb-18th%2F&locale=en_US) to post a comment. # Post navigation [← Hi I’d like to request Lithuanian WordPress Forums…](https://make.wordpress.org/polyglots/2015/02/23/hi-id-like-to-request-lithuanian-wordpress-forums/) [Thought it might be fitting to post this… →](https://make.wordpress.org/polyglots/2015/02/24/thought-it-might-be-fitting-to-post-this/)