<html><body>
<p><font size="2" face="sans-serif">Hi, </font><tt><font size="2">Łukasz</font></tt><br>
<br>
<font size="2" face="sans-serif">Thank you for your signing up.</font><br>
<font size="2" face="sans-serif">It's one of the most interesting works.</font><br>
<br>
<font size="2" face="sans-serif">Publishing documents in a staging server will be much similar with publishing in official server, </font><br>
<font size="2" face="sans-serif">except staging server contains incomplete translated documents.</font><br>
<font size="2" face="sans-serif">I also plan to enable "comments/replies" in staging server, which will facilitate the discussion</font><br>
<font size="2" face="sans-serif">in review stage.</font><br>
<br>
<font size="2" face="sans-serif">We can discuss details in the future.</font><br>
<font size="2" face="sans-serif">At the beginning, I will suggest you to start from the current Jenkin scripts related with document publish.</font><br>
<font size="2" face="sans-serif">They are:</font><br>
<br>
<font size="2" face="sans-serif">modules/openstack_project/files/jenkins_job_builder/config/project.yaml</font><br>
<font size="2" face="sans-serif">modules/openstack_project/files/jenkins_job_builder/config/translation-jobs.yaml</font><br>
<font size="2" face="sans-serif">modules/openstack_project/files/zuul/layout-dev.yaml</font><br>
<font size="2" face="sans-serif">modules/openstack_project/files/zuul/layout.yaml</font><br>
<br>
<font size="2" face="sans-serif">You can get these files under <a href="http://git.openstack.org/cgit/openstack-infra/config/tree/">http://git.openstack.org/cgit/openstack-infra/config/tree/</a>.</font><br>
<font size="2" face="sans-serif">Clark Boylan from CI team can be a helpful people if we meet with problems.</font><br>
<br>
<font size="2" face="sans-serif">Thanks and regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<tt><font size="2">Łukasz Jernaś <deejay1@srem.org> wrote on 2013/11/14 20:41:53:<br>
<br>
> Łukasz Jernaś <deejay1@srem.org> </font></tt><br>
<tt><font size="2">> 2013/11/14 20:41</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo/China/IBM@IBMCN, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-i18n] What's up and what's next? I18n team</font></tt><br>
<tt><font size="2">> <br>
> Hi Daisy!<br>
> <br>
> I'm glad to see that the summit was eventful for the i18n team. I<br>
> think I may be able to help with point 7 of the action list if any<br>
> work is needed (especially on the puppet front ;)<br>
> <br>
> Best regards,<br>
> -- <br>
> Łukasz [DeeJay1] Jernaś<br>
> <br>
> On Wed, Nov 13, 2013 at 9:56 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:<br>
> > Hi, all<br>
> ><br>
> > The openstack summit was held last week.<br>
> > There were 4 sessions in total related with OpenStack I18n.<br>
> > I had chances to discuss with Doc team, Oslo team, Infra team and release<br>
> > management team about I18n tools and processes.<br>
> > I got very positive results.<br>
> > It turns out that leaders in OpenStack community think I18n as a very<br>
> > important area ( which is great ).<br>
> [--snip--]<br>
> > I have the following items in my mind:<br>
> ><br>
> > 1. Publish Japanese operation guide in the website.<br>
> > Operation guide in other languages are welcomed too.<br>
> > For translation teams, if you have plans to translate, please let me know.<br>
> > We can figure out a reasonable plan for the translation work.<br>
> ><br>
> > 2. Re-organize the I18n wiki page.<br>
> > Clearly list our team structure.<br>
> > I plan to use "I18n team" and "L10n teams" to manage.<br>
> > I18n team will be responsible for OpenStack I18n, which means to help<br>
> > OpenStack to become a software<br>
> > that can be localized. I18n includes setting up translation process,<br>
> > changing code infrastructure, and so on.<br>
> > L10n teams will be responsible for OpenStack L10n, including translation and<br>
> > localization.<br>
> > People can join both I18n team and his/her L10n team. People can join only 1<br>
> > team also.<br>
> > The wiki page shall list clearly these information.<br>
> > Here are good samples: <a href="https://l10n.gnome.org/teams/">https://l10n.gnome.org/teams/</a> and<br>
> > <a href="http://loco.ubuntu.com/teams/">http://loco.ubuntu.com/teams/</a>.<br>
> ><br>
> > 3. Use Launchpad to manage bugs and blueprints.<br>
> > Find a way to track the contributors.<br>
> > If we are not able to track them automatically, let's track them manually.<br>
> > Coordinators please help to track the contributors to your language<br>
> > translations.<br>
> > At least, remember and display their names.<br>
> ><br>
> > 4. Enable translation function in MediaWiki<br>
> > If we want to translate wiki page, we will use the translation function in<br>
> > MediaWiki itself to manage.<br>
> ><br>
> > 5. Separate log messages into different po files & enable messages IDs<br>
> > This work may need more developers to join.<br>
> ><br>
> > 6. Contact with Transifex, Pootle, Zanata, TranslationWiki to raise feature<br>
> > requirements.<br>
> ><br>
> > 7. Set up staging server for translated document review.<br>
> ><br>
> > 8. Continue translations in documents and messages.<br>
> ><br>
> > Surely I'm not able to do all these works myself and I need all kinds of<br>
> > help.<br>
> > If you are suggests/comments to these items, please speak out.<br>
> > If you are interested in some, please sign up.<br>
> > Let's start the discussion in the mailing list.<br>
> ><br>
> > We missed 1 IRC meeting because of the summit.<br>
> > We will have next IRC meeting next week on Nov 21th.<br>
> > At that time, hope we can have a clear plan at that time.<br>
> ><br>
> > Regards<br>
> > Ying Chun Guo (Daisy)<br>
> <br>
</font></tt></body></html>