- OpenStack-I18n - lists.openstack.org

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

29 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, An incredibly hot week here in the antipodes, coupled with Australia Day has meant that I haven't been particularly productive this week. Luckily, the rest of you have picked up the slack, and things have been ticking along nicely. Thanks everyone :) == Progress towards Mitaka == 68 days to go! 368 bugs closed so far for this release. RST Conversions * All planned RST conversions are now complete! 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''' No update this week. '''Installation Guide - Christian Berendt''' AODH install instructions merged '''Networking Guide - Edgar Magana''' Networking guide versioning has been completed, we are publishing Liberty and Mitaka releases. Networking guide ToC has been updated and missing chapter have been assigned. Etherpad with the topic missing from the guide: https://etherpad.openstack.org/p/networking-guide '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' Team meetings started again this week, and the large point was an IA reorg after content merging. Other discussion point included checking in with Docs liasons for Sahara, Trove, Murano, and Magneto plus checking in with interested volunteers for the User Guide Team. '''Ops and Arch Guides - Shilla Saebi''' Reorganization of the architecture guide is on-going. We have a full team of volunteers on our wiki <https://wiki.openstack.org/wiki/Documentation/OpsGuide>, but not much traction. We need more volunteers and we were looking to do a swarm in Manchester but not enough team members attending. Looking to maybe set one up for Austin. '''API Docs - Anne Gentle''' No update this week. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Liberty support continues to make good progress. We can now launch an instance VM. Some clean up and reviewing still needs to be done. '''Training Guides - Matjaz Pancur''' Preparations for Austin Upstream training (https://review.openstack.org/#/c/271006/) New landing page for Training guides (http://docs.openstack.org/draft/training-guides/. '''Hypervisor Tuning Guide - Joe Topjian''' An update to to the Guide was posted back in December with a call for participation: http://lists.openstack.org/pipermail/openstack-operators/2015-December/0091… == Doc team meeting == Next meetings: US: Wednesday 3 February, 14:00 UTC APAC: Wednesday 10 February, 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… 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/ iQEcBAEBCAAGBQJWquVYAAoJELppzVb4+KUyBTQH/0M+ixT7g/MIePoZpFms5aSU SvLV/rAJe1dKbB2tNfq5ozNcWS/uMHB+w4bzHGjP+xexOvTUZNoBrKGLcufADMSS ekOMITnr69PLlXh5e+/G55/02sZUFmmq4ZC2xmDrgGbwZLohbLUA/L1G3o+oJGYy 2/KrNAQCutkEKTNwAN4NkA+cbSj8jM8UyVWfFzfEbywSmpmrrQyetEhfmZPj3g9t 7cUnqrRegHI7mwPGeLyM3O2bIj3CLKsmWDFEfzOfoUGDGDCQ6yGj8iv8u4PuA6Zt Mw041/PII0LWDCSvovYnsRoZXMcRGVFfWdBvrOVZaGZfVhZLK/2BrZPIr+r6EzA= =eKF8 -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] IBM translations to contribute
by Akihiro Motoki 28 Jan '16

28 Jan '16

Hi Doug, First, I don't have any strong opinion on importing Mitaka translation contribution from IBM. Any decision is okay to me. The reason is described below. In addition, as an i18n active member, growing OpenStack translation folks is important but each language team should be a team. All comments below is as one of Japanese team reviewer who reviewed about 50% of strings (> 10000 messages) in Liberty release. I hope the same thing never happens in the Nxx release. Before going to the detail, I must apologize my following message is rude, but let me share my feeling as an active Japanese reviewer. 2016-01-13 0:02 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Hi Akihiro, > > I understand your concern. These are translations that were completed > outside of Zanata, using our previous process. They were translated using > the same guidelines as the previous IBM contributions. While they are > professionally done and well tested, they have not been written to conform > to OpenStack community guidelines. It's likely any issues that existed in > the previous IBM translations will exist with these as well. Personally I was disappointed significantly with this. I am feeling that my effort to review Japanese IBM translations in Liberty cycle should not be done. I and some reviewers spent not small amount of time to review them because we believe our comments will be feedback-ed to Mitaka translations, but it turns out that it wasted the time. Regarding Japanese translations, the contributed translations did not have the enough quality that we could release them as-is from various points. * Not a small number of terminologies used were not natural to experienced OpenStack operators, * Strings were translated but it seems actual context where strings were used were not checked, especially substitutions (like %s, %(xxx)s), * There are many inconsistency with the existing team guidelines. (I have various experiences of translating Japanese certification exam for IT engineers and I believe I know what quality is ready for such purposes) We left many comments in Zanata but they are not referred at all.............. We, at least me, made these comments to share our guidelines..... In addition, Japanese translation team provides a lot of information including our glossary, contact points, discussion channels through OpenStack wiki page, but it does not work so far.... I will stop writing my feeling here. > I agree this is not a good long term way to complete translations. I'm not > sure if you are aware, but our Italian translation center has completed a > pilot of working directly in Zanata. Notice the high completion percentage > for Horizon Italian. I expect to have broader participation in this area > during the translation of Mitaka. It depends on the progress of translations of each language and I hope it works well. In addition, growing translation community is a good thing in the longer term. > We would like to contribute these translations to help with the OpenStack > translation effort. I understand that because they were not translated with > the same guidelines they may instead be burdensome to the translators. I > believe this is the purpose of creating the branch for offline translations: > so that language coordinators can evaluate if the translations are actually > beneficial to our OpenStack translation efforts, or if they are inconsistent > with the language's guidelines and more trouble than they are worth. I > certainly understand that creating and populating a branch does not mean > that these translations will actually be accepted. For Mitaka translation contribution, I don't have a strong opinion and either option is okay to me. If we talk about only Japanese translations of Mitaka release, server translations do not affect GUI translations (and CLI translation if any). According to our survey in Japan, most of all operators prefer to English messages. Considering these situations, I think Japanese translations of server projects can be shipped as-is without reviews. We can discuss the translation guidelines for Nxxx release translations to address inconsistencies and mismatches. > I'd like to have the branch created so that the review can take place. What > do you think? As mentioned above, I am okay with either decision. I am just concerned and disappointed with the fact that all translation efforts are being done completely separately and hope it never happens. Akihiro > > Doug > > > ----- Original message ----- > From: Akihiro Motoki <amotoki(a)gmail.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] IBM translations to contribute > Date: Mon, Jan 11, 2016 11:09 PM > > Hi Doug, > > Thanks for continuing the effort. > > I have two questions. > > First, why do we need to use a branch again. > We already set up the translation platform and IBM team can translate > on Zanata directly > as we discussed in Liberty cycle. There is no reason to use a branch > and push translation bursty again. > > Second, is existing community translation guideline per language team > honored in the contributed translations? > When talking about Japanese, we saw a lot of different translation > guidelines on wording in the last IBM translation contributed in > Liberty. > As a reviewer, we don't want to comment the same thing again. > After we Japanese review team reviewed Liberty contribution from IBM, > we don't receive any feedback/response/discussion from IBM team, > so I am afraid we need to do the similar again. It need to be avoided. > Otherwise reviewers will lose their energy. > Could you comment on the situation? > > Thanks, > Akihiro > > > 2016-01-12 12:54 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: >> We have translations to contribute for languages >> de es fr it ja ko_KR pt_BR ru zh_CN zh_TW >> for ceilometer, cinder, glance, keystone, neutron, and nova >> >> These are additional translations performed by the same teams that >> translated our previous contributions. They have been reviewed and tested. >> I >> estimate up to 35K messages will be contributed across the 10 languages >> and >> 6 components. >> >> Following the process outlined here >> >> http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001388.h… >> I am requesting that a branch be created in Zanata to facilitate review of >> these translations by the language coordinators. >> >> Thanks >> >> Doug >> >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > > > >

6 7

Fwd: [openstack-dev] [all][i18n] Rework of translation setup
by Andreas Jaeger 28 Jan '16

28 Jan '16

FYI, I'll copy resources around for python-* and oslo.* projects, Andreas -------- Forwarded Message -------- Subject: [openstack-dev] [all][i18n] Rework of translation setup Date: Thu, 28 Jan 2016 13:13:50 +0100 From: Andreas Jaeger <aj(a)microfocus.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard, Graham Norton , HRB 21284 (AG Nuernberg) To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Projects that want to setup translations for their repositories run into a few common problems and we're addressing these now to make the setup for everybody easier. The problems they run into came from limitations of the current infra scripts, so we rework the infra scripts. We want to have a simple and consistent setup for translations - with a sensible consistency. Right now it’s consistent for python projects but not sensible in some cases. See here for the full spec: http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_se… We're working basically on two major changes: a) The same setup for django projects. b) Locate files for python projects in a better place. b) only affects olso.* and python-*client projects: We need to update setup.cfg, your i18n file and move the files from $reponame/locale/$reponame.pot to $modulename/locale/modulename.pot - so placing it in your source directory and not besides it. While we move files around, we also stopped syncing of translations for olso* and python-client projects. So, please review these changes quickly and merge them. For a) we will review each django project and send patches for them as well. Also, we make our scripts more robust - and will document this properly. If you have any questions, please reach out to us. We hope that this will make translation setup for projects easier, Akihiro Motoki & Andreas Jaeger -- 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 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- 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

Re: [Openstack-i18n] IRC meeting today
by Jeremy Stanley 22 Jan '16

22 Jan '16

On 2016-01-22 14:17:23 +0800 (+0800), Ying Chun Guo wrote: [...] > Zanata has API to query translators activities. [...] Oh, that's excellent news! Maybe the update I heard we were still needing was so that we could let non-administrators query that? > Adding them to "extra ATCs" is a way. > Are there any other options to grant them the election rights ? At the moment you'll need to continue updating the extra-atcs list. The tool which queries our contributors in Gerrit could be extended to also query Zanata, but I haven't even seen the API documentation for that yet so I can't gauge how long it would take me to integrate into what I have. Longer term, of course we want this data source automatically integrated with our contributor listing tools. For the curious, https://review.openstack.org/263971 is the current state of development on the new framework I'm using for determining electoral rolls and qualifiers for contributor summit codes. -- Jeremy Stanley

1 0

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 14 Jan '16

14 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

Re: [Openstack-i18n] Czech translation error
by Akihiro Motoki 08 Jan '16

08 Jan '16

I am not sure it is a bug of the source string. It works as the source language. The similar example is shown in the gettext documentation I quoted in the first mail. Apart from the warning you mentioned, after we change msgstr[0] to contain %s in a translation, the error disappears. IMHO, it is a bug of GNU gettext. On the other hand, I agree it is less confusing if the source string contains %s. Feel free to file a bug to horizon with a background. Akihiro 2016-01-07 18:19 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > It is a bug in the source code, isn't it ? > I don't see the translations are wrong. > > msgid is "Instance launched." > We cannot simply add %s to msgstr[0]. > Zanata will report a warning: Unexpected variable: %s > > I think the source string "Instance launched." should add %s firstly. > "Instance launched." should be changed to "Instance %s launched." > And then, the translation msgstr[0] should add %s correspondingly. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/07 01:44:42: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/01/07 01:46 >> Subject: [Openstack-i18n] Czech translation error > >> >> Hi Czech language team and i18n Zanata admin, >> >> Horizon translation import is broken due to Czech translation. >> This blocks all translation imports of horizon. >> Could you fix it? >> >> https://review.openstack.org/#/c/259677 >> >> The error is like this: >> http://logs.openstack.org/77/259677/15/check/gate-horizon-dsvm- >> integration/e5ed03e/logs/devstacklog.txt.gz#_2016-01-02_17_55_04_608 >> 2016-01-02 17:55:04.608 | CommandError: Execution of msgfmt failed: >> /opt/stack/new/horizon/openstack_dashboard/locale/cs/LC_MESSAGES/ >> djangojs.po:655: >> number of format specifications in 'msgid_plural' and 'msgstr[0]' does >> not match >> 2016-01-02 17:55:04.608 | msgfmt: found 1 fatal error >> >> The error point is: >> https://review.openstack.org/#/c/259677/15/openstack_dashboard/ >> locale/cs/LC_MESSAGES/djangojs.po >> >> I think we need to add %s to msgstr[0] to avoid msgfmt error. >> >> #, python-format >> msgid "Instance launched." >> msgid_plural "%s instances launched." >> msgstr[0] "Instance spuštěna. >> msgstr[1] "Spuštěny %s instance." >> msgstr[2] "Spuštěno %s instancí." >> >> >> BTW, I am not sure this is valid according to GNU gettext documentation >> [1], >> but msgfmt actually does not support this form. >> In the example of [1], msgid does not contain %s but all msgstr[n] contain >> %s. >> Although there is no explicit description, %s must be contained in all >> msgstr[n]. >> To avoid confusion, it is better to contain %s in 'msgid' (singular >> form) as well. >> >> [1] https://www.gnu.org/software/gettext/manual/html_node/ >> Translating-plural-forms.html >> >> >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >

3 2

Czech translation error
by Akihiro Motoki 07 Jan '16

07 Jan '16

Hi Czech language team and i18n Zanata admin, Horizon translation import is broken due to Czech translation. This blocks all translation imports of horizon. Could you fix it? https://review.openstack.org/#/c/259677 The error is like this: http://logs.openstack.org/77/259677/15/check/gate-horizon-dsvm-integration/… 2016-01-02 17:55:04.608 | CommandError: Execution of msgfmt failed: /opt/stack/new/horizon/openstack_dashboard/locale/cs/LC_MESSAGES/djangojs.po:655: number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match 2016-01-02 17:55:04.608 | msgfmt: found 1 fatal error The error point is: https://review.openstack.org/#/c/259677/15/openstack_dashboard/locale/cs/LC… I think we need to add %s to msgstr[0] to avoid msgfmt error. #, python-format msgid "Instance launched." msgid_plural "%s instances launched." msgstr[0] "Instance spuštěna. msgstr[1] "Spuštěny %s instance." msgstr[2] "Spuštěno %s instancí." BTW, I am not sure this is valid according to GNU gettext documentation [1], but msgfmt actually does not support this form. In the example of [1], msgid does not contain %s but all msgstr[n] contain %s. Although there is no explicit description, %s must be contained in all msgstr[n]. To avoid confusion, it is better to contain %s in 'msgid' (singular form) as well. [1] https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-fo… Akihiro

4 4

IRC meeting today
by Ying Chun Guo 07 Jan '16

07 Jan '16

Hello, team I hope you had a good new year holiday. We will have our first IRC meeting in 2016 today, at 0600UTC in #openstack-meeting. I'm going to cover following topics: * Glossary management process discussion * Open discussions Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

2 1

Re: [Openstack-i18n] How do we manage glossary?
by Kato, Tomoyuki 06 Jan '16

06 Jan '16

> >> 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. I'm not fully contexted, but generally agree to 'post' pipeline idea. KATO Tomoyuki

1 0

Fw: [OpenStack-docs] Travel support for Summit, April 25-29, Austin, TX
by Ying Chun Guo 05 Jan '16

05 Jan '16

Hi, team If you need the travel support for Austin Summit, you could apply now. Best regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2016/01/05 17:01 ----- Anne Gentle <annegentle(a)justwriteclick.com> wrote on 2016/01/05 01:43:00: > From: Anne Gentle <annegentle(a)justwriteclick.com> > To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org> > Date: 2016/01/05 01:45 > Subject: [OpenStack-docs] Travel support for Summit, April 25-29, Austin, TX > > Hi all, > Want to be sure that documentarians know about the travel support > program to get contributors to the Summit. Read all about it and apply here: > > https://www.openstack.org/summit/austin-2016/austin-and-travel/#travel-supp… > > Thanks, > Anne > > -- > Anne Gentle > Rackspace > Principal Engineer > www.justwriteclick.com_______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

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

05 Jan '16

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 translation po 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 >> >

2 1

Re: [Openstack-i18n] Transifex
by Ian Y. Choi 23 Dec '15

23 Dec '15

Hello Daisy, Thank you so much for your kind explanation. I agree that all of translation data are successfully moved to Zanata, and I have no objection to remove current Transifex not to be confused for OpenStack translation contributor candidates. I just worried that some guys might want to see previous Transifex history: who contributed to OpenStack translations later, since, the author of translation results from Transifex to Zanata is "OpenStack Infra", not actual translators, as far as I know. However, I also think that it is very difficult to keep all the history to public. For my OpenStack translation stuff, I do not need Transifex any more. So if other translators also do not need to see to track previous translators in Transifex, then there is no more additional reason to remove Transifex except querying statistics. And one more idea: although some previous translators are not regarded as ATC, I think it would be much better to mention their Transifex ID (at least) to acknowledge their previous contribution or credit on somewhere, such as OpenStack wiki. Let's discuss on today IRC meeting :) With many thanks, /Ian Ying Chun Guo wrote on 12/17/2015 2:39 PM: > > Ian Y, > > I will not use the official i18n repo to store those materials. > I plan to store it in a personal repo in github, > just to keep the history. > > We have moved all data into Zanata while we migrated to Zanata in > September. > 4 months passed, we didn't get any complains about any missing data. > We could be sure that all data have been moved to the new tool. > So it's not that necessary to back up. > > The only reason to support to not delete OpenStack from Transifex is that: > it's easy to query the contribution data in any certain period through > the web UI of Transifex. > If we remove OpenStack from Transifex, we will lost the ability to query. > I could export the contribution data for a certain period, for > example, the last 3 years, from Transifex, > and store the export data somewhere. > But I will lost the ability to query any periods, for example, the > data from 2015.4-2015.10 will not be able to get. > > So we could discuss whether we need this ability in the meeting today. > If we don't need, Transifex is no use for us. We could delete it safely. > > Best regards > Ying Chun Guo (Daisy) > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/12/17 12:21:34: > > > From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN, Andreas Jaeger <aj(a)suse.com> > > Cc: Robert Simai <robert.simai(a)suse.com>, > openstack-i18n(a)lists.openstack.org > > Date: 2015/12/17 12:22 > > Subject: Re: [Openstack-i18n] Transifex > > > > Hello Andreas, > > > > I am copying & pasting from Andreas's comment to this thread: > > > > +++ > > "Sorry, let me clarify this again: > > * ATC is one year (voting rights for i18n) > > * Free passes for OpenStack conference is 6 months > > > > For ATC, you could take a one time snapshot as well now - going back > > to 1st of April, instead of saving it for later," > > > > > > => Thank you so much for your nice clarification on ATC status and > > summit free passes. > > > > We would vote this issue (removing on Transifex site) on today's IRC > > meeting, and yes. > > We need contribution statistics data from Transifex, and I agree that > > we can query and save Transifex statistics data (from April 1 2015 > > to now) and later > > we would merge this data with Zanata statistics data on next April. > > > > And I am not sure exactly, but we might use openstack/i18n repo to > > store Transfex related data > > into a specific branch, not a master branch. > > > > > > With many thanks, > > > > /Ian > > > > > > Ying Chun Guo wrote on 12/17/2015 1:21 AM: > > If we don't need the contribution data in Transifex, I think we > > could remove it. > > > > As to the back up, it's a personal habit. I just want to keep it as > > the history. > > I will use a repo in github to store the documents, including an > > Excel file with the contribution statistic data. > > > > Best regards > > Ying Chun Guo (Daisy) > > > > > > -----Andreas Jaeger <aj(a)suse.com> wrote: ----- > > > > >To: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Robert Simai > > ><robert.simai(a)suse.com> > > >From: Andreas Jaeger <aj(a)suse.com> > > >Date: 12/16/2015 09:59PM > > >Cc: openstack-i18n(a)lists.openstack.org > > >Subject: Re: [Openstack-i18n] Transifex > > > > > >On 2015-12-16 14:45, Andreas Jaeger wrote: > > >> On 2015-12-16 14:34, Ian Y. Choi wrote: > > >>> Hello Robert, > > >>> > > >>> As far as I remember, on the last i18n irc meeting (Dec 03 2015 +6 > > >UTC), > > >>> we discussed this issue. > > >>> > > >>> During the meeting, meeting attendees found that querying to > > >Transifex > > >>> statistics data > > >>> is needed to check ATC status for the next OpenStack release, > > >Mitaka. > > >> > > >> ATC status is handed out only for people active in the current > > >release, > > >> so for the next summit in Austin, only for people that were active > > >in > > >> Mitaka time frame. And since we used Zanata for all of Mitaka, > > >there's > > >> no need to query transifex IMO. > > >> > > >> Katamo is wrong with ATC status for one year, this has changed, > > > > > >See > > >https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstac > > >k-summit/ > > >with information for Tokyo summit (1st of April was cut-off-date), > > > > > >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 > > > > > > > > >_______________________________________________ > > >Openstack-i18n mailing list > > >Openstack-i18n(a)lists.openstack.org > > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > > > >

5 5

How do we manage glossary?
by Akihiro Motoki 17 Dec '15

17 Dec '15

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

2 1

Re: [Openstack-i18n] Transifex
by Ian Y. Choi 17 Dec '15

17 Dec '15

Hello Andreas, I am copying & pasting from Andreas's comment to this thread: +++ "Sorry, let me clarify this again: * ATC is one year (voting rights for i18n) * Free passes for OpenStack conference is 6 months For ATC, you could take a one time snapshot as well now - going back to 1st of April, instead of saving it for later," => Thank you so much for your nice clarification on ATC status and summit free passes. We would vote this issue (removing on Transifex site) on today's IRC meeting, and yes. We need contribution statistics data from Transifex, and I agree that we can query and save Transifex statistics data (from April 1 2015 to now) and later we would merge this data with Zanata statistics data on next April. And I am not sure exactly, but we might use openstack/i18n repo to store Transfex related data into a specific branch, not a master branch. With many thanks, /Ian Ying Chun Guo wrote on 12/17/2015 1:21 AM: > If we don't need the contribution data in Transifex, I think we could > remove it. > > As to the back up, it's a personal habit. I just want to keep it as > the history. > I will use a repo in github to store the documents, including an Excel > file with the contribution statistic data. > > Best regards > Ying Chun Guo (Daisy) > > > -----Andreas Jaeger <aj(a)suse.com <mailto:aj@suse.com>> wrote: ----- > > >To: "Ian Y. Choi" <ianyrchoi(a)gmail.com <mailto:ianyrchoi@gmail.com>>, > Robert Simai > ><robert.simai(a)suse.com <mailto:robert.simai@suse.com>> > >From: Andreas Jaeger <aj(a)suse.com <mailto:aj@suse.com>> > >Date: 12/16/2015 09:59PM > >Cc: openstack-i18n(a)lists.openstack.org > <mailto:openstack-i18n@lists.openstack.org> > >Subject: Re: [Openstack-i18n] Transifex > > > >On 2015-12-16 14:45, Andreas Jaeger wrote: > >> On 2015-12-16 14:34, Ian Y. Choi wrote: > >>> Hello Robert, > >>> > >>> As far as I remember, on the last i18n irc meeting (Dec 03 2015 +6 > >UTC), > >>> we discussed this issue. > >>> > >>> During the meeting, meeting attendees found that querying to > >Transifex > >>> statistics data > >>> is needed to check ATC status for the next OpenStack release, > >Mitaka. > >> > >> ATC status is handed out only for people active in the current > >release, > >> so for the next summit in Austin, only for people that were active > >in > >> Mitaka time frame. And since we used Zanata for all of Mitaka, > >there's > >> no need to query transifex IMO. > >> > >> Katamo is wrong with ATC status for one year, this has changed, > > > >See > >https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstac > >k-summit/ > >with information for Tokyo summit (1st of April was cut-off-date), > > > >Andreas > >-- > > Andreas Jaeger aj(a){suse.com <mailto:aj@%7Bsuse.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 > > > > > >_______________________________________________ > >Openstack-i18n mailing list > >Openstack-i18n(a)lists.openstack.org > <mailto:Openstack-i18n@lists.openstack.org> > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > >

2 1

IRC meeting today
by Ying Chun Guo 17 Dec '15

17 Dec '15

Hi, team We will have IRC meeting today, at 1300UTC in #openstack-meeting. I'm going to cover following topics. * Status update: Liberty installation guide translation * Discussion: Midcycle spring/virtual spring * Vote: delete OpenStack from Transifex * Open discussions Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

1 0

Transifex
by Ying Chun Guo 16 Dec '15

16 Dec '15

Hello, team I have handled all the team join requests to OpenStack in Transifex, sending emails to inform the tool change and then rejecting them. I noticed there was no translations happened in Transifex after Oct. I think we could start to remove Openstack projects from Transifex. We may find a place to back up firstly, and then remove. Any objections to the remove ? Any suggestions about the back up ? Best regards Ying Chun Guo (Daisy)

4 6

How to set accept language tag to Dutch (nl) in OpenStack Tempest test framework?
by durga rao 15 Dec '15

15 Dec '15

I have latest tempest downloaded from GitHub.Here is my test requirement:We have a set of test scripts for compute, storage and network. For all the REST calls made by tempest test framework, I want to set the "Accept Language" tag to Dutch [nl] (Netherlands Dutch).It might just be one configuration file change. I want to know the configuration file that needs to be changed.Quick response is appreciated.Thank you

1 0

What's Up, Doc? Holiday Edition
by Lana Brindley 11 Dec '15

11 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This is my final newsletter for the year, as I'm taking summer vacation over the next few weeks (yay for Southern Hemisphere weather!). Your regularly scheduled programming will resume in mid-January. I would like to take a moment to acknowledge the incredible work of the entire documentation team, especially the core team who have worked all year to keep on top of reviews, the speciality team leads who motivate and inspire their teams each and every day, and every single documentation contributor and reviewer: without you all doing your little bit, we wouldn't have had the success we have had. Thank you also to our crew of support people: from infra and release management, to our subject matter experts and the wonderful people on the TC and at Foundation. Thanks for helping us be the best we can be. I would also like to make special mention of Andreas Jaeger and Anne Gentle, who both continue to hold my hand daily and make sure I don't make too much of a fool of myself in public. Your support and encouragement have been invaluable. While we're on the goodwill wagon: if there's someone (or something!) you would like to call out for a special mention, you can do so using #success in our IRC channel. All successes get logged here: https://wiki.openstack.org/wiki/Successes and it's a great way to show your appreciation for your fellow community members. == Progress towards Mitaka == 117 days to go! 150 bugs closed so far for this release. RST Conversions * Arch Guide ** RST conversion is complete! Well done Shilla and team for getting this done so incredibly quickly :) * Config Ref ** Is underway: contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** Is complete! Well done Tomoyuki-san :) Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Doc sprint planned for December 21-22. Contact the Ops Guide speciality team for more info or to get involved. ** 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 * Waiting to merge the patch for the new Jenkins job: https://review.openstack.org/#/c/251301/ which for now will be against Nova only so we can make sure it's working correctly before we roll it out across the board. Document openstack-doc-tools and reorganise index page * Thanks to Brian and Christian for volunteering to take this on! Horizon UX work * Thanks to the people who offered to help out on this! If you're interested but haven't gotten in touch yet, contact Piet Kruithof of the UX team. There is now a blueprint + spec in draft: https://blueprints.launchpad.net/openstack-manuals/+spec/ui-content-guideli… and https://review.openstack.org/#/c/252668/ == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' The change to shift IRC meeting was not accepted. Going to create a new poll this time with correct options suggested by Tony Breeds. No more updates. '''Installation Guide - Christian Berendt''' We require Debian Install Guide testers. Please contact Christian if you're interested. '''Networking Guide - Edgar Magana''' The networking guide had its first official IRC meeting: https://wiki.openstack.org/wiki/Documentation/NetworkingGuideMeetings We are restructuring a little bit the wikis for better engagement with new contributors; Versioning spec for networking guide has been merged: https://review.openstack.org/#/c/253283/ Working of the remaining actions items from the meeting: http://eavesdrop.openstack.org/meetings/networking_guide/2015/networking_gu… We have proposed a time and date for an IRC meeting covering APAC time zone: https://review.openstack.org/#/c/254999/ '''Security Guide - Nathaniel Dillon''' Planning for a bug sprint and general triage/cleanup. '''User Guides - Joseph Robinson''' The User Guide Reorganization Spec merged this week, and the final User Guide meeting for 2016 has been rescheduled to next Thursday December 16 at 23:30 UTC, and the plan is to discuss work items. A patch for the User Guide Dashboard has begun using the blueprint implementation as a start to the reorg. '''Ops and Arch Guides - Shilla Saebi''' Regarding this spec - https://review.openstack.org/#/c/227660/, we decided we are going to hold off until the N-release; Architecture Guide Swarm - Asking for everyone who wants to help to please use the https://etherpad.openstack.org/p/arch-guide-reorg to document potential changes; The arch guide RST conversion is complete; For the swarm, everyone works in their timezone. They will then submit patches and allocate team members in the other timezones to review; The final dates for the arch guide virtual swarm is: 12/21-12/22. '''API Docs - Anne Gentle''' Trimming down what is output so that eventually we'll get working Swagger migrated from WADL. Repo still awaits being pulled into gerrit: https://github.com/russell/fairy-slipper to https://review.openstack.org/#/c/245352/ Nova API docs sprint 12/8 and 12/9 came up with good questions and answers and patches. Also, the Gabbi API test suite has a new release, see http://lists.openstack.org/pipermail/openstack-dev/2015-December/081891.html '''Config Ref - Gauvain Pocentek''' The configuration reference RST migration is almost done, only a few more Block Storage drivers docs to handle. Thanks to all the contributors! '''Training labs - Roger Luethi''' Training-labs merged a KVM provider patch which allows the training cluster to build on top of KVM. The IP address ranges now match the install guides. The Liberty training cluster is being worked on. '''Training Guides - Matjaz Pancur''' Through no fault of Matjaz', this report was erroneously left out of the last newsletter, sorry for the delay: A complete Korean translation of the Upstream training material is officially published at http://docs.openstack.org/ko_KR/upstream-training/ (big thanks to Ian Y. Choi and KATO Tomoyuki) '''Hyperviser Tuning Guide - Joe Topjian''' Finished the first pass of converting etherpad notes to the wiki. I sent an email <http://lists.openstack.org/pipermail/openstack-operators/2015-December/0091…> to the openstack-operators with a summary of the current state. Hopefully the guide will pick up two or three regular contributors to help things along. I'll continue to work on it 1-2 hours a week as I get time. == 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 == We failed to hold the APAC docs meeting this week because I can't read a calendar, and clearly just need a holiday. My apologies! Next meetings: US: Wednesday 16 December, 14:00 UTC APAC: Will resume in the new year Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- Happy holidays everyone, and remember to ... 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/ iQEcBAEBCAAGBQJWaj4RAAoJELppzVb4+KUyFoAH/jVqenzze6Pl6xF68dKBwouT ij8j80wBMdbUzyn4zc4726uxQ1TMdzXgK+8Q8Ouk4fOewn6cV9rOZJelpSPSboOR Lv4mjm172UxqnrN1npy5f9tB9EnIC/R8N0KlZHJmD0YJ/EbiJ0Hv/wl4/6+f8L7D Ns6iIUylI62a/ycIs7Wz5RGASaMZpZaP1XEeQtUoXbpIHggTlxPcHgETayHVnBMl 5qIuG5B5fgIOdUKQAa41SuMRCttxyHStXCFM/lborpDd6vEbMR2S/UbJb+7zh0jK PIACfhsnnZCBiZqno9NFnxBehdqTXpDG3crG0I9Ajd2YnEdhmFro+jMQr56lkGE= =1Kk+ -----END PGP SIGNATURE-----

1 0

What's Up, Doc? 4 December 2015
by Lana Brindley 09 Dec '15

09 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Slight delay in the newsletter this time around, it's been a busy week! I've been working on the DocImpact changes, reviewing the docs and docs-specs core teams, and catching up with blueprint management and reviews from while I was on leave. Since we're getting to the pointy end of the year, remember to call out successes using #success in our IRC channel. All successes get logged here: https://wiki.openstack.org/wiki/Successes and it's a great way to show your appreciation for your fellow community members. == Progress towards Mitaka == 121 days to go! 139 bugs closed so far for this release. RST Conversions * Arch Guide ** RST conversion is complete! Well done Shilla and team for getting this done so incredibly quickly :) * Config Ref ** Contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/image-guide-rst and https://review.openstack.org/#/c/244598/ Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Doc sprint in planning for December 21-22. Contact the Ops Guide speciality team for more info or to get involved. ** 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 * This is now well underway, with the first two patches merged. One changes the default bug queue for DocImpact back to the projects' own queue, and the other changes all current projects (with the exception of the six defcore projects) to their own bug queue. There has also been some discussion on the mailing lists about this process change. The next step is to merge the new Jenkins job (https://review.openstack.org/#/c/251301/) which for now will be against Nova only so we can make sure it's working correctly before we roll it out across the board. Thank you to Andreas, Josh Hesketh, and everyone else who has helped get us this far, and to the Nova team who are allowing us to use them as guinea pigs. Document openstack-doc-tools and reorganise index page * Thanks to Brian and Christian for volunteering to take this on! Horizon UX work * Thanks to the people who offered to help out on this! If you're interested but haven't gotten in touch yet, contact Piet Kruithof of the UX team. There is now a blueprint + spec in draft: https://blueprints.launchpad.net/openstack-manuals/+spec/ui-content-guideli… and https://review.openstack.org/#/c/252668/ == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Finished IRC meeting schedule poll, finalised the Corosync/pacemaker patch (https://review.openstack.org/235893) participating and tracking progress with the HA for OpenStack instances research (https://etherpad.openstack.org/p/automatic-evacuation) to make it into the HA guide, eventually. '''Installation Guide - Christian Berendt''' Debian install guide nearly completed, testers needed; meeting time for the EU/US meeting will probably change from 13 UTC to 17 UTC; Aodh install instructions nearly finished, ongoing discussion because of missing SUSE packages; Japanese translation of the Liberty install guide published. '''Networking Guide - Edgar Magana''' We are having our first official IRC meeting tomorrow at 1600 UTC. The goal is to find out what we can to complete during the Liberty cycle and have specific tasks assigned. Relevant patches: Create tags for the Networking Guide - WIP (https://review.openstack.org/#/c/251979/) '''Security Guide - Nathaniel Dillon''' No update this week '''User Guides - Joseph Robinson''' The User guide meeting on IRC worked, however attendance was down; the reorganization spec is updated with information from Big Tent Project navigator to define the scope (http://www.openstack.org/software/project-navigator) and information from the published nova-network to neutron migration study. '''Ops and Arch Guides - Darren Chan''' The arch guide RST conversion is completed. We plan on doing a virtual swarm this December. The doodle link was sent out last week and the poll is now closed. The final date for the virtual swarm is: 12/21-12/22. '''API Docs - Anne Gentle''' Working on usage docs for migration, how to build, what gets migrated, how the docs are assembled: https://github.com/russell/fairy-slipper/blob/master/doc/source/usage.rst Responding to spec reviews: https://review.openstack.org/#/c/246660/ Revising patch to bring fairy-slipper into openstack org: https://review.openstack.org/#/c/245352/ '''Config Ref - Gauvain Pocentek''' The RST migration is still in progress. The Manila section has been greatly improved in the process, and the Zaqar documentation should land during this cycle as the spec has been approved. '''Training labs - Pranav Salunke''' KVM port is almost done. Planned to merge this by end of this week; Network configuration for the cluster is updated. Now it uses same network addresses as install guides; Welcome berndbausch into our team; Liberty port is in progress. Follow https://etherpad.openstack.org/p/training-labs-liberty for more details; Need to decide meeting time for weekly IRC meetings. '''Training Guides - Matjaz Pancur''' No update this week '''Hyperviser Tuning Guide - Joe Topjian''' Still on schedule. Halfway done with a first-pass cleanup. Should be ready for open contributions within 2 weeks. == Core Team Changes == During last week, I announced some changes to the docs-specs core team. Previously, this core team was a small subset of docs core team members, with an understanding that we would wait for speciality team leads to +1 a spec relevant to their team before approving. Now we have formalised that process by inviting each speciality team lead to the docs-specs core team, so that they can +2A their own specs. Speciality team leads are listed on the wiki here: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams remember to engage them when you create a new spec for approval. We have also reviewed the current docs core team list for December, and the results of that will be announced shortly. We will not be reviewing the team in January because of the holiday period, and will resume regular reviews in February 2016. == Doc team meeting == We held the APAC docs meeting this week. Big thanks to Joseph for running that while I was away, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-11-25 Next meetings: US: Wednesday 9 December, 14:00 UTC APAC: Wednesday 16 December, 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… - -- Just a note that this will be my penultimate newsletter for 2015. 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/ iQEcBAEBCAAGBQJWZPzNAAoJELppzVb4+KUyT+IH/0yFFN5+X1WG5mbq+SUK0DnP av+pdcVbIlVpSuVgI5rV69ri3TwnU9DmFyJfOcx7h3ZRib3ri3T09UQ7L4A/EvfL Ar+AzG0OLriSLz1WJEVhg8VYkVuxVugIfAUvrKyNPIQs9sbDHQfmnpYoyZ8LB/TK tXd6+R15yMt+2KOPfKT2UMj8NUhf+XYxEpuW8TCTNss3GWlQZBHy9USNFfat+rzY MaLpUGGG6dviKgWGStGOD4I2JUIswobqFRdOKJ0a3h7vDEPeJMkr+OHDG3wzNMx7 n2TL5jAf2teIoys0sLP7qVRBD/c4cQHIGi0C70iWlqSrbG80yq27Prc0cJrl/VA= =rNRL -----END PGP SIGNATURE-----

1 1

Chinese (zh_CN) translations are broken
by Andreas Jaeger 07 Dec '15

07 Dec '15

The import of openstack-manuals for zh_CN fails: On liberty for doc/common-rst/source/locale/common-rst On stable for install-guide In both cases, there's a Backspace character in there (0x08 Unicode). I'm removing all these backspaces now and ask the translators to be careful, 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 7

CLI Reference translations
by Andreas Jaeger 06 Dec '15

06 Dec '15

Hi The CLI reference is autogenerated from the output of our command line clients and currently has no translations, I suggest to not translate it at all and have proposed a change to do so. It currently is just a lot of noise in openstack-manuals with the source pot files whenever we do an update (see https://review.openstack.org/#/c/253794/) If there's interest later to translate the CLI reference, we can enable it again, Andreas Change: https://review.openstack.org/253803 -- 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

3 2

Re: [Openstack-i18n] Chinese (zh_CN) translations are broken
by Andreas Jaeger 04 Dec '15

04 Dec '15

On 2015-12-04 10:32, Ying Chun Guo wrote: > I have connected with the translator and he has found the problem. > He said it was caused by the input method. > He has solved the problem. > > Thank you Andreas for the information. Thanks, Daisy! Everything looks fine now, 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

Install Guide translation
by KATO Tomoyuki 04 Dec '15

04 Dec '15

Hi team, especially Czech member, Just a reminder. As mentioned a days ago, the translation resource of Install Guide for Liberty is "stable-liberty" version at Zanata. "master" version is a draft for Mitaka. Also, to be honest, the guide may be heavily rewrited for Mitaka. Regards, KATO Tomoyuki > On 2015-11-17 10:49, Ying Chun Guo wrote: > > Hi, Andreas > > > > I see stable/liberty is created in the repo of openstack-manuals, > > and stable-liberty version is created for openstack-manuals project in > > Zanata. > > Thank you for handling these. > > > > Is the installation guide in the master branch keeping open for Mitaka > > release? > > Yes. > > > So in order to translate Liberty installation guide, our translators should > > go to stable-liberty and work there. > > Correct. > > > I have changed the link of openstack manuals in the home page > > translation plan > > to stable-liberty version. > > Correct me if I'm wrong. > > Looks fine > > Andreas

1 0

Re: [Openstack-i18n] Chinese (zh_CN) translations are broken
by Andreas Jaeger 03 Dec '15

03 Dec '15

On 2015-12-03 09:43, Ying Chun Guo wrote: > Thank you, Andreas. > > Could you tell me what are source strings of the bad translations? > I will take a look and investigate the history. For liberty, it was all strings of the form "`Bugs: OpenStack Block Storage (cinder) <https://bugs.launchpad.net/cinder>`__" 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

3 2

Re: [Openstack-i18n] [OpenStack-docs] Usage of custom RST directives
by Lana Brindley 03 Dec '15

03 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 How will it impact translation? L On 02/12/15 23:21, Mariia Zlatkova wrote: >> >> At the moment I am not sure if I like it or not. But I think the usage of >> custom RST directives should be discussed on the list and if we decide to >> use custom RST directives they should be documented in the contributor >> guide. >> > > I think it makes sense to add this directive to the Contributor Guide (not > to copy and paste files to the repository and then update them manually). > > Maria > > On Wed, Dec 2, 2015 at 2:45 PM, Olena Logvinova <ologvinova(a)mirantis.com> > wrote: > >> At the moment I am not sure if I like it or not. But I think the >>> usage of custom RST directives should be discussed on the list and if >>> we decide to use custom RST directives they should be documented in >>> the contributor guide. >> >> >> I like the way a document looks like if we use this directive - it becomes >> smaller and, therefore, looks nicer. =) >> So I vote for adding this directive to the Contributor Guide conventions. >> >> Thanks >> Olena >> >> On Wed, Dec 2, 2015 at 1:17 PM, Gauvain Pocentek < >> gauvain.pocentek(a)objectif-libre.com> wrote: >> >>> Le 2015-12-02 11:31, Christian Berendt a écrit : >>> >>>> Hello everybody. >>>> >>>> While reviewing a review request for the new config-rst-guide I saw >>>> the usage of the RST directive "remote-code-block". I never saw this >>>> directive before and after searching for the definition I only found >>>> >>>> https://github.com/openstack/openstack-manuals/blob/master/doc/config-ref-r… >>>> . >>>> >>> >>> This particular directive tries to reproduce the docbook <xi:include> >>> behaviour, to avoid adding loads of sample file in our tree. I'm guilty of >>> adding it to the config-ref-rst folder. >>> >>> >>>> At the moment I am not sure if I like it or not. But I think the >>>> usage of custom RST directives should be discussed on the list and if >>>> we decide to use custom RST directives they should be documented in >>>> the contributor guide. >>>> >>> >>> Agreed. To be honnest I planned to write to the ML but it just slipped my >>> mind. >>> >>> >>> Gauvain Pocentek >>> >>> Objectif Libre - Infrastructure et Formations Linux >>> http://www.objectif-libre.com >>> >>> >>> _______________________________________________ >>> OpenStack-docs mailing list >>> OpenStack-docs(a)lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >>> >> >> >> >> -- >> Best regards, >> Olena Logvinova, >> Technical Writer | Mirantis, Kharkiv | 38, Lenin av., Kharkiv >> ologvinova(a)mirantis.com | +380950903196 >> >> _______________________________________________ >> OpenStack-docs mailing list >> OpenStack-docs(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >> >> > > > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > - -- 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/ iQEcBAEBCAAGBQJWX3PhAAoJELppzVb4+KUyD5IIAI78AYaDM00xzv1rmSyd7Pg1 3p0NrvZD2BtLPEiCq42B5DRWf2XNNnzbFGyqWvyT8ShD/94pr+5ASGceKv5t8P7H Rn0Gkc6idGKsv53ZKxWRHwizCm8mt+3VPiOQYZYhK4ghFII/mBY8kYNwnRQyyYHv rU5tdLNqOAlq36WqmVVbOUh0C3Rf3+YPs3BjcWNnnqVx11C/tPYJ5LR7oNHxW3jJ ZP0wZe9i/+6yOtH5dDxj0k4WnwXvdfXQPIAlHbpY1FvJUl8vsRMxrEe7s10AmpTS D2UybNqPg79PBdg7CUX6c72r+ASPw+LZTJeJm3vVpWY4izpmezZWt30drEUIgkU= =gnC5 -----END PGP SIGNATURE-----

2 1

IRC meeting tomorrow
by Ying Chun Guo 02 Dec '15

02 Dec '15

Hello, team We will have IRC meeting tomorrow at 0600 UTC in the IRC channel #openstack-meeting. I'm going to cover following topics tomorrow. * Discussion: Bug management process in Launchpad * Discussion: Glossary management process * Open discussions If you have more topics, please propose freely. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] [OpenStack-docs] [openstack-dev] DocImpact Changes
by Lana Brindley 02 Dec '15

02 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/12/15 12:53, Armando M. wrote: > On 24 November 2015 at 13:11, Lana Brindley <openstack(a)lanabrindley.com> > wrote: > > Hi Akihiro, > > Judging by most of the bugs we see in the openstack-manuals queue, the > bugs that will be raised in projects' own queues will usually be against > their own developer documentation. > > >> I am a bit confused. The developer documentation coexists with the code >> that's being patched. Is this the documentation you're referring to? So for >> instance in Neutron we have [1] rendered into [2]. That's correct. > >> I always assumed that DocImpact was needed to flag configuration changes, >> and more generally user facing issues, and these are not captured in the >> developer doc [2] (afaik, *-aas services do have a developer documentation >> but no entry point in [4]), as developers are not the audience, but rather >> guide [3]. On the other hand, if patches do require dev doc changes (like >> design issues etc), reviewers tend to ask to take care of them in the >> context of the same patch, without the burden of going through an extra bug >> report. I agree, and that was the original intention, however it doesn't get used that way in the majority of cases we see. Feel free to use DocImpact (with a description), and then manually flip the bug to openstack-manuals in this case. > >> So the fact that Neutron's DocImpact changes raises a bug report in LP >> Neutron seems counterintuitive, and I am a bit at loss here. Can you >> elaborate on what was the rationale for making only certain projects target >> their own queues? I wouldn't want to have bug reports be reassigned to the >> right queue only to cause more burden that this initiative originally >> intended to relieve. We chose the five 'defcore' projects here, as they are the ones that are formally (and most extensively) documented in openstack-manuals. > >> Having said that, let's assume we are stricter about what gets flagged with >> DocImpact, would you be open to revisiting the doc group for Neutron as set >> in [5]? In the meantime, I'll go ahead and look at the outstanding patches >> and bug reports recently filed to sanitize with the best of my abilities. As we noted in the original spec, we appreciate that Neutron is on the cusp of being considered 'defcore', and we're happy to include it once that has happened formally. Thanks for your help. 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/ iQEcBAEBCAAGBQJWXmDwAAoJELppzVb4+KUyezMH/3WuKrW+8Py9XU3o2vddCK4c ZovehU0Xq1mHzzpfh8Vfc71MfJVAtotr9Lt0Vd5b4jAnjSWz7QI4/W2CG3d+aM+L FYPDn9koTC/+EsXlz8ekzLQUz6PToa21jfdmcg6tSAPA09FV5j7SPWIPXD9bvzun q9NWhs3jjj4hVtgUhmFdeC7B0vDzT6EWU2kAuSWwUEf7z2c3S7ZnuteyOKLf6aLZ rRbZi59ras8/3jI9EY8h6Wk47gQ3fLwvYyL/tHU9c2jOGPPz47f7HKaXVO0MQ58p E4V3nhGEITt3NMQH8m0IEW7JLd3tRX1C7ERKK05+k5yl7dirxKsysq52xJh0EMo= =1mW1 -----END PGP SIGNATURE-----

1 0

Translation warnings (Re: [OpenStack-docs] Code block in RST and translation)
by Akihiro Motoki 01 Dec '15

01 Dec '15

2015-11-25 23:54 GMT+09:00 Andreas Jaeger <aj(a)suse.com>: > On 2015-11-25 15:48, KATO Tomoyuki wrote: >>> >>> >>>> On 25 Nov 2015, at 03:41, KATO Tomoyuki <tomo(a)dream.daynight.jp> wrote: >>>> >>>>> My idea at now is to use "code-block" directive as possible as we can, >>>> >>>> >>>> As far as I know, docs team guides mainly use "code-block". >>>> So, I'm okay to unify to "code-block" directive. >>>> >>>>> but I am not sure it is the right direction as "::" is widely used. >>>> >>>> >>>> In my understand, most of developers like “::”, which is simple RST >>>> format :) >>> >>> >>> Maybe we could add a gate check that looks for “::” in the end of the >>> strings (original and translated)? It would enable developers to use >>> whatever they are used to. >> >> >> Nice idea! Sounds good to me, as a non-vote job. >> >> Regards, >> KATO Tomoyuki > > > But who will monitor this and correct it? > > We already see warnings in translated code that everybody ignores, let's > find a good way to monitor and fix these problems first before we add > more tests... I think this kind tests are categorized into two: (a) to detect anti-patterns which are not good for translations. (b) to detect warnings when building translation documents. I have no good idea on who monitors it. (b) can be a periodic job and language translators need to check them. Related to (b) warnings in translation documents, I cleaned up warnings in Japanese translations last night. At now, Japanese documents have no warnings except https://bugs.launchpad.net/openstack-manuals/+bug/1521473. Most of them can be fixed by - adding an extra white space after closing RST markups such as `` or **, or - removing extra white spaces at beginning or end of strings wrapped by RST markups. Even with these warnings, translated documents are rendered properly. On the other hand, some warnings are actually due to translation mistakes to be fixed. This turns out that checking warnings is still important. Akihiro > > 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 > > > > _______________________________________________ > Openstack-i18n mailing list > Openstack-i18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

2 1

Upstream Training material publication
by KATO Tomoyuki 01 Dec '15

01 Dec '15

Hi team, Happily, we have new translation feature for Upstream Training material. Also, translation publication job is enabled at now. For ONLY this guide, the translated guide is published immediately. Amazingly, Korean team has almost finished translation. Congrats! http://docs.openstack.org/ko_KR/upstream-training/ Regards, KATO Tomoyuki

2 1

external reference in RST and translation
by Akihiro Motoki 27 Nov '15

27 Nov '15

Hi, It is about RST formatting and translation, again. I had a trouble in translating the following type of external references. The following style is used especially when the same reference is used multiple times. In this case, translators MUST keep an original label, in this case 'User guide' in English even if there is more appropriate string in each language. If translators translate such strings, we will get a broken external link. I don't have a good solution on this other than keep original strings at now. Any suggestions? (http://docs.openstack.org/contributor-guide/rst-conv/refs.html#external-ref…) ---- Here is an external web link separated from its definition: This paragraph contains the link to `User guide`_. ... .. format the link definition at the end of the file as follows: .. _`User guide`: http://docs.openstack.org/user-guide/ ---- Thanks, Akihiro

1 0

Code block in RST and translation
by Akihiro Motoki 27 Nov '15

27 Nov '15

Hi, According to [1], we use two types of code blocks in RST documentations. The one is to end a line with "::" [2] and the other is to use 'code-block'. During translation, I noticed the first style can be a wrong formatting in translated documents (it will be considered as "block quote" as far as I tested). It is not easy that translators understand "::" at end of line has a special meaning. To keep the format, translators MUST keep "::" at the end of line, but ":" is rarely used in some languages and I think they will forget "::" easily. In addition, it is hard to detect this kind of things during translation reviews. Note that other RST conventions are easier to be recognized as special because they are very different from usual strings. On the other hand, ending a line with "::" is a standard ReST convention and it is widely used in writing documents in ReST format. My idea at now is to use "code-block" directive as possible as we can, but I am not sure it is the right direction as "::" is widely used. Thought? Thanks, Akihiro [1] http://docs.openstack.org/contributor-guide/rst-conv/source-code.html [2] http://docs.openstack.org/contributor-guide/rst-conv/source-code.html#stand… [3] http://docs.openstack.org/contributor-guide/index.html#search-in-this-guide

4 6

Arch Design Guide RST conversion finished
by KATO Tomoyuki 27 Nov '15

27 Nov '15

Hi team, Docs team finished Arch Design Guide RST conversion. At now, new RST translation resource is uploaded to Zanata. openstack-manuals / arch-design (same name) Best Regards, KATO Tomoyuki

1 0

release notes translation
by KATO Tomoyuki 26 Nov '15

26 Nov '15

Hi team, Maybe, as you know, we have the new release notes tool "reno". As far as I know, reno doesn't have translation feature. I'm not sure whether it is planned or not. So, we need to contact and maybe work with reno team. Anyone, interested in taking a lead? Here is a rough blueprint: https://blueprints.launchpad.net/openstack-i18n/+spec/release-notes-transla… Best Regards, KATO Tomoyuki

2 2

DocImpact Changes
by Lana Brindley 25 Nov '15

25 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, The DocImpact flag was implemented back in Havana to make it easier for developers to notify the documentation team when a patch might cause a change in the docs. This has had an overwhelming response, resulting in a huge amount of technical debt for the docs team, so we've been working on a plan to change how DocImpact works. This way, instead of just creating a lot of noise, it will hopefully go back to being a useful tool. This is written in more detail in our spec[1], but this email attempts to hit the highlights for you. TL;DR: In the future, you will need to add a description whenever you add a DocImpact flag in your commit message. Right now, if you create a patch and include 'DocImpact' in the commit message, Infra raises a bug in either the openstack-manuals queue, or (for some projects) your own project queue. DocImpact is capable of handling a description field, but this is rarely used. Instead, docs writers are having to dig through your patch to determine what (if any) change is required. What we are now implementing has two main facets: * The DocImpact flag can only be used if it includes a description. A Jenkins job will test for this, and if you include DocImpact without a description, the job will fail. The description can be a short note about what needs changing in the docs, a link to a gist or etherpad with more information, or a note about the location of incorrect docs. There are specific examples in the spec[2]. * Only Nova, Swift, Glance, Keystone, and Cinder will have DocImpact bugs created in the openstack-manuals queue. All other projects will have DocImpact bugs raised in their own queue. This is handled in [3] and [4]. This will hopefully reduce the volume of DocImpact bugs being created in the openstack-manuals queue, and also improve the quality of the bugs that are created. I know there is a fair amount of confusion over DocImpact already, so I'm more than happy to field questions on this. Thanks, Lana 1: http://specs.openstack.org/openstack/docs-specs/specs/mitaka/review-docimpa… 2: http://specs.openstack.org/openstack/docs-specs/specs/mitaka/review-docimpa… 3: https://review.openstack.org/#/c/248515/ 4: https://review.openstack.org/#/c/248549/ - -- 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/ iQEcBAEBCAAGBQJWU5Q0AAoJELppzVb4+KUyYz4H/j+iAG5x2iRiNbJMBgxm5Qb5 tvxzlOePHZa6VQKj1gYrp8wnBFab0CsNDt/U03D8H9D6No2hqz5qvFgOuMDXIOkS DXG+2RDD8xKMRS42t70mNtJu2oPl+9BWIre+Qyvjd7heicGd+lN/mqAvmwVV3tKB fwJl3iLrlSpwwsyunzR3LxGxzVfHUroRdFv11iQGQZNJYbS9DfOLsz66e5JBTZPh ZoCK8VAlEionaL8ExppoMPQOwpU0oYMWSjM2HGxlc/RDrNEz7HWfXl36nxqfw/mO q8Op0p5cn5UW4fYv/9Ufbw6k0JRgwODCwzSEzJ73gmOJpBrcTEdZKocnGDSdtYA= =CCIn -----END PGP SIGNATURE-----

3 3

New guides published
by Andreas Jaeger 25 Nov '15

25 Nov '15

FYI, Japanese networking guide and Chinese (zh_CN) Install Guides have been added as drafts: http://docs.openstack.org/draft/draft-index.html 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

Virtual Machine Image Guide RST conversion finished
by KATO Tomoyuki 24 Nov '15

24 Nov '15

Hi team, Sorry for late announce. Virtual Machine Image Guide RST conversion has finished. You can look at new translation resource at Zanata: openstack-manuals/image-guide (same name) Unfortunatelly, we has droped the translations with XML markup, which is replaced with RST markup. However, we can easily translate them from Zanata translation memory. Tips: The strings ":guilabel:`xxxx`" is needed to keep this structure. :guilabel:`[yourlanguage]` This is a kind of RST markup. Best Regards, KATO Tomoyuki

1 0

translate.openstack.org upgraded to Zanata 3.7.3
by Elizabeth K. Joseph 20 Nov '15

20 Nov '15

Hi everyone, Thanks to work by Steve Kowalik and testing the upgrades on our translate-dev server, we have landed the upgrade of the production Zanata server from 3.7.1 to 3.7.3. This isn't a major upgrade, but if you're curious as to what has changed, release notes are as follows for the two versions we've upgraded through: 3.7.2: http://docs.zanata.org/en/latest/release-notes/#372 3.7.3: http://docs.zanata.org/en/latest/release-notes/#373 We'd like to involve Daisy and others as we do subsequent upgrades, particularly when we reach the major releases. Steve has written a script to query the API prior to upgrade and after the upgrade on the dev server so that we can be more confident that all of our scripts will continue to work in production, and I'll ask for volunteers from this team to look at translate-dev to confirm that the UI acts the way we expect it to after upgrading translate-dev and before upgrading the production translate server. I've logged in and walked through the UI post upgrade today, but please let us know if you have any trouble. -- Elizabeth Krumbach Joseph || Lyz || pleia2

3 3

What's Up Doc, 20 Nov 2015
by Lana Brindley 20 Nov '15

20 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been working on catching up with some reviews and bug triage, I've been speaking to O'Reilly about the future of the Ops Guide, and also been working on a range of other things including docs-specs core team review, and the addition of Zaqar docs into the user guides. Just a quick heads up that there won't be a docs newsletter next week, though, as I'm taking a couple of days off (my Mum is coming to visit!), so I'll see you again around 4 December. For those of you in the United States, I hope you all have a lovely Thanksgiving :) == Progress towards Mitaka == 138 days to go! 119 bugs closed so far for this release. RST Conversions * 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 * Ops Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst ** Determining whether or not we want to do an updated version for O'Reilly in L * Config Ref ** Contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/image-guide-rst and https://review.openstack.org/#/c/244598/ Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Doc sprint in planning for December. Contact the Ops Guide speciality team for more info or to get involved. ** 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 * I've added some examples to the spec, and we're pretty much ready to go now: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact Document openstack-doc-tools and reorganise index page * Thanks to Brian and Christian for volunteering to take this on! Horizon UX work * Thanks to the people who offered to help out on this! If you're interested but haven't gotten in touch yet, contact Piet Kruithof of the UX team. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Two patches look ready for merge now: https://review.openstack.org/#/c/225418/ and https://review.openstack.org/235893 '''Installation Guide - Christian Berendt''' Business as usual. Nothing special to mention this week. '''Networking Guide - Edgar Magana''' Open Reviews: https://review.openstack.org/#/c/239361/ Merged: https://review.openstack.org/#/c/246671/ Very slow progress, hoping to speed up after the USA holidays. '''Security Guide - Nathaniel Dillon''' No update this week '''User Guides - Joseph Robinson''' After a specification update, there is a need to provide a more comprehensive scope: a list of Core features within scope, and include research on the nova-network/ neutron migration study. Contact from Zaqar, Trove, and Murano Liaisons on Admin guide tasks has been helpful, and given the reorganisation direction. A patch on fernet tokens (FAQ format) merged into the Cloud Admin Guide this week. '''Ops and Arch Guides - Darren Chan''' Arch guide migration is close to completion. We are currently planning to reorganize the guide over a two day virtual sprint in mid December. '''API Docs - Anne Gentle''' Review ready for the Mitaka specification of a vision for app dev docs: https://review.openstack.org/#/c/246660/ '''Config Ref - Gauvain Pocentek''' The tools are ready, the liberty branch is set up, the RST migration is on! Pick your file, run the tools, and let's review. '''Training labs - Pranav Salunke''' Training-labs has Kilo patch merged! We are currently updating the network configuration and trying to get things as per Matt's feedback/request. We plan to start adding Liberty very soon and also KVM port is on the way. '''Training Guides - Matjaz Pancur''' There is interest in translating Upstream training; we are waiting for https://review.openstack.org/#/c/245615/ to merge to enable it on the repo. '''Hyperviser Tuning Guide - Joe Topjian''' On schedule - working on changing bullet-point notes into rough draft sections. == Doc team meeting == We held the US docs meeting this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-11-18 Next meetings: APAC: Wednesday 25 November, 00:30:00 UTC US: Wednesday 2 December, 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… - -- 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/ iQEcBAEBCAAGBQJWTqEMAAoJELppzVb4+KUyx8AH/0AOs2kfvR8TwvMTO9FSuT2F UkfrQfzqPIPjU0d4prIkFxJJ3k9NlGDS4+h2lgZSsqYSDRfinoYMkzAOFGOBB0I/ P9KYx7dd+IRagmF2bOfIDBhl+qTxD4GrzaKdzpH9kAaizmf1xylk6VCXT2Yh0PRd wPRw7RAXg3XjvJhQIElm0pNoRijikAR1CfafzR+HnZMswXPI1S1NnwQSBJD3yYwK npdfEiICdIkzTcdNMODzN57PXkLBymb++EAW/UsWEnmlyyIGJTZqlJNbd8TAGjHz vpvILlZHsuJ8mavPASStZy0ZZad3svusNf6pbsZEdUcS3ibZKRSb3xpEOh31eC0= =7tXE -----END PGP SIGNATURE-----

1 0

IRC meeting tomorrow
by Ying Chun Guo 18 Nov '15

18 Nov '15

Hello, team We will have IRC meeting tomorrow at 1300 UTC in the IRC channel #openstack-meeting. I'm going to cover following topics tomorrow. If you have more topics, please propose freely. * Status update and issues collection of the work items * Discussion: how to manage I18n related bug reports ? * Open discussions Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] RFC: draft doc on how to report translation bugs
by Akihiro Motoki 18 Nov '15

18 Nov '15

BTW, The I18n team meeting wiki page says the next meeting is "Thursday, 5th December at 0600 UTC". Is this wrong information? 2015-11-18 11:59 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for initiating this. > Besides discussion in Gerrit, > let's create a topic to discuss it in the IRC meeting tomorrow. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/17 20:00:13: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2015/11/17 20:28 >> Subject: [Openstack-i18n] RFC: draft doc on how to report translation bugs > >> >> Hi team, >> >> I proposed a doc patch on how to report a translation/I18N bugs. >> >> https://review.openstack.org/#/c/246256/ >> >> It discusses which and where bugs should be filed. >> I know we don't have any consensus on how to manage >> language-specific translation bugs. >> My draft is just a start-line and I don't think it is best. >> Any discussion and input would be appreciated. >> >> Thanks, >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

1 0

RFC: draft doc on how to report translation bugs
by Akihiro Motoki 18 Nov '15

18 Nov '15

Hi team, I proposed a doc patch on how to report a translation/I18N bugs. https://review.openstack.org/#/c/246256/ It discusses which and where bugs should be filed. I know we don't have any consensus on how to manage language-specific translation bugs. My draft is just a start-line and I don't think it is best. Any discussion and input would be appreciated. Thanks, Akihiro

2 1