[Openstack-i18n] Summaary of Paris Translators meeting
Ying Chun Guo
guoyingc at cn.ibm.com
Wed Nov 5 09:49:33 UTC 2014
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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20141105/7910b14c/attachment.html>
More information about the Openstack-i18n
mailing list