- OpenStack-I18n - lists.openstack.org

OpenStack translations in Marathi Language
by chandrakant dhutadmal 15 Nov '14

15 Nov '14

Hi All. Just heard a talk by Daisy and Chandan Kumar regarding translations of OpenStack in various languages across the globe. My name is Chandrakant Dhutadmal, working with C-DAC, Pune, India. I am ready to contribute to Marathi language translation. Kindly let me know the process to start with. Regards,Chandrakant Dhutadmal.

1 0

Stable translation import schedule (Juno and Icehouse)
by Akihiro Motoki 13 Nov '14

13 Nov '14

Hi, The dates of upcoming Stable update releases of Juno and Icehouse are fixed during the summit discussion and available at [1]. Translation import patch will be proposed three days after the freeze. (Note that the freeze date is one week before the release). According to the rule, the dates of translation import deadline will be as follows. The first upcoming date is Nov 23 (the first Juno stable update). If your language team has an update, please keep the date in your mind. This is the last call from me and I won't send another reminder mail on it. Juno 2014.2.1 Nov 23, 2014 2014.2.2 Jan 25, 2015 2014.2.3 Apr 5, 2015 Icehouse 2014.1.4 Feb 14, 2015 (we don't have a plan to import translation for 2014.1.5) As long as I remember the date, I will be able to propose a patch, but it will be appreciated if someone reminds me. [1] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Ficehou… -- Akihiro Motoki <amotoki(a)gmail.com>

2 2

Discussion on fuel-cloud module in Pune Linux User Group Meet
by Rajesh Ranjan 07 Nov '14

07 Nov '14

fyi. ---------- Forwarded message ---------- From: Manjusha Joshi <manjusha.joshi(a)gmail.com> Date: Tue, Nov 4, 2014 at 3:03 PM Subject: [PLUG] [Confirmation] Monthly PLUG meet on 8th Nov., 2014 To: Pune GNU/Linux Users Group Mailing List <plug-mail(a)plug.org.in> Hello, PLUG meeting for Month of November, 2014 will be held on 8th Nov., Saturday at 4pm in SICSR. Location: SICSR, Atur Centre, Model Colony, Pune Room No 704, 7th floor Time: 4:00 pm Agenda: 1. Discussion about Upcoming event: Please mark the calendar a) 14-15 November FUEL : Venue: Yashada, near University circle, Pune website: : http://fuelproject.org/gilt2014/index b) 22 November CenOS DOJO venue : CMS, Univ. Pune website: http://wiki.centos.org/Events/Dojo/Pune2014 2. There will be session on FUEL Cloud Rajesh & Chandan will introduce FUEL Cloud module for review. Explore it. FUEL-CLOUD is a collection of commonly used entries for localization of cloud computing related software and docs. Today, Cloud is very new to this world and is an emerging technology to the future. Lots of companies are switching their application to cloud. To understand and reach to various corner of world, it is necessary to made it available in different languages. To make the life of translators and localizer easier, it is necessary to provide a list of commonly used entries from cloud computing with its context. fuel-cloud module is prepared from different cloud technologies so that the module can be used across platform. This module will help to use a particular word precisely in cloud computing. Here is the link of FUEL-CLOUD module. https://docs.google.com/spreadsheets/d/1UYbFoANH7pFdjaEJ3aGFZcYaE22-Ierf4iB… Chandan will take the session, introducing FUEL cloud module and if enough folks in audience interested then a quick review of the module can be done. FUEL Project (http://fuelproject.org/) is the largest and fastest growing open source based language resource repository that works to create standard terminology, style guide, assessment methodology etc with the help of community and different organizations. Currently it works with c.60 languages community One can exchange CDs, DVDs of new versions. All are welcome to attend the meeting. There is no fee to attend the meeting. See you there. -- Manjusha <http://manjushajoshi.wordpress.com/> _______________________________________ Pune GNU/Linux Users Group Mailing List -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Can the FOSS community save 197 endangered Indian languages? <http://opensource.com/community/14/7/save-endangered-language-today> -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Can the FOSS community save 197 endangered Indian languages? <http://opensource.com/community/14/7/save-endangered-language-today>

2 1

Re: [Openstack-i18n] Summaary of Paris Translators meeting
by Ying Chun Guo 07 Nov '14

07 Nov '14

I'm in the talk with Francois now. Transifex provides a report of all translators contributions, which could be viewed in projects, languages, and a specific duration. He suggested to send the translator contribution statics of each translation team to the coordinators, per month. I will add it as a TODO. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2014/11/05 17:49:33: > Ying Chun Guo/China/IBM > 2014/11/05 17:49 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Summaary of Paris Translators meeting > > Hello, team > > There was a session yesterday in Paris Design summit to gather > translators together. > There were 6 translation teams joined the meeting locally. They are > French team, Spanish team, German team, Catalan team, Chinese Taiwan > team, and Chinese team. > Some team members were trying to join the meeting remotely through > Google Hangout. Yet they failed because of a fault made by me. I'm > very sorry for that. > > We discussed how to build translation teams, how to make a high > quality translation, and how to maintain the priority definition of > documents. There are some good suggestions I could collect. Feel > free to add more if I miss. > > * how to build translation teams > #1: Use local Openstack meetups to promote translations > #2: Use a blog post on OpenStack planet to promote translations. > #3: Give the new comers a start point > #4: Give people a goal and a timeframe (a focus) > #5: A overall description of translation priorities, including both > docs and messages > #6: Create mailing lists on OpenStack infrastructure for local > translation teams > #7: Improve our tools to clearly state translators contributions and > teams progresses. Integrate with Stackalytics in the future. > > * how to make a high quality translation > #1: Maintain a glossary > #2: Report bugs to projects if the problems of translations are due > to the source strings, with a "i18n" tag. > #3: Report bugs i18n team if the problems of translations are due to > the translation quality, with a tag of language code. (https:// > bugs.launchpad.net/openstack-i18n) > #4: Keep on the improving of "Horizon translatable strings rules" ( > https://etherpad.openstack.org/p/i18n_translatable_strings) Educate > our developers. > > * how to maintain the priority definition of documents > #1: Team discussion and team decision, including both i18n team and doc team. > #2: Keep up to date of the priorities defined now: https:// > wiki.openstack.org/wiki/I18nTeam/docs-translation > > Let's define some action items based on these useful suggestions. > Keep on the discussion in the ML. We could make a list of actions > and owners in our next I18n meeting on Nov 20th. > The I18n meeting of this week will be ignored because of the summit. > > Thank you all for your active participation and contributions. > Merci. > > Best regards > Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Pootle and Zanata trial - summary of responses from translators
by Ying Chun Guo 05 Nov '14

05 Nov '14

Hello, all Till now, I got responses from 5 translators in Japanese, Korean, Spanish, French and Chinese translation team. 4 of them clearly described their preferences is Zanata. Here are some comments from them to support Zanata: "Using Zanata, cooperation with other translators is easier: chat room, listing translators who are translating at the same time, comments if a translation is rejected." "The role management of Zanata is powerful. It clearly defines translators, reviewers, and project maintainers." "I like the Project-wide search and replace feature in particular. It allows translators or maintainer to search for a word, a phrase, a sentence, or a paragraph and replace it across multiple files within a single project. It is extremely useful when you do the final editing or reviewing." "I guess the impression a translator can have is that Zanata is more user friendly, whilst Pootle looks a bit quirky makinf finding info or the right links a bir more difficult. I think Zanata is very easy to use and also promote s translator engagement." Also, there are some problems with Pootle which will block us: The support of CJK (Chinese font, Japanese font and Korean font) is poor, for example: saved translations in Korean font is ???; saved translations in CJK fonts do not seem to be recognized by the TM. No official client till now. Our current translation process (uploading, downloading and reviewing) could not be implemented. So as a summary of the translators evaluation, we would prefer to use Zanata. If you have any questions, please let me know. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2014/10/16 17:04:27: > Ying Chun Guo/China/IBM > 2014/10/16 17:04 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Pootle and Zanata trial > > Hello, team > > Pootle and Zanata trial are ready for test. > 1. Pootle > http://23.253.231.198/projects/ > 2. Zanata > http://15.126.226.230:8080/ > > I need volunteers to test features and feed back how satisfied you feel. > I use an Etherpad page to track: > https://etherpad.openstack.org/p/translation-tools-comparation > > I have gotten volunteers from Korean and Indian team. > I'm looking for volunteers from other translation teams. > > If you want to help, please let me know. > If you want to try admin features, send me emails with your account ID. > > Thank you. > > Best regards > Ying Chun Guo (Daisy)

1 1

Summaary of Paris Translators meeting
by Ying Chun Guo 05 Nov '14

05 Nov '14

Hello, team There was a session yesterday in Paris Design summit to gather translators together. There were 6 translation teams joined the meeting locally. They are French team, Spanish team, German team, Catalan team, Chinese Taiwan team, and Chinese team. Some team members were trying to join the meeting remotely through Google Hangout. Yet they failed because of a fault made by me. I'm very sorry for that. We discussed how to build translation teams, how to make a high quality translation, and how to maintain the priority definition of documents. There are some good suggestions I could collect. Feel free to add more if I miss. * how to build translation teams #1: Use local Openstack meetups to promote translations #2: Use a blog post on OpenStack planet to promote translations. #3: Give the new comers a start point #4: Give people a goal and a timeframe (a focus) #5: A overall description of translation priorities, including both docs and messages #6: Create mailing lists on OpenStack infrastructure for local translation teams #7: Improve our tools to clearly state translators contributions and teams progresses. Integrate with Stackalytics in the future. * how to make a high quality translation #1: Maintain a glossary #2: Report bugs to projects if the problems of translations are due to the source strings, with a "i18n" tag. #3: Report bugs i18n team if the problems of translations are due to the translation quality, with a tag of language code. ( https://bugs.launchpad.net/openstack-i18n) #4: Keep on the improving of "Horizon translatable strings rules" ( https://etherpad.openstack.org/p/i18n_translatable_strings) Educate our developers. * how to maintain the priority definition of documents #1: Team discussion and team decision, including both i18n team and doc team. #2: Keep up to date of the priorities defined now: https://wiki.openstack.org/wiki/I18nTeam/docs-translation Let's define some action items based on these useful suggestions. Keep on the discussion in the ML. We could make a list of actions and owners in our next I18n meeting on Nov 20th. The I18n meeting of this week will be ignored because of the summit. Thank you all for your active participation and contributions. Merci. Best regards Ying Chun Guo (Daisy)

1 0

Infrastructure Translations Tools session at Kilo Summit
by Elizabeth K. Joseph 31 Oct '14

31 Oct '14

Hello translators! Thanks for your work evaluating Pootle and Zanata, the etherpad[0] will be very helpful to us. If others could chime in on Pootle in the next week or so it would be great. The Infrastructure team has reserved a spot in our track at the summit next week in order to discuss the tools and next steps based on your input and what Andreas and I have discovered about maintainability and process with regard to both tools. The session will be on Thursday at 11AM local (Paris) time: http://kilodesignsummit.sched.org/event/d40800cfbdcd2c9cf752c3cede10cf6e#.V… Please join us if you're available. We've put some infrastructure notes and what we expect from the translations team in the "Summit session" part of our etherpad, so if there are other topics you wish to cover, please add them there: https://etherpad.openstack.org/p/kilo-translations If you're not available to join, feedback here on list, on the above etherpad or to Daisy, Andreas or myself is welcome so we can make sure your opinions/suggestions are represented at the session. [0] https://etherpad.openstack.org/p/translation-tools-comparation -- Elizabeth Krumbach Joseph || Lyz || pleia2

3 3

Need more inputs: Pootle and Zanata trial
by Ying Chun Guo 31 Oct '14

31 Oct '14

Hello, Thank you for those volunteers who are registered as testers: Chandan Kumar Sungjin Kang Tom Fifield Andreas Jaeger Marian Tort Pablo Iranzo Maxime Coquerel (ZiGMaX) I would like to collect more inputs from you. Please response to me with answers to those questions by next Tuesday: (You could response my personal email if you don't want to public your choice.) 1. Which tool do you prefer? 2. Why do you make such choice? e.g. what features of the selected tool do you like? what features of the other tool do you not like? Your inputs will help us to provide good translation services to all translators. Thank you in advance. Best regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2014/10/31 11:25 ----- Ying Chun Guo/China/IBM wrote on 2014/10/16 17:04:27: > Ying Chun Guo/China/IBM > 2014/10/16 17:04 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Pootle and Zanata trial > > Hello, team > > Pootle and Zanata trial are ready for test. > 1. Pootle > http://23.253.231.198/projects/ > 2. Zanata > http://15.126.226.230:8080/ > > I need volunteers to test features and feed back how satisfied you feel. > I use an Etherpad page to track: > https://etherpad.openstack.org/p/translation-tools-comparation > > I have gotten volunteers from Korean and Indian team. > I'm looking for volunteers from other translation teams. > > If you want to help, please let me know. > If you want to try admin features, send me emails with your account ID. > > Thank you. > > Best regards > Ying Chun Guo (Daisy)

1 0

Translation update process for stable branch(es)
by Akihiro Motoki 28 Oct '14

28 Oct '14

Hi all, In this mail I would like to discuss what releases do we accept translations. At now there is no systematic process when we import translations after the initial release of some version (Juno, Icehouse, ...). Importing translations to stable update is done occasionally so far. It is almost up to me. When I noticed some need for translation update (mainly in Japanese :-)), I propose a patch to import translations. It is really not systematic. If I am busy, I don't check it. This is the reason the first Icehouse update didn't have translation update. Questions are: - What release(s) we accept translations? Note that "Accept translations" means translations will be imported into a stable branch and releases as a part of the stable update release. My idea is to accept translations only for the latest stable release. - When should we import translations to a stable branch? Systematically (as a team)? Occasionally (up to someone's interest)? My vote is to import translations for each stable update of the latest stable branch. At least the first and second stable update (201X.Y.1 or .2) need to be considered. If we decide to do import as a stable release process as a team, we should assign someone to work on for each stable update (because I can't always take care of it). Assigned person(s) should check the date of a next stable update, check if there are new translations to be imported, and then propose a patch to import translations to a corresponding stable branch. I already have a consensus with the stable maintenance team that the deadline of translations import proposal is 3 day after the freeze date. The freeze date of a stable maintenance release is usually announced in stable-maint list. Thought? Any volunteer? -- Akihiro Motoki <amotoki(a)gmail.com>

4 9

OpenStack Docs and OpenStack Academy
by Frans Thamura 27 Oct '14

27 Oct '14

Hi all sorry for cross posting I have several schools, univs and company that join the translation program, and there are discussion regarding this work. because this is voluntaire based work they want a "aknowledgement" and this is my proposal to them 1. OpenStack User Group in their places (as sub OSUG). 2. OpenStack Translation Team 3. OpenStack Academic Team (because we start from Insallation Guide and Training Guide) In another area, the companies that work with me, now also bring to become HP Helion Partner (and Sub Partner) and Ubuntu Advantage Sub-Partner (Which I stand as partner of UA). Any legal thing that I must process, that I can guarrantee this work will grow the openstack movement in this country, and all the content from OpenStack will manage in the same web with OpenStack , https://www.transifex.com/organization/openstack/ I got this idea, because slow process in translation, and there are hugh 55.000 word we need to work :) My propsal If a school and univ commit to join the work, we can bring "OpenStack Translation Team" or "OpenStack Training Guide Team" but the logo of openstack is belong to "openstack foundation" any idea all Thx

2 2