August 2017 - OpenStack-I18n - lists.openstack.org

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Doug Hellmann 02 Aug '17

02 Aug '17

[resending to the lists] > On Aug 1, 2017, at 10:55 AM, Doug Hellmann <doug(a)doughellmann.com> wrote: > > Excerpts from Andreas Jaeger's message of 2017-08-01 08:57:09 +0200: >> On 2017-07-31 22:46, Doug Hellmann wrote: >>> Excerpts from Ian Y. Choi's message of 2017-08-01 03:16:09 +0900: >>>> [...] >>>> 2. Draft index page for translated documents was also removed >>>> >>>> Previously, Docs team maintained draft documents for the master branch >>>> (which will be the stable branch >>>> after the official release and the document stables) on >>>> https://docs.openstack.org/draft/draft-index.html page. >>>> It also contained translated draft documents and I18n team accessed the >>>> page to see whether translated documents >>>> render well or not, and also review translated strings. >>>> >>>> I did not notice when I saw the spec [1], but recently, I noticed that >>>> the the draft-index.html page was deprecated >>>> by [next-release-name]/index.haml (e.g., >>>> https://docs.openstack.org/pike/index.html ) [4]. >>>> >>>> Since I18n team encourages translation review for the better quality of >>>> translations, it is a good idea to see >>>> draft documents before language landing pages have the link to fully >>>> translated and reviewed documents. >>> >>> Is it possible to see the draft of a translation by reviewing the >>> output of the job that proposes the patch containing the translated >>> text? >> >> Currently not, it needs publishing to docs-draft and a way to access the >> multiple documents. Note this needs handling for both openstack-manuals >> and project repos like neutron (networking-guide). > > Could we make it work that way? I understand why we need a separate > review step for the translations, but not why we need a separate > copy of the docs published outside of the context of a job in order > to perform that review. (This is probably just me not understanding > how a tool works.) > >> >>>> Motoki-san proposed an idea of translation status support using an yaml >>>> file in openstack-manuals [5], >>>> and I would like to discuss with I18n team how we deal with the change >>>> of draft index page. >>> >>> How would that flag or information be used? >>> >> >> WE could just have the link to it added - dependent on the flag - to either: >> * language index >> * draft index > > It seems like we want a list of languages for which there are > translations for a given set of docs. We could use that to populate > templates in a few different ways (link from the English version > to the other languages, link from a $language landing page to all > of the guides in that language, etc.). > > I can advise someone on how to add those features, if we have a > volunteer. > > Doug

3 4

[StringFreeze] Soft period was over - Plz contribute translation for the release!
by Ian Y. Choi 02 Aug '17

02 Aug '17

Dear language coordinators & translators! Only a few weeks left before official Pike release [1] and I would like to inform you that the last week was the Soft StringFreeze period. Language teams need to focus on Horizon and Horizon-related projects before all translated strings will be packaged for upcoming release. According to the dashboard on https://translate.openstack.org, our targeted priorities look as follows: - Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Magnum UI (Medium) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - neutron-lbaas-dashboard (Medium) - Murano Dashboard (Low) - Designate Dashboard (Low) - TripleO UI (Low) All of those and more additional target projects grouped in [2] in *master* branch and current & next PTL will check feature freeze status on projects listed above. He will create a stable version: *stable-pike* in Zanata for the target projects after the project have stable/pike branch. Although the stable version has not been created yet, but it is highly encouraged to translate those projects from now, since StringFreeze periods are relatively short (about 2 weeks of RC1, then HardStringFreeze). For more details on how I18n team is doing with releases (especially Horizon & plugin projects), please see [3]. If you have questions, feel free to ask through openstack-i18n at lists.openstack.org mailing list or ask I18n members on Freenode #openstack-i18n channel. Thank you all for your contribution! [1] https://releases.openstack.org/pike/schedule.html [2] https://translate.openstack.org/version-group/view/pike-dashboard-translati… [3] https://docs.openstack.org/i18n/latest/release_management.html With many thanks, /Ian

4 3

French member with no role
by Akihiro Motoki 02 Aug '17

02 Aug '17

Hi French team coordinators, I see one member in French language team has no role. What does this mean? Is he considered as a translator? This is just a question and to clarify the situation. I see a warning every time I run a script to sync Zanata users list into the i18n repo. Thanks, Akihiro

2 3

[Elections] Candidacy for I18n PTL (Queens)
by Frank Kloeker 02 Aug '17

02 Aug '17

Good morning! Today I would like to announce my candidacy as I18n PTL in Queens cycle. I've been in the OpenStack Community since 2015, active as a translator in the German team. I participated in my first OpenStack Summit in Tokyo and met the I18n team for the first time at the Design Summit. It was an exciting moment to meet people from all over the world working on the same thing. It is not just translations, but working with different cultures, views and ... time zones. These are the magical dimensions and challenges. After Tokyo we had virtual midcycle sprint to develop the translation check site, one of the tools to help translators in their work. I met more people during Barcelona Summit and sank deeper and deeper into the work of OpenStack and I18n. In Boston we had our own session to show the work of the I18n team. We prepared a workshop also which was not so successful, but the preparation was great and we can repeat it at any time. At this point I would like to thank Ianychoi for his excellent work in the past as PTL. He is tireless, full of energy, and brought I18n far forward. He was for me in the last weeks a kind of mentor to learn all the things related to I18n and PTL. Nevertheless, I still need support from the entire team to successfully manage this task. What goals have I set for myself for Queens: 1. Completion of the translation check site. I have been involved in this project since 2015 and now it has to be finished :-) 2. Automate all the things. We have some manual work in I18n and our tools that are to automate to make the work easier. 3. Aquire more people to the team. We have great teams that do a lot. But we also get more work through translate new OpenStack projects or the User Survey. I hope I have given a good overview. Contact me directly if you have any questions or requests. On good cooperation in a new cycle of OpenStack! kind regards Frank Email: eumel(a)arcor.de IRC: eumel8 Twitter: eumel_8 OpenStack Profile: https://www.openstack.org/community/members/profile/45058/frank-kloeker

2 1

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Andreas Jaeger 02 Aug '17

02 Aug '17

On 2017-07-31 22:46, Doug Hellmann wrote: > [...] > This is good to know. I am going to need someone who knows how the > translation jobs work to help set those up. I can assist, but I do not > know how they work so I cannot lead that effort. Doug, I'm happy to have a discussion with you - and anybody else - on these. We can do a special IRC session or some kind of videochat. Who else wants to join? Once I know participants, let's set up something... Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Andreas Jaeger 01 Aug '17

01 Aug '17

On 2017-07-31 22:46, Doug Hellmann wrote: > Excerpts from Ian Y. Choi's message of 2017-08-01 03:16:09 +0900: >> [...] >> 2. Draft index page for translated documents was also removed >> >> Previously, Docs team maintained draft documents for the master branch >> (which will be the stable branch >> after the official release and the document stables) on >> https://docs.openstack.org/draft/draft-index.html page. >> It also contained translated draft documents and I18n team accessed the >> page to see whether translated documents >> render well or not, and also review translated strings. >> >> I did not notice when I saw the spec [1], but recently, I noticed that >> the the draft-index.html page was deprecated >> by [next-release-name]/index.haml (e.g., >> https://docs.openstack.org/pike/index.html ) [4]. >> >> Since I18n team encourages translation review for the better quality of >> translations, it is a good idea to see >> draft documents before language landing pages have the link to fully >> translated and reviewed documents. > > Is it possible to see the draft of a translation by reviewing the > output of the job that proposes the patch containing the translated > text? Currently not, it needs publishing to docs-draft and a way to access the multiple documents. Note this needs handling for both openstack-manuals and project repos like neutron (networking-guide). >> Motoki-san proposed an idea of translation status support using an yaml >> file in openstack-manuals [5], >> and I would like to discuss with I18n team how we deal with the change >> of draft index page. > > How would that flag or information be used? > WE could just have the link to it added - dependent on the flag - to either: * language index * draft index Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Summary of how I18n affects with doc-migration
by Ian Y. Choi 01 Aug '17

01 Aug '17

Hello translators, The OpenStack manuals project migration [1] has been going well, and I would like to share what I have found which things influence on I18n activities from the perspective of translators, since some translators asked me about missing some openstack-manuals documents in Zanata. 1. Removal of documents in openstack-manuals project in Zanata In [2], the following documents are not currently visible : admin-guide, arch-design, networking-guide, ops-guide, user-guide . For several release cycles, there have been less amount contribution on admin-guide (migrating to each project tree) and arch-design (deprecated). For networking-guide, translating in stable-ocata will be preserved, but master version was removed and the content will be migrated into neutron repository. User-guide will be migrated and divided between the horizon repository and python-openstackclient repository. If the strings for the migrated projects (admin-guide, networking-guide, and user-guide) would be the same as the removed strings in openstack-manuals, I18n team expects that translation memory merge functionality in Zanata would be able to fill out translations for the migrated projects. Note that the translation support work of migrated documents will be started after the migration completes and I18n team need volunteers for the work. 2. Draft index page for translated documents was also removed Previously, Docs team maintained draft documents for the master branch (which will be the stable branch after the official release and the document stables) on https://docs.openstack.org/draft/draft-index.html page. It also contained translated draft documents and I18n team accessed the page to see whether translated documents render well or not, and also review translated strings. I did not notice when I saw the spec [1], but recently, I noticed that the the draft-index.html page was deprecated by [next-release-name]/index.haml (e.g., https://docs.openstack.org/pike/index.html ) [4]. Since I18n team encourages translation review for the better quality of translations, it is a good idea to see draft documents before language landing pages have the link to fully translated and reviewed documents. Motoki-san proposed an idea of translation status support using an yaml file in openstack-manuals [5], and I would like to discuss with I18n team how we deal with the change of draft index page. 3. Archiving translated documents is also needed Liberty translated documents (e.g., [6]) and translated documents which were migrated (e.g., [7], [8]) are still accessible through docs.o.o. In my opinion, those translated documents are also the target of archiving documents [9]. For translated documents, I think just publishing htmls as read-only (e.g., github pages?) would be fine, and the work needs volunteers. With many thanks, /Ian [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migra… [2] https://translate.openstack.org/iteration/view/openstack-manuals/master/doc… [3] https://translate.openstack.org/iteration/view/openstack-manuals/stable-oca… [4] https://docs.openstack.org/pike/index.html [5] http://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-… [6] https://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/ [7] https://docs.openstack.org/ja/user-guide/ [8] https://docs.openstack.org/ja/ops-guide/ [9] http://specs.openstack.org/openstack/docs-specs/specs/pike/archiving.html [10] https://etherpad.openstack.org/p/denver-doc-PTG

2 1