<div dir="ltr">Very good Daisy, Thanks for the updates. <div><br></div><div>Let's do this! :)</div><div><br></div><div>Regards,</div><div>Gabriel.</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Nov 13, 2013 at 6:56 AM, Ying Chun Guo <span dir="ltr"><<a href="mailto:guoyingc@cn.ibm.com" target="_blank">guoyingc@cn.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><font face="sans-serif">Hi, all</font><br>
<br>
<font face="sans-serif">The openstack summit was held last week. </font><br>
<font face="sans-serif">There were 4 sessions in total related with OpenStack I18n.</font><br>
<font face="sans-serif">I had chances to discuss with Doc team, Oslo team, Infra team and release management team about I18n tools and processes.</font><br>
<font face="sans-serif">I got very positive results.</font><br>
<font face="sans-serif">It turns out that leaders in OpenStack community think I18n as a very important area ( which is great ).</font><br>
<font face="sans-serif">I summarize what happened in the summit here.</font><br>
<br>
<font face="sans-serif">1. Publishing translated documentation (<a href="https://etherpad.openstack.org/p/icehouse-doc-translation" target="_blank">https://etherpad.openstack.org/p/icehouse-doc-translation</a>)</font><br>
<br>
<font face="sans-serif">The translated document publish process was discussed in this session.</font><br>
<font face="sans-serif">The decision was to have two servers to publish translated documents: official server and staging server.</font><br>
<font face="sans-serif">The official server will be used to publish the well translated documents.</font><br>
<font face="sans-serif">Staging server will be used to host the ongoing translated documents, which will help the review process.</font><br>
<br>
<font face="sans-serif">2. Translation tools and scripts (<a href="https://etherpad.openstack.org/p/icehouse-summit-translation-tools-and-scripts" target="_blank">https://etherpad.openstack.org/p/icehouse-summit-translation-tools-and-scripts</a>)</font><br>
<br>
<font face="sans-serif">This discussion was held to decide whether we went away from Transifex (because of some well known reasons, </font><br>
<font face="sans-serif">if you don't know, please contact me) and moved to another translation platform.</font><br>
<font face="sans-serif">After comparing with several famous translation platforms, we figured out Transifex was the best one till now.</font><br>
<font face="sans-serif">As Transifex won't trun off in a short time, we will continue to use Transifex.</font><br>
<font face="sans-serif">At the same time, we will contact Transifex as well as other translation tool communities, to raise the feature</font><br>
<font face="sans-serif">requirements and see how they can satisfy us. Then we make decision in several months.</font><br>
<br>
<font face="sans-serif">3. I18n policies of messages (<a href="https://etherpad.openstack.org/p/icehouse-oslo-i18n-policies" target="_blank">https://etherpad.openstack.org/p/icehouse-oslo-i18n-policies</a>)</font><br>
<br>
<font face="sans-serif">This session was to discuss the messages translation policies.</font><br>
<font face="sans-serif">The result was to separate messages ( log messages, API response messages, and etc ) into different po files,</font><br>
<font face="sans-serif">and let translation teams/coordinators to decide the translation priorities.</font><br>
<font face="sans-serif">Another result was to introduce message IDs to log messages, which will enable searching and bug diagnosis</font><br>
<font face="sans-serif">if log messages are not in English. (It's a great change from the software architecture view.)</font><br>
<br>
<font face="sans-serif">4. Icehouse release schedule & coordination</font><br>
<br>
<font face="sans-serif">I had chance to explain our translation process with "big guys" in Openstack community.</font><br>
<font face="sans-serif">This session is more related with messages translation than documents translation.</font><br>
<font face="sans-serif">In a release cycle, message translations will be continuously imported into git repository.</font><br>
<font face="sans-serif">At last, the translation teams can decide which languages should be shipped with release. </font><br>
<font face="sans-serif">(None translation team supported languages will be removed.)</font><br>
<br>
<font face="sans-serif">Havana was called a conclusion, and Icehouse was just kicked off. </font><br>
<font face="sans-serif">We shall also make our plans in this release cycle.</font><br>
<font face="sans-serif"> </font><br>
<font face="sans-serif">I have the following items in my mind:</font><br>
<br>
<font face="sans-serif">1. Publish Japanese operation guide in the website.</font><br>
<font face="sans-serif">Operation guide in other languages are welcomed too.</font><br>
<font face="sans-serif">For translation teams, if you have plans to translate, please let me know.</font><br>
<font face="sans-serif">We can figure out a reasonable plan for the translation work.</font><br>
<br>
<font face="sans-serif">2. Re-organize the I18n wiki page.</font><br>
<font face="sans-serif">Clearly list our team structure.</font><br>
<font face="sans-serif">I plan to use "I18n team" and "L10n teams" to manage.</font><br>
<font face="sans-serif">I18n team will be responsible for OpenStack I18n, which means to help OpenStack to become a software</font><br>
<font face="sans-serif">that can be localized. I18n includes setting up translation process, changing code infrastructure, and so on.</font><br>
<font face="sans-serif">L10n teams will be responsible for OpenStack L10n, including translation and localization.</font><br>
<font face="sans-serif">People can join both I18n team and his/her L10n team. People can join only 1 team also.</font><br>
<font face="sans-serif">The wiki page shall list clearly these information.</font><br>
<font face="sans-serif">Here are good samples: <a href="https://l10n.gnome.org/teams/" target="_blank">https://l10n.gnome.org/teams/</a> and <a href="http://loco.ubuntu.com/teams/" target="_blank">http://loco.ubuntu.com/teams/</a>.</font><br>
<br>
<font face="sans-serif">3. Use Launchpad to manage bugs and blueprints.</font><br>
<font face="sans-serif">Find a way to track the contributors.</font><br>
<font face="sans-serif">If we are not able to track them automatically, let's track them manually.</font><br>
<font face="sans-serif">Coordinators please help to track the contributors to your language translations.</font><br>
<font face="sans-serif">At least, remember and display their names. </font><br>
<br>
<font face="sans-serif">4. Enable translation function in MediaWiki</font><br>
<font face="sans-serif">If we want to translate wiki page, we will use the translation function in MediaWiki itself to manage.</font><br>
<br>
<font face="sans-serif">5. Separate log messages into different po files & enable messages IDs</font><br>
<font face="sans-serif">This work may need more developers to join.</font><br>
<br>
<font face="sans-serif">6. Contact with Transifex, Pootle, Zanata, TranslationWiki to raise feature requirements.</font><br>
<br>
<font face="sans-serif">7. Set up staging server for translated document review.</font><br>
<br>
<font face="sans-serif">8. Continue translations in documents and messages.</font><br>
<br>
<font face="sans-serif">Surely I'm not able to do all these works myself and I need all kinds of help.</font><br>
<font face="sans-serif">If you are suggests/comments to these items, please speak out.</font><br>
<font face="sans-serif">If you are interested in some, please sign up.</font><br>
<font face="sans-serif">Let's start the discussion in the mailing list.</font><br>
<br>
<font face="sans-serif">We missed 1 IRC meeting because of the summit.</font><br>
<font face="sans-serif">We will have next IRC meeting next week on Nov 21th.</font><br>
<font face="sans-serif">At that time, hope we can have a clear plan at that time.</font><br>
<br>
<font face="sans-serif">Regards<br>
Ying Chun Guo (Daisy)<br>
</font></p></div><br>_______________________________________________<br>
Openstack-i18n mailing list<br>
<a href="mailto:Openstack-i18n@lists.openstack.org">Openstack-i18n@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
<br></blockquote></div><br></div>