Hi Daisy! I'm glad to see that the summit was eventful for the i18n team. I think I may be able to help with point 7 of the action list if any work is needed (especially on the puppet front ;) Best regards, -- Łukasz [DeeJay1] Jernaś On Wed, Nov 13, 2013 at 9:56 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Hi, all
The openstack summit was held last week. There were 4 sessions in total related with OpenStack I18n. I had chances to discuss with Doc team, Oslo team, Infra team and release management team about I18n tools and processes. I got very positive results. It turns out that leaders in OpenStack community think I18n as a very important area ( which is great ). [--snip--] I have the following items in my mind:
1. Publish Japanese operation guide in the website. Operation guide in other languages are welcomed too. For translation teams, if you have plans to translate, please let me know. We can figure out a reasonable plan for the translation work.
2. Re-organize the I18n wiki page. Clearly list our team structure. I plan to use "I18n team" and "L10n teams" to manage. I18n team will be responsible for OpenStack I18n, which means to help OpenStack to become a software that can be localized. I18n includes setting up translation process, changing code infrastructure, and so on. L10n teams will be responsible for OpenStack L10n, including translation and localization. People can join both I18n team and his/her L10n team. People can join only 1 team also. The wiki page shall list clearly these information. Here are good samples: https://l10n.gnome.org/teams/ and http://loco.ubuntu.com/teams/.
3. Use Launchpad to manage bugs and blueprints. Find a way to track the contributors. If we are not able to track them automatically, let's track them manually. Coordinators please help to track the contributors to your language translations. At least, remember and display their names.
4. Enable translation function in MediaWiki If we want to translate wiki page, we will use the translation function in MediaWiki itself to manage.
5. Separate log messages into different po files & enable messages IDs This work may need more developers to join.
6. Contact with Transifex, Pootle, Zanata, TranslationWiki to raise feature requirements.
7. Set up staging server for translated document review.
8. Continue translations in documents and messages.
Surely I'm not able to do all these works myself and I need all kinds of help. If you are suggests/comments to these items, please speak out. If you are interested in some, please sign up. Let's start the discussion in the mailing list.
We missed 1 IRC meeting because of the summit. We will have next IRC meeting next week on Nov 21th. At that time, hope we can have a clear plan at that time.
Regards Ying Chun Guo (Daisy)