- OpenStack-I18n - lists.openstack.org

IRC meeting today
by Ying Chun Guo 22 Jan '16

22 Jan '16

Hello, team We will have our regular meeting today, at 1300UTC in #openstack-meeting. I'm going to cover following topics: * Discussion: Glossary management process * Discussion: IBM contributions * Status update: Installation guide translation * Status update: Translation check website * Status update: Stackalytics feature Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

3 3

What's Up, Doc? 22 January 2016
by Lana Brindley 22 Jan '16

22 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, We seem to be more or less back into the swing of things here in docs land this week, with our meeting schedule back up and running, and now our very first full-length newsletter for 2016! We only have two and a half months until Mitaka goes out, but we're in great shape so far, with 345 bugs dealt with, and all the planned RST conversions complete. Most of the discussion this week has been around API documentation and Fairy Slipper, Docs Tools and some site theme changes, and a little back and forth on meeting times. == Progress towards Mitaka == 75 days to go! 345 bugs closed so far for this release. RST Conversions * All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :) Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Meeting moved http://lists.openstack.org/pipermail/openstack-docs/2016-January/008209.html. Kenneth finished his Galera patch https://review.openstack.org/#/c/263075/, there were also several patches from different contributors, so things are improving. '''Installation Guide - Christian Berendt''' AODH instructions near completion, EU/US meeting moved (Every two weeks (on even weeks) on Tuesday at 1600 UTC), APAC meeting will be dropped the next weeks if if not more participants join. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' One patch combining Images and Instances content merged, and a patch on Shared File Systems is now available for review. User Guide team meetings are set to begin next Thursday, with guidelines for combining admin and cloud admin files a topic for discussion. '''Ops and Arch Guides - Shilla Saebi''' No update this week. '''API Docs - Anne Gentle''' Anne imported and triaged over 60 GitHub Issues into Launchpad bugs. Anne working on build jobs for making API docs with fairy-slipper: https://review.openstack.org/#/c/269809. Anne emailed over 25 individuals about the plans for API docs and answered follow-up questions. Karen worked on validated Swagger: https://review.openstack.org/#/c/266527/. Need to release fairy-slipper this week or next. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Roger Luethi''' Liberty is making good progress, trying to get Liberty patches working. Early beginnings of Fedora support switched to CentOS. Copy-on-write disks for KVM. Bug fixing and refactoring, as usual. Early work on python port. Plan to host training labs on a web page. '''Training Guides - Matjaz Pancur''' German translation of the Upstream training (http://docs.openstack.org/de/upstream-training/) - this makes 3 full translations (en, de, ko_kr), ja is at 80%. A patch that enables direct bug reporting on the slides (https://review.openstack.org/#/c/259654/) several other patches. '''Hyperviser Tuning Guide - Joe Topjian''' No update this week. == Core Team Changes == The next core team review will occur on 1 February. In the meantime, it's probably a good time to go over what being a core means, and how the review system works. For more detail, see the Contributor Guide: http://docs.openstack.org/contributor-guide/docs-review.html Docs cores have the ability to +2 docs reviews, and they also have the ability to merge reviews. Reviews are merged by cores only once there's been *two* +2 votes, and at least one +1. There are very few exceptions to this rule, for changes that need to go through very quickly to resolve gate breakages or similar, but this rule holds in just about every situation. Cores are assigned based on merit, usually through the core review process that we do every month. During a core review, the PTL gathers statistics on reviews made, and patches created and merged, and uses that to determine who should be added to (or removed from) the core list. That then goes to a vote of the existing core team before being actioned and announced. Core team members also have the ability to nominate (and vote on) exceptional team members, where the statistics might not reflect the amount of effort they have put in. If you ever have any questions about becoming a docs core, or about getting your docs patch merged, you can contact the team on the usual docs mailing list, or ping any of us on IRC. == Doc team meeting == The US team meeting was held last week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-01-20 Next meetings: APAC: Wednesday 27 January, 00:30 UTC US: Wednesday 3 February, 14: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… Note that there is currently discussion about moving the US meeting four hours later to 20:00 UTC. If you have a strong opinion on this matter, make sure you weigh in on the mailing list thread: http://lists.openstack.org/pipermail/openstack-docs/2016-January/008206.html - -- Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWoafKAAoJELppzVb4+KUyFR8H/1so79V/BvFSAehklcbyDmZG JYkHQwrMUiTREN0y4l2ccegtgYWKeXEd01holKTMxxzR1KAcibi2eBMGjizNbIdt L8Add2BIPB8zwlqR0zrBAVKzecUth4EpvWLBTU4UDuHIHoF6cyOL3RZWKmkEg7/o GD7H/Yt264qFFPmQ8t8Flq5mUE892s2aReDVFkXPmmkNzBtIGDmzu13P6Y5zX4YX xzUSWJmBDTJPaz/0IsG8Sc46R3gs15hV7wtcCPwVtQXVZ18mKkYYz02zKQzpW518 Z8ysKgwHYkRhn+cxgsg10bV8/NePyxvgvHnknTLpbBZOV700kCmSTEmP3V3LUQw= =6VAi -----END PGP SIGNATURE-----

1 0

[OpenStack-i18n] Install guide finished translated Korean
by SungJin Kang 20 Jan '16

20 Jan '16

Hi, Install guide finished transtated ko_KR and review too. How to add draft site[1]? Thanks Sungjin. ps. not yet common-docs... [1]: http://docs.openstack.org/draft/draft-index.html

6 11

What's Up, Doc? 15 January
by Lana Brindley 15 Jan '16

15 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Welcome to 2016! A short newsletter this week as I get my feet back under me after my vacation. I hope you all had a wonderful holiday period, and got some well-earned down time. I'm looking forward to working hard with you all over the next few months to get Mitaka out into the wild :) == Progress towards Mitaka == 82 days to go! 324 bugs closed so far for this release. RST Conversions * All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :) Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == No updates this week, as I'm totally disorganised. Next week for sure! == Core Team Changes == I would like to offer a warm welcome to Atsushi Sakai as our newest core team member. Welcome to the team :) We will resume regular reviews in February 2016. == Doc team meeting == There's been some confusion over the meeting schedule, but as far as I can tell, these are the next meeting dates: Next meetings: US: Wednesday 20 January, 14:00 UTC APAC: Wednesday 27 January, 00:30 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… - -- Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWmHLwAAoJELppzVb4+KUydocH/30zQwOcQ7kOPSeWIYvGPJ6u /WO2Tv9QkoOZe4O7WulkTRXTsVTlr9lP3esANYf9Vys8E1720Wl3pPNL6YYJ8XCe 1WWIxZpZNiIRB86dfgJn6/oLdhNjAS6W6SvNHNKtecQ5m/6Kv0uRfpVHxw89BRBV +f5QvPnDsydUlKEamQJAyRWzKc6BnpM/AbgS20BL3/luhZpZI3V1Z2bnxbGJCRlD 10uAwY3+z6Oo3SCQI7HVe3TfZQDa6BBYPUK2KSlY5Kr8VjclEgy4tuootRd/4rva WCS4Z61XPvR6DQdLPS6RVCmCrkRtHd1yYeBZt5fP9GBDrXm2CUZipl13grZMXY8= =XuVl -----END PGP SIGNATURE-----

1 0

FW: [Bug 1534418] [NEW] Wrong Chinese translation in OpenStack Liberty install doc
by Kato, Tomoyuki 15 Jan '16

15 Jan '16

Hi Chinese team, Please take a look at the bug: https://bugs.launchpad.net/bugs/1534418 I can't understand what is wrong from the bug report =) > Subject: [Bug 1534418] [NEW] Wrong Chinese translation in OpenStack Liberty install doc > > Public bug reported: > > The original link is http://docs.openstack.org/liberty/install-guide-rdo/environment-ntp-control… > The translation draft link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/environment-ntp-c… > > ** Affects: openstack-i18n > Importance: Undecided > Status: New > > ** Attachment added: "01.png" > https://bugs.launchpad.net/bugs/1534418/+attachment/4550272/+files/01.png > > -- > > Title: > Wrong Chinese translation in OpenStack Liberty install doc > > Status in openstack i18n: > New > > Bug description: > The original link is http://docs.openstack.org/liberty/install-guide-rdo/environment-ntp-control… > The translation draft link is > http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/environment-ntp-c…

2 1

Re: [Openstack-i18n] How do we manage glossary?
by Akihiro Motoki 15 Jan '16

15 Jan '16

2016-01-05 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the patch, Akihiro. > I think it's easier to discuss in email. > So I copied your comments in your patch here. > >> Expected workflow: >> * add an entry to the master glossary: >> - Update glossary/master.yaml and review it on gerrit >> - Once approved, glossary-tool sync will update per-language glossary >> files and propose the update to gerrit (jenkins jos) > > In your design, when the changes to master.yaml is approved, how to trigger > the jenkins job ? using a tag ? > I think we could add one more action in this Jenkins job: automatically send > an email to i18n to notify that the glossary is changed. We can use 'post' pipeline to trigger some jobs when each change is merged. >> * update per-language glossary: >> - Each language team upload a proposed glossary to gerrit. A language team >> members review it and once they have a consensus i18n core reviewer merges >> it into the repository. >> - Once approved, a corresponding glossary PO file is generated and >> uploaded to Zanata. (glossary-tool write-po and jenkins job) > > In your design, translators will not use translation editor in Zanata to > translate glossary. > Translators will propose the glossary translation to gerrit. > I don't know if translators have enough training to commit a patch. > They may understand how to use Zanata more than how to use gerrit. > There is no commands to support uploading glossary to Zanata. > So the action to upload po files have to be executed manually. I think uploading glossary can be done by Jenkins job triggered by 'post' job as well. I agree that translators are familiar with Zanata rather than Gerrit to some extent. However, my question is still how to keep discussion contexts (or history/background). It seems Zanata history is associated with Zanata internal resource ID. I am afraid it can be easily lost and we cannot recover it :-( > How do you think if we change to: > - Update glossary/master.yaml and review it on gerrit. > - Once approved, glossary-tool sync will update per-language glossary files > and propose the update to gerrit (jenkins jos). > - The jenkins job will upload pot file in Zanata. > - The jenkins job will send email to i18n to notify the change. > - Translators log in to Zanata to translate. > - Jenkins job download po files to i18n repository. > - Zanata admin automatic update Zanata glossary. Again, how can we maintain discussion contexts? On the other hand, I might be thinking "context" too much. If we go to the above way you mentioned, I think we need to maintain discussion contexts in other places. If the team suggests to do so, I am okay. Japanese team actually maintains it in OpenStack wiki and it works mostly well except that we need to sync glossary manually, but it might be a small thing compared to keep "context". Keeping "context" will save time to explain why we choose THIS in our current glossary. If we do not have it, we need to explain same things to new contributors again and again, and this will increase the barrier to new contributors. >> * syntax when a review is proposed >>- 'glossary-tool' check verifies if YAML data is valid. It can be a part of >> pep8 target. > > Good to have syntax check. > > BTW, how do you think the advantage of YAML file, comparing with po and pot > files? > Because if we use po and pot files directly, we could put "note" as comments > in pot files. > Do you want "note" also be translated ? The only reason is YAML file is human-friendly and easy to edit by text editors. I don't think it is a good idea to edit PO file directly. The format is not human-friendly and we can easily make mistakes in editing PO files. "note" in a PO file will be overridden if the glossary is downloaded from Zanata. This means we need to manage PO files directly in our git repo. I don't think maintaining PO files is more difficult than maintaining YAML files. Finally, I would like to purge ancient glossary on Zanata as soon as possible. The current glossary harms translation and provides no value. Akihiro > > Regards > Daisy > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/05 07:05:51: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/01/05 07:07 >> Subject: Re: [Openstack-i18n] How do we manage glossary? > >> >> Hi Daisy and the team, >> >> 2015-12-17 19:35 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Hi, Akihiro >> > >> > Please let me know your comments to https://review.openstack.org/258924 >> >> I commented your above review. >> >> I proposed a counter proposal https://review.openstack.org/261767. >> This is just an idea. I am open to the input. >> >> Comments inline below. >> >> > Answers to your question: >> > >> > 1. Context >> > >> > The current solution in my patch could not satisfy this requirement >> > about >> > context. >> > If we want to put context to glossary, we need to develop our own >> > extension >> > of sphinx-build. >> > How do you think the priority to support context ? >> >> IMHO supporting contexts is important to make discussion on glossary >> productive. >> As you can see in Japanese glossary on OpenStack wiki [1], I believe >> that discussion contexts >> are important for further discussions and it also helps new >> contributors understand the background. >> >> In my proposal https://review.openstack.org/261767, >> we maintain all contexts in YAML glossary files. >> >> > 2. Process >> > >> > If people want to change the glossary, e.g. add, update, change the >> > comments, add coments >> > following process is designed. >> > >> > a> the requestor submits a patch to i18n repo >> > b> core team approve the patch >> > c> the auto uploading process is triggered. terminology.pot is uploaded >> > to >> > Zanata for translation >> > d> translators finish translation >> > e> Zanata admin manually patch terminology.pot and its translationpo >> > files, > >> > and upload to Zanata >> >> IMO the glossary needs to be reviewed more carefully compared to >> regular translations. >> In regular translations, all translated strings are imported, but for >> glossary it is better that >> only reviewed strings are imported. Another choice is to use gerrit >> for the glossary review. >> My proposal https://review.openstack.org/261767 implements the latter >> option. >> >> Thought? >> >> Thanks, >> Akihiro >> >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/12/02 02:29:44: >> > >> >> From: Akihiro Motoki <amotoki(a)gmail.com> >> >> To: "openstack-i18n(a)lists.openstack.org" >> >> <Openstack-i18n(a)lists.openstack.org> >> >> Date: 2015/12/02 02:32 >> >> Subject: [Openstack-i18n] How do we manage glossary? >> > >> >> >> >> Hi team, >> >> >> >> Recently we added the glossary to the i18n repo [1]. >> >> I wonder how we can manage the glossary and am sending this mail. >> >> The glossary can be referred to in Zanata, so it would be useful. >> >> >> >> Mainly I have two questions. >> >> >> >> The first point is what is the expected process to manage the glossary. >> >> How can we update the glossary? >> >> When is it uploaded to Zanata for translations? >> >> >> >> The second point is how we can have the context. >> >> I think the second point is also important. >> >> Each entry in our glossary has some background, for example >> >> why we reach the current consensus. >> >> This kind of context is important to discuss for further improvements. >> >> >> >> I updated the glossary for Japanese translation last week >> >> and I added various description about backgrounds of the glossary. >> >> I feel it is important to keep the context. >> >> How can we manage the context? >> >> >> >> I don't have a good idea now. >> >> I would like to raise these questions for broader discussion. >> >> >> >> Thanks, >> >> Akihiro >> >> >> >> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n >> >> >> >> _______________________________________________ >> >> Openstack-i18n mailing list >> >> Openstack-i18n(a)lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> >> > >> >

4 5

IBM translations to contribute
by Douglas Fish 12 Jan '16

12 Jan '16

2 2

[all][i18n] Proposed change for consistent setup of translation - up for review
by Andreas Jaeger 11 Jan '16

11 Jan '16

Projects that want to have translations, need to setup their repository in very specific ways which lead to quite a few questions from some of you and also quite different solutions. Let's make this easier - and consistent. I've written a spec that aims to provide a consistent set up for the repositories and ask for your review and comments on it: https://review.openstack.org/#/c/262545/ 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, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Re: [Openstack-i18n] How do we manage glossary - requirements priorities
by Akihiro Motoki 11 Jan '16

11 Jan '16

Thanks for initiating the effort. 2016-01-11 18:36 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hello, team > > There are three possible solutions to manage glossaries and their > translations. > All of these solutions have their advantages and disadvantages. > I think we should prioritize the requirements firstly, then we make the > choice based on the requirements. > Here I list some requirements. > I would like to suggest to distinguish "master glossary" (in the source language) and "per-language glossary" in this discussion. Theoretically speaking, each language team can have its own glossary, but IIUC Zanata glossary does not allows it and we need to have a common glossary entries. As the assumption of this discussion, should we assume the current enabled feature in Zanata or can we assume to enhancing Zanata? I would suggest to distinguish 'requirements' and the current limitation of Zanata. 'requirement' should not have assumption based on 'the current limitation of Zanata'. Now, I am looking through the listed items. #0 each language team can manage their glossary without 'admin' role. At least, language coordinator and reviewers should be allowed to do it. To me, this is the top priority "must to have". > #1. Save glossaries in i18n repo "nice to have" "master" or "per-language"? Based on #2 below, it seems "master glossary". > #2. Translate and review with Zanata editor, and enable the auto sync > between Zanata editor and i18n repo. In #2, it seems two things are mixed. The first part "Translate and review with Zanata editor", yes it is a requirement. The second part is just a process. It is not a requirement, i.e., "nice to have". > #3. View comments while translating "Must to have" (as the second priority) I believe it is "Must to have" but it is not a top priority because the top priority to me is that each language is allowed to maintain their glossary without 'admin' privilege. > #4. Review the new added glossary by Gerrit "not necessary" I am not sure this needs to be done in Gerrit. If we have a way to add a new entry in Zanata, it is sufficient as well. I am not sure what assumption you have. > #5. View the list of glossaries and their comments in i18n documents. "not necessary" I don't think it is a requirement. I hope the list of glossary on Zanata instead as Transfix does. When we go to "Glossary" link at the top of Zanata UI https://translate.openstack.org/glossary/view.seam, we see a list of languages but when we click a language name, we will get a list of members of each language team. It is a confusing behavior and we expect a glossary in each language. > #6. Keep the history of glossary translations and discussions. "must to have" (as the second priority) Yes. this is important! > > Please let me know your thoughts to these requirements. > You can add comment "Must support", "good to have", and "not necessary" to > each requirement, > and order these requirements by the priority in your mind. > If you have other requirements, feel free to add. /FYI/ I abandoned my reviews to keep my review list small. Feel free to restore them if necessary even after this discussion have a consensus. Thanks, Akihiro > > For your reference, here are the three possible solutions: > > - Solution 1 Save glossaries in pot file and translations in po files. > The current solution in repo: openstack/i18n > Support requirement #1 , #2 and #4 > ( @Alex, please help to verify if #3 and #6 could be satisfied in this > solution.) > > - Solution 2 Save glossaries in rst file and translations in po files. > https://review.openstack.org/#/c/258924/ > Support requirement #1, #2, and #4, #5 > > - Solution 3 Save glossaries in YAML file and translations in YAML files. > https://review.openstack.org/#/c/261767/ > https://review.openstack.org/#/c/262710/ > Support requirement #1, #3 and #4, #6 > > Your input will help us to make a team decision. > Thank you. > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/05 19:09:09: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/01/05 19:10 >> Subject: Re: [Openstack-i18n] How do we manage glossary? >> >> 2016-01-05 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Thank you for the patch, Akihiro. >> > I think it's easier to discuss in email. >> > So I copied your comments in your patch here. >> > >> >> Expected workflow: >> >> * add an entry to the master glossary: >> >> - Update glossary/master.yaml and review it on gerrit >> >> - Once approved, glossary-tool sync will update per-language glossary >> >> files and propose the update to gerrit (jenkins jos) >> > >> > In your design, when the changes to master.yaml is approved, how to >> > trigger >> > the jenkins job ? using a tag ? >> > I think we could add one more action in this Jenkins job: automatically >> > send >> > an email to i18n to notify that the glossary is changed. >> >> We can use 'post' pipeline to trigger some jobs when each change is >> merged. >> >> >> * update per-language glossary: >> >> - Each language team upload a proposed glossary to gerrit. A language >> >> team >> >> members review it and once they have a consensus i18n core reviewer >> >> merges >> >> it into the repository. >> >> - Once approved, a corresponding glossary PO file is generated and >> >> uploaded to Zanata. (glossary-tool write-po and jenkins job) >> > >> > In your design, translators will not use translation editor in Zanata to >> > translate glossary. >> > Translators will propose the glossary translation to gerrit. >> > I don't know if translators have enough training to commit a patch. >> > They may understand how to use Zanata more than how to use gerrit. >> > There is no commands to support uploading glossary to Zanata. >> > So the action to upload po files have to be executed manually. >> >> I think uploading glossary can be done by Jenkins job triggered by >> 'post' job as well. >> I agree that translators are familiar with Zanata rather than Gerrit >> to some extent. >> >> However, my question is still how to keep discussion contexts (or >> history/background). >> It seems Zanata history is associated with Zanata internal resource ID. >> I am afraid it can be easily lost and we cannot recover it :-( >> >> > How do you think if we change to: >> > - Update glossary/master.yaml and review it on gerrit. >> > - Once approved, glossary-tool sync will update per-language glossary >> > files >> > and propose the update to gerrit (jenkins jos). >> > - The jenkins job will upload pot file in Zanata. >> > - The jenkins job will send email to i18n to notify the change. >> > - Translators log in to Zanata to translate. >> > - Jenkins job download po files to i18n repository. >> > - Zanata admin automatic update Zanata glossary. >> >> Again, how can we maintain discussion contexts? >> >> On the other hand, I might be thinking "context" too much. >> If we go to the above way you mentioned, >> I think we need to maintain discussion contexts in other places. >> If the team suggests to do so, I am okay. >> >> Japanese team actually maintains it in OpenStack wiki and it works mostly >> well >> except that we need to sync glossary manually, but it might be a small >> thing >> compared to keep "context". Keeping "context" will save time to explain >> why >> we choose THIS in our current glossary. If we do not have it, we need to >> explain same things to new contributors again and again, and this >> will increase >> the barrier to new contributors. >> >> >> * syntax when a review is proposed >> >>- 'glossary-tool' check verifies if YAML data is valid. It can be a part >> >> of >> >> pep8 target. >> > >> > Good to have syntax check. >> > >> > BTW, how do you think the advantage of YAML file, comparing with po and >> > pot >> > files? >> > Because if we use po and pot files directly, we could put "note" as >> > comments >> > in pot files. >> > Do you want "note" also be translated ? >> >> The only reason is YAML file is human-friendly and easy to edit by >> text editors. >> I don't think it is a good idea to edit PO file directly. >> The format is not human-friendly and we can easily make mistakes in >> editing PO files. >> >> "note" in a PO file will be overridden if the glossary is downloaded >> from Zanata. >> This means we need to manage PO files directly in our git repo. >> I don't think maintaining PO files is more difficult than maintaining >> YAML files. >> >> >> Finally, I would like to purge ancient glossary on Zanata as soon >> aspossible. >> The current glossary harms translation and provides no value. >> >> Akihiro >> >> >> > >> > Regards >> > Daisy >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/05 07:05:51: >> > >> >> From: Akihiro Motoki <amotoki(a)gmail.com> >> >> To: Ying Chun Guo/China/IBM@IBMCN >> >> Cc: "openstack-i18n(a)lists.openstack.org" >> >> <Openstack-i18n(a)lists.openstack.org> >> >> Date: 2016/01/05 07:07 >> >> Subject: Re: [Openstack-i18n] How do we manage glossary? >> > >> >> >> >> Hi Daisy and the team, >> >> >> >> 2015-12-17 19:35 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> >> > Hi, Akihiro >> >> > >> >> > Please let me know your comments to >> >> > https://review.openstack.org/258924 >> >> >> >> I commented your above review. >> >> >> >> I proposed a counter proposal https://review.openstack.org/261767. >> >> This is just an idea. I am open to the input. >> >> >> >> Comments inline below. >> >> >> >> > Answers to your question: >> >> > >> >> > 1. Context >> >> > >> >> > The current solution in my patch could not satisfy this requirement >> >> > about >> >> > context. >> >> > If we want to put context to glossary, we need to develop our own >> >> > extension >> >> > of sphinx-build. >> >> > How do you think the priority to support context ? >> >> >> >> IMHO supporting contexts is important to make discussion on glossary >> >> productive. >> >> As you can see in Japanese glossary on OpenStack wiki [1], I believe >> >> that discussion contexts >> >> are important for further discussions and it also helps new >> >> contributors understand the background. >> >> >> >> In my proposal https://review.openstack.org/261767, >> >> we maintain all contexts in YAML glossary files. >> >> >> >> > 2. Process >> >> > >> >> > If people want to change the glossary, e.g. add, update, change the >> >> > comments, add coments >> >> > following process is designed. >> >> > >> >> > a> the requestor submits a patch to i18n repo >> >> > b> core team approve the patch >> >> > c> the auto uploading process is triggered. terminology.pot is >> >> > uploaded >> >> > to >> >> > Zanata for translation >> >> > d> translators finish translation >> >> > e> Zanata admin manually patch terminology.pot and its translationpo >> >> > files, >> > >> >> > and upload to Zanata >> >> >> >> IMO the glossary needs to be reviewed more carefully compared to >> >> regular translations. >> >> In regular translations, all translated strings are imported, but for >> >> glossary it is better that >> >> only reviewed strings are imported. Another choice is to use gerrit >> >> for the glossary review. >> >> My proposal https://review.openstack.org/261767 implements the latter >> >> option. >> >> >> >> Thought? >> >> >> >> Thanks, >> >> Akihiro >> >> >> >> > >> >> > Best regards >> >> > Ying Chun Guo (Daisy) >> >> > >> >> > >> >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/12/02 02:29:44: >> >> > >> >> >> From: Akihiro Motoki <amotoki(a)gmail.com> >> >> >> To: "openstack-i18n(a)lists.openstack.org" >> >> >> <Openstack-i18n(a)lists.openstack.org> >> >> >> Date: 2015/12/02 02:32 >> >> >> Subject: [Openstack-i18n] How do we manage glossary? >> >> > >> >> >> >> >> >> Hi team, >> >> >> >> >> >> Recently we added the glossary to the i18n repo [1]. >> >> >> I wonder how we can manage the glossary and am sending this mail. >> >> >> The glossary can be referred to in Zanata, so it would be useful. >> >> >> >> >> >> Mainly I have two questions. >> >> >> >> >> >> The first point is what is the expected process to manage the >> >> >> glossary. >> >> >> How can we update the glossary? >> >> >> When is it uploaded to Zanata for translations? >> >> >> >> >> >> The second point is how we can have the context. >> >> >> I think the second point is also important. >> >> >> Each entry in our glossary has some background, for example >> >> >> why we reach the current consensus. >> >> >> This kind of context is important to discuss for further >> >> >> improvements. >> >> >> >> >> >> I updated the glossary for Japanese translation last week >> >> >> and I added various description about backgrounds of the glossary. >> >> >> I feel it is important to keep the context. >> >> >> How can we manage the context? >> >> >> >> >> >> I don't have a good idea now. >> >> >> I would like to raise these questions for broader discussion. >> >> >> >> >> >> Thanks, >> >> >> Akihiro >> >> >> >> >> >> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n >> >> >> >> >> >> _______________________________________________ >> >> >> Openstack-i18n mailing list >> >> >> Openstack-i18n(a)lists.openstack.org >> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> >> >> >> > >> >> >> > >> >

1 0

Austin OpenStack Summit call-for-papers is open
by Ying Chun Guo 11 Jan '16

11 Jan '16

Hello, team The next OpenStack Summit will take place on April 25-29 in Austin, Texas, US. The Call for Papers is opened and will close on Feb 1st. You could find details on the tracks and process on the official page: https://www.openstack.org/summit/austin-2016/call-for-speakers/. I think following tracks are much related with our work. You are welcomed to submit speech proposals to these tracks. * Project Updates * How to Contribute * Upstream Development * Working Groups The track "Working Groups" is special. It is for collaborative working sessions rather than presentations. It will be in smaller rooms and video record will not be served. We can organize I18n/translations related working sessions in this track. If you have any speeches or discussion topics related with I18n/translations, you can contact with me. I'm happy to help review and schedule. BTW, the travel support program is opened at: https://www.openstack.org/summit/austin-2016/austin-and-travel/#travel-supp… . The deadline is Feb 9. Thank you. Best regards Ying Chun Guo (Daisy)

1 0