- OpenStack-I18n - lists.openstack.org

IRC meeting tomorrow
by Ying Chun Guo 01 Jul '15

01 Jul '15

Hello, team We will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on July 2nd. I'm going to cover following topics: * Feature design: translation metrics in stackalytics * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

What's Up, Doc? 26 June 2015
by Lana Brindley 25 Jun '15

25 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, our M release has been named! Sadly, it hasn't cleared legal yet, so we can't publicly announce it, however, here are the poll results: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc It was a close-run contest! This week, I've been continuing to dust off some old bugs, and have been chatting to a few of our docs liaisons to work out how we can best get them engaged with what we're working on. I've also been spending a lot of time on standards questions, and thinking about the future of the DocImpact flag. == Progress towards Liberty == * RST conversion: ** Install Guide: Conversion is now ready to start, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is chugging along. Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also underway. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: In planning. Stand by for more info. * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has started on the Ironic docs, we're now trying to resolve some issues with service name standards ("Bare Metal" or "Bare metal"?). Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** No progress this week * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Thanks to Yusuke-san for closing bug 1330005! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Blueprint+Spec: TBD For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Docs Tools == Andreas and Nick just released openstack-docs-tools 0.29.1, after we discovered an RST translation bug in 0.29. Thanks for the quick turnaround on that! == Documentation Standards == There's been quite a lot of conversation this week over capitalisation of service names, with the community divided down the middle as to which we prefer! While we all enjoy a good style discussion, I've also asked Anne (in her role on the TC) to confirm the legal restrictions for us. Watch this space! In the meantime, continue to discuss this on the mailing list :) == Docs Liaisons == Don't forget that we have subject matter experts to help you with documentation questions that you might have. One of the best ways to get our liaisons' attention is to add them to a bug or a patch. Feel free to look up the liaison for the project you're working with, and add them to the cc list for your patch: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation == Doc team meeting == The APAC meeting was held this week, see the minutes here to catch up: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-06-24 Next meetings are: US: Wednesday 1 July, 14:00:00 UTC (note that this has NOT changed with daylight savings time) APAC: Wednesday 8 July, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… == Spotlight bugs for this week == Of the three bugs we spotlighted last week, one of them was closed (thanks Yusuke-san!), and the other two are still up for grabs. Olga is working on a Spotlight bug from last week, too. Let's keep the momentum, with another three sad old bugs that could use some love: https://bugs.launchpad.net/openstack-manuals/+bug/1212349 vmware documentation https://bugs.launchpad.net/openstack-manuals/+bug/1212687 xenapi https://bugs.launchpad.net/openstack-manuals/+bug/1239308 Add notifications for groups and roles - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVjOGvAAoJELppzVb4+KUy+3EH/RkUHZwCY6VS43k36x/d0ue9 Zl2Y8d9OJPZwElmhQ7Zl+LOpM1k+vpYDJs6WiCGiGsLVdg8tJX6bdoW1QZwH6+dV d2qR0yOitQ1/Z2W8y2EK6yAjMmLy7GU3fQBVi742A3g7V0FtbSduCEUwEWBdAv6A hIMY5nr5nXX0X0oiDro6XcdgHHLtIaFLpumbLE8AcPoYlAauaSjNyT7o4vKqz26u GxHioUtizv/G+fYWjeejQ3wFGRRbIU5H18h5ohPF4tPlUBKn3pHL7w9RCkzj/993 lJQh3fi4ONwIU0c5tHmqolXAAiWvzROf/l6da1BtSQeSp4qwR2XN+KcsZBQ1V/4= =Bq+e -----END PGP SIGNATURE-----

1 0

Help with RST translation tool chain needed
by Andreas Jaeger 22 Jun '15

22 Jun '15

The Japanese translation of the User Guide should be complete according to transifex but looking at docs.openstack.org/draft/ja/user-guide/ I see only a few words in Japanese. Building the guide locally, I see po files that are completely translated but somehow the sphinx tools are not picking these up properly. I'm puzzled on what's going wrong here. Is there anybody that can look at the RST building and tell us what's wrong - and fix if possible ;), please? Note to build the document locally yourself, you can run: tox -e buildlang -- ja Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

Terminologies
by Ying Chun Guo 19 Jun '15

19 Jun '15

Hello, In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources. Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9I… Best regards Ying Chun Guo (Daisy)

7 9

What's Up, Doc? 19 June 2015
by Lana Brindley 18 Jun '15

18 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, This week, I've been working on helping out the Ironic team to sort out their Install Guide (thanks have to go to Gauvain and Nick, who have offered to help out with writing assistance here), and trying to come up with some better ways to work with the i18n team, and our docs liaisons. More on all of that further in. == Progress towards Liberty == * RST conversion: ** Install Guide: Spec is merged, stand by for conversion to start ** Cloud Admin Guide: is well on the way. Get in touch with Brian or Joe, or sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also underway. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: In planning. Stand by for more info. * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** We now have a team starting to form to work on Ironic docs. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** No progress this week * Improve communication with Docs Liaisons ** I have now reached out to liaisons. More later in this newsletter. * Clearing out old bugs ** Thanks to Tom for closing bug 1195875. Let's keep up the great work! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Spec: https://review.openstack.org/#/c/183138/ ** Watch this space: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/reorganise-user-gu… ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Blueprint+Spec: TBD For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Docs Tools == Andreas will shortly be updating openstack-docs-tools to 0.29. == Docs Liaisons == Don't forget that we have subject matter experts to help you with documentation questions that you might have. As you're working on bugs, feel free to give them a quick ping or an email to ask questions. They promise not to laugh at you! https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation == i18n Team == At Summit, I spent a lot of time with Ying Chun Guo (Daisy) from the translation team, to try and come up with a way we can make sure our teams are working together better. To that end, we've got a few ideas we're going to be implementing over the next few weeks. First of all, this newsletter now goes direct to the the translation mailing list, as well the dev and doc lists (hi translators!). Secondly, Daisy is going to poll her team to identify an i18n documentation liaison, who will be the go-to person for all questions about translation for docs. The other thing we're going to do is to make sure we're helping the i18n team to keep their status page up to date: https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… If you're working on a doc that is translated, please check that table and make sure the translation team know what you're up to! This will help prevent needless effort on their part, which benefits us all in the end. == Doc team meeting == The US meeting was held this week, see the minutes here to catch up: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-06-17 Apologies for the timing confusion on that one, it seems as though daylight savings changes took us by surprise. For now, the meeting will remain at 1400UTC. If you would prefer it to be at a different time, bring it up on the mailing list, or in the next US meeting. Next meetings are: APAC: Wednesday 24 June, 00:30:00 UTC US: Wednesday 1 July, 14:00:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… == Spotlight bugs for this week == Of the three bugs we spotlighted last week, one of them got marked as invalid (thanks Tom!), and another is in progress with SME assistance (thanks Olga!). That's great! Here's another three dusty old bugs that could use a polish up: https://bugs.launchpad.net/openstack-manuals/+bug/1330005 Glance image properties and values (low hanging fruit) https://bugs.launchpad.net/openstack-manuals/+bug/1394397 Nova notification_driver https://bugs.launchpad.net/openstack-manuals/+bug/1205402 iPXE ISO boot support - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVg34hAAoJELppzVb4+KUyBWcIAM+914bjuU/6BwFQqWUwTiEA Ed5wAfdr55kE4QT6OZgaBWUH7e3qyjk6VHmfIKXKyoYaMXq82oT0gBEsJYH4PY46 q/lOYG9tkDUuPjA3i4ibPYClGfLC3Ku0zOdwG9alg/2AystOqW/VbGLRQLhHQavD JgZs5/iB8S1JvBhHEiAixMyRgM5NMuXiM/j6TXVTw1tSm3Iz1KRnm2z8RiYVxBYj 9HKHKNy50PFXpubnYYu+B6iBqWv2JggkeCYOL2G0MiQubdnoXekNCKxNlHKiaPPU xCTj3qzUNW/UJZHVLpQskuD736kli2pqkEbiCeuNcqd3VQicE6VvY3QV31kGU5c= =IC4Z -----END PGP SIGNATURE-----

1 0

Specialty teams connecting to translation team
by Anne Gentle 18 Jun '15

18 Jun '15

Hi all, I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who leads the i18N efforts for OpenStack. She would like each specialty team lead to connect with the i18N team to communicate the amount of change expected so that they can evaluate the timing of translation, and how much is done that can be translated. We also had a session with the i18N team and want to work on more communication with each team, and I think the specialty team leads are a great way to start that effort. Thoughts or ideas? Let us know. Thanks, Anne -- Anne Gentle annegentle(a)justwriteclick.com

4 6

common (RST) translation
by KATO Tomoyuki 17 Jun '15

17 Jun '15

Hi team, I'm translating User Guides (RST) recently. I found a below problem. Any thought? Problem: Each message catalog "pot" file contains all strings of the RST document, including "common" files (glossary and so on). In particular, "user-guide" and "user-guide-admin" resource at Transifex have same strings in "common" files respectively. This causes unintended inconsistency of translation. In fact, Japanese "user-guide" and "user-guide-admin" have different translated strings, which need to sync manually. Solution (just my idea): As is: 1. Sphinx(?) generates the "pot" file. 2. translate at Transifex. 3. Sphinx(?) merge the translated strings. To be: 1. Sphinx(?) generates the "pot" file. 2. A new script split message stringss for "common". (maybe, based on "msgcat") So, generate 2 resources (main document resource and "common" resource). 3. translate at Transifex. 4. merge the 2 resources for Sphinx(?). 5. Sphinx(?) merge the translated strings. Regards, KATO Tomoyuki

3 10

Criteria of core members and active members
by Ying Chun Guo 17 Jun '15

17 Jun '15

Hello, In today's IRC meeting, we discussed about the criteria of core members and active members. Here are some outputs. If you don't joined the discussion, please comment here. -------- I18n Core Contributors The coordinator of active language teams, who coordinates Dashboard translation or two documents translations during the previous two release cycles and attend team meetings at least once a month, will be granted as "I18n Core Contributors" I18n Active Contributors Translators or reviewers, who translate or review more than 200 words during the previous two release cycles, will be granted as "I18n Active Contributors" Best regards Ying Chun Guo (Daisy)

6 6

IRC Meeting
by Ying Chun Guo 17 Jun '15

17 Jun '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on June 18th. I'm going to cover following topics: * Review translation terminologies * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

French User Guide publication
by KATO Tomoyuki 17 Jun '15

17 Jun '15

Hi fdot, I noticed draft "fr/user-guide" link is broken[1]. Do you know what is the present situation? [1] http://docs.openstack.org/draft/draft-index.html Reagards, KATO Tomoyuki

3 4