- OpenStack-I18n - lists.openstack.org

[horizon] Question on a singular/plural string use in openstack_dashboard
by Ian Y. Choi 19 Sep '16

19 Sep '16

Hello, Recently, thanks to the help from Andreas, I am investigating on a broken job for the translation import of Horizon project [1]. The actual error message is : openstack_dashboard/locale/ko_KR/LC_MESSAGES/django.po:8273: a format specification for argument 'req' doesn't exist in 'msgstr[0]' And then I have found that this error was from a string in horizon - openstack_dashboard [2] error_message = ungettext_lazy( 'The requested instance cannot be launched as you only ' 'have %(avail)i of your quota available. ', 'The requested %(req)i instances cannot be launched as you ' 'only have %(avail)i of your quota available.', count) params = {'req': count, 'avail': available_count} In i18n translation infrastructure, only one of two (for singular and plural) strings should be selected, translated, saved, and finally imported back to Horizon project as [1]. However, the first string only used "%(avail)i" string variable, and the second string used both "%(req)i" and "%(avail)i" string variables. Since one Korean translator selected the first string, there will be no "%(req)i" in Korean po file, which generates such an error. So my suggestion is to use the same string variables for both two strings when we use ungettext_lazy function. Is it a bug from Horizon? Would it be other issues when we change like : from 'The requested instance cannot be launched as you only ' to 'The requested %(req)i instance cannot be launched as you only '? [1] http://logs.openstack.org/periodic/horizon-propose-translation-update/c038a… [2] http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/da… With many thanks, /Ian

4 8

Re: [OpenStack-I18n] [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings
by Ian Y. Choi 18 Sep '16

18 Sep '16

Hello, First of all, a little bit sorry for following this thread late. I am a Korean translator. Translation is also one of important and vital parts within OpenStack "Big Tent". Although the hard string freeze period before final release date is only for 3 weeks, many I18n language teams focus on translations during that period intensively. For example, Horizon translation results on lots of languages have been already included since several past releases. For nova and many other projects, the translation focus depends on different language teams. Luigi Toscano wrote on 9/12/2016 9:04 PM: > On Friday, 9 September 2016 14:12:51 CEST Matt Riedemann wrote: >> On 9/9/2016 1:58 PM, Ben Swartzlander wrote: >>> On 09/08/2016 08:37 PM, Matt Riedemann wrote: >>>> On 9/8/2016 7:05 PM, Ravi, Goutham wrote: >>>>> Hi, >>>>> >>>>> >>>>> >>>>> I was looking for some clarity around backports of bug fixes that >>>>> qualify the stable branch policy [1]. >>>>> <http://docs.openstack.org/project-team-guide/stable-branches.html#appro >>>>> priate-fixes> >>>>> >>>>> >>>>> What is the policy if the fix introduces a new translatable string or >>>>> modifies an existing one? >>>>> >>>>> The guidelines in Release management [2] >>>>> <http://docs.openstack.org/project-team-guide/release-management.html> >>>>> regarding string freeze do not specifically call this scenario out. I >>>>> see that while translatable strings are mostly avoided, some projects >>>>> have been merging changes to stable branches with introduction of new >>>>> translatable strings. >>>>> >>>>> >>>>> >>>>> The question is reminiscent of one posed in the ML a few releases ago >>>>> [3]; >>>>> <http://lists.openstack.org/pipermail/openstack-dev/2015-September/07394 >>>>> 2.html> >>>>> >>>>> >>>>> but applies to stable branches. Should we allow changes to translatable >>>>> strings for bug fixes that matter, or is it better to always deny them >>>>> for the sake of translation accuracy? >>>> The former IMO, a high severity bug fix trumps a translation. Note that >>>> some projects are translated on the stable branches too, I know this is >>>> the case for Nova. >>>> >>>> If it's a user-facing change, like an error message in the API, then it >>>> might require a bit more careful consideration, but if it's just a log >>>> message marked for translation that an end user of the API wouldn't see >>>> anyway, then I think it's fine to backport it. >>> So this stance makes sense to me, but I can't reconcile it with the >>> "hard string freeze" rules. Is the theory that after we release, the >>> string freeze ends for the stable branch, and that the hard string >>> freeze only exists for that 3 week period between RC1 and final release, >>> or is the theory that hard string freeze is always subject to exceptions >>> for "critical" bug fixes? >>> >> I treat it as the former. > Interesting: I'm not a translator in the OpenStack project, but I contribute > as translator to other Free Software communities and I would thought as the > latter as more appropriate. Stable is stable and string changes should be > approved on a case-by-case, otherwise translator's life can be more > complicated especially when the next release is translated. > > But as I said I'm not a translator here. > Currently my suggestion is the latter, not former, and if some exception is needed, then writing and sharing such as http://lists.openstack.org/pipermail/openstack-i18n/2016-September/002402.h… would be nice. However, it seems that there are some more things to be elaborated such as: - Need to identify how many projects are interested in translation especially for hard string freeze in different language teams - Although strings are hard-freezed, some strings will not appropriate to be translatable. It can be from misuse of ungettext() and ungettext_lazy() functions. - Or translators may find source string typos. Should they be included into stable branch? - Notification to exceptional cases to I18n team is needed. - ... I would like to copy this thread to openstack-i18n mailing list, and also discuss those things with many translators to find great solutions. If there is some better idea, please share it :) With many thanks, /Ian

1 0

Stop
by Sonny TADJER 17 Sep '16

17 Sep '16

Stop Sent from my iPad > On 17 Sep 2016, at 13:00, openstack-i18n-request(a)lists.openstack.org wrote: > > Send OpenStack-I18n mailing list submissions to > openstack-i18n(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > or, via email, send a message with subject or body 'help' to > openstack-i18n-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-i18n-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenStack-I18n digest..." > > > Today's Topics: > > 1. Re: First stable/newton branches created (Akihiro Motoki) > 2. Re: First stable/newton branches created (Andreas Jaeger) > 3. [String freeze exception] Horizon > https://review.openstack.org/#/c/371907/ (Akihiro Motoki) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Sep 2016 23:42:32 +0900 > From: Akihiro Motoki <amotoki(a)gmail.com> > To: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > Cc: Andreas Jaeger <aj(a)suse.com>, "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Subject: Re: [OpenStack-I18n] First stable/newton branches created > Message-ID: > <CALhU9tk1OnDZ7H+HTqrFG=CJh4EZ2_nvX5iadEMgzQWpzbJ+5A(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 2016?9?16?????Kato, Tomoyuki<kato.tomoyuki(a)jp.fujitsu.com>????????: > >>> Thanks Andreas for the info. >>> >>> Kato-san, could you take care of it? >>> You can do it yourself or delegate it to someone else, >>> but it is better to do it soon. Otherwise master and stable-newton >>> will be diverged. >> >> Sorry for late response. I wiil work on it from now. > > > No problem. I can help additional prpject branching. > We were just discussing what we can, > Thanks formyour help. > > >> KATO Tomoyuki >> >> >>> >>>> Syncing to Zanata works automatically if there is a stable-newton (note >>>> the "-", Zanata does not allow "/"!) branch. >>> >>> That's what was unclear to me. Thanks. >>> So, the question now is who creates stable-newton version in Zanata. >>> I think only the limited folks can do that. Perhaps Daisy, Kato-san, >> Andreas? >>> In addition to the permission, the tips on creating a Zanata version >>> has not been shared. >>> >>> Akihiro >>> >>> 2016-09-16 14:32 GMT+09:00 Andreas Jaeger <aj(a)suse.com <javascript:;>>: >>>>> On 09/16/2016 04:30 AM, Akihiro Motoki wrote: >>>>> Hi Ian, >>>>> >>>>> 2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi(a)gmail.com >> <javascript:;>>: >>>>>> Hello Andreas and i18n team members, >>>>>> >>>>>> Yesterday (according to UTC), Kato-san and me discussed this topic >> in IRC >>>>>> meeting [1], >>>>>> but we are not sure when we will have stable-newton branch. >>>>>> I think it is time to create stable-newton branch now and Kato-san >> will deal >>>>>> with, >>>>>> but I would like to ask some details to clarify the best timing of >> creating >>>>>> a stable branch. >>>>>> >>>>>> When should i18n team create a stable branch (e.g., stable-newton) in >>>>>> Zanata? >>>>> >>>>> Although I am not familiar with Zanata operations, I think the i18n >>>>> team needs to >>>>> create 'stable-newton' version by branching 'master' version in Zanata >>>>> to inherit >>>>> translation works made in the master version so far. >>>>> >>>>> In my understanding, what we need to do are: >>>>> (a) create stable-newton version in Zanata from master version -> >> i18n team >>>>> (b) release RC1 deliverables and create stable/newton branch in git >>>>> repositories -> each project team and release team >>>>> (c) set up project-config to sync repositories and translations for >>>>> stable/newton -> infra team (I can as well) >>>> >>>> Syncing to Zanata works automatically if there is a stable-newton (note >>>> the "-", Zanata does not allow "/"!) branch. Importing into >>>> stable/newton needs project-config changes. If you would do that, it >>>> would be great! >>>> >>>> >>>>> There is no strict relationship between (a) and (b), and either of >>>>> them can happen first. >>>>> If the timing of (a) and (b) are closer, most translation work in >>>>> 'master' in Zanata are copied into 'stable-newton' version. >>>>> (c) needs to be done after both (a) and (b). >>>> >>>> Indeed, >>>> >>>> Andreas >>>> >>>>>> I thought just after from "Hard StringFreeze" in [2] would be the >> right >>>>>> time, >>>>>> or checking at least Horizon development status (since the focus of >> i18n >>>>>> team now is Horizon related projects) >>>>>> would be needed. (Previously we had I18n cross project liaisons [3].) >>>>> >>>>> To be honest, RC1 release means 'Hard String Freeze'. That's all. >>>>> We can know RC1 release notices by various ways: >>>>> - checking release announcements, >>>>> - checking openstack/releases reviews [5], >>>>> - checking releases.openstack.org [6] >>>>> >>>>> I think we should prepare stable-newton version in Zanata for all >> projects, >>>>> even though most of the i18n team focus on horizon related >> translations. >>>>> >>>>> I am not sure i18n liaisons for horizon related projects work in this >> cycle. >>>>> We have sent no reminder for i18n liaisons... >>>>> In the previous release, I took care of horizon related projects but >>>>> it is beyond >>>>> the role of horizon-i18n liaison and I am not taking care of them >>>>> (except horizon itself). >>>>> >>>>> Horizon RC1 will be shipped in several hours. The team is preparing >>>>> the release now. >>>>> >>>>>> Or should we start gradually the projects merged with >> "topic:create-[release >>>>>> name]" patches, like [4]? >>>>>> >>>>>> [1] >>>>>> http://eavesdrop.openstack.org/meetings/openstack_i18n_ >> meeting/2016/openstack_i18n_meeting.2016-09-15-13.03.html >>>>>> [2] https://releases.openstack.org/newton/schedule.html >>>>>> [3] https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n >>>>>> [4] https://review.openstack.org/#/q/topic:create-newton >>>>> >>>>> [5] https://review.openstack.org/#/q/project:openstack/releases+ >> path:%255Edeliverables/newton/.* >>>>> [6] https://releases.openstack.org/newton/index.html >>>>> >>>>> Thanks, >>>>> Akihiro >>>>> >>>>>> >>>>>> >>>>>> With many thanks, >>>>>> >>>>>> /Ian >>>>>> >>>>>> Andreas Jaeger wrote on 9/16/2016 3:35 AM: >>>>>>> >>>>>>> Could somebody please set up stable-newton branches for those >> projects >>>>>>> that should get translations of them, please? >>>>>>> >>>>>>> With RC1 today, projects are creating stable/newton branches now, >>>>>>> >>>>>>> Andreas >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> OpenStack-I18n mailing list >>>>>> OpenStack-I18n(a)lists.openstack.org <javascript:;> >>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >>>> >>>> >>>> -- >>>> 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

[String freeze exception] Horizon https://review.openstack.org/#/c/371907/
by Akihiro Motoki 17 Sep '16

17 Sep '16

Hi i18n team, I would like to request a string freeze exception for horizon: https://review.openstack.org/#/c/371907/ which fixes https://bugs.launchpad.net/horizon/+bug/1624197 . It is small enough and can be accepted. Can we move this forward? This patch allows translators to control the word order in delete confirm forms. Currently "You have selected: " and selected items are concatenated and in some language the selected items need to be placed first. Thanks, Akihiro

3 2

What's Up, Doc? 16 September
by Lana Brindley 16 Sep '16

16 Sep '16

Hi everyone, Newton goes out in three weeks, and the release team and I have been busy working with our cross-project liaisons to ensure the docs suite is up to date and ready to go. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. This week, I've also been working on Summit planning, and drafting my PTL candidacy, which you can read here: http://lists.openstack.org/pipermail/openstack-docs/2016-September/009112.h… Big thanks to everyone who has emailed me over the past few days to offer their support. Knowing you all have my back is the reason I keep doing this :) == Progress towards Newton == 19 days to go! Bugs closed so far: 444 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * I have a draft schedule starting to take shape, which you can see here: https://etherpad.openstack.org/p/Ocata-DocsSessions I'll put this into Sched once the tool becomes available, and your early feedback is welcome. Additionally, if you're interested in moderating a session in Barcelona, please let me know. * By now, you should be well on the way to having your travel and accommodation booked for Barcelona. In case you're still working on it, though, there's travel information available on the Summit site here: https://www.openstack.org/summit/barcelona-2016/travel/ * Looking a little further forward, Foundation have now announced that the first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: http://www.openstack.org/ptg == Speciality Team Reports == This will be the last Speciality Team report before we release Newton, as focus shifts to final preparations, testing, and release notes. I'd like to take this opportunity to thank all our speciality team leads, who work very hard behind the scenes to keep their books in top shape, and their teams working together towards a common goal. Our docs suite wouldn't be what it is without these hard working people. '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting Next meeting: 27 September August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No report this week. '''API Guide: Anne Gentle''' Working with teams who want to write guides similar to FirstApp: Murano and Heat for example. This patch moves Cinder v1 API to Deprecated: https://review.openstack.org/#/c/370407/ Thanks Mark Voelker for all the links to go with the patch! '''Config/CLI Ref: Tomoyuki Kato''' Updating Config reference for Newton release. We need to help, especially for vendor plug-in configuration. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-09-14 Next meetings: APAC: Wednesday 21 September, 00:30 UTC US: Wednesday 28 September, 19: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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#16_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

What's Up, Doc? 9 September
by Lana Brindley 11 Sep '16

11 Sep '16

Hi everyone, Only four weeks to go until Newton! Andreas, Brian, Olga, and I met with our new release managers Olena and Alex a few days ago, and we're all ready and waiting with bated breath to get started on the release. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. This week, I've also done a core team review, and we bid farewell to two core team members. More on that in this newsletter. == Progress towards Newton == 26 days to go! Bugs closed so far: 428 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * If there's something you want to make sure we discuss at Summit, please put your ideas here: https://etherpad.openstack.org/p/Ocata-DocsSessions When we get our room allocations, I'll organise it into a schedule. * If you require a visa invitation letter to travel to Spain, then you need to fill out the form here: https://www.openstack.org/summit/barcelona-2016/travel/#visa Looking a little further forward, Foundation have now announced that the first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: http://www.openstack.org/ptg == Core Team Review == The core team have completed their review for August, and I'm a bit sad to announce that both Atsushi Sakai and Gauvain Pocontek are no longer core team members. Gauvain has been committing to OpenStack manuals since well before my time, and has been an invaluable resource for many people (including myself!) over the years. He is currently working on some new projects, but we hope to still see him around from time to time. Atsushi-san joined the core team last year, and during that time has proven an extremely effective reviewer. He is still very busy on OpenStack, with an increased focus on cross-project tasks, so we will be sure to still see him around. I wish you well on your endeavours! I thank you both for your commitment to being core team members, and for all your contributions. We are better because of your effort. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' Organizing a HA meetup at summit Intention is get an update plan finalized shortly '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 13 September August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No report this week. '''API Guide: Anne Gentle''' Working on an article for Super User describing the switchover in API guide sources to project repos and the new navigation. '''Config/CLI Ref: Tomoyuki Kato''' Consolidating the OSC command reference into the OSC specific doc. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Finished first day of our virtual sprint series (6 Sep): Common items: https://etherpad.openstack.org/p/upstream-uni-common-items (coordinated by Ildiko Vancsa, ildikov), Code contribution: https://etherpad.openstack.org/p/upstream-uni-code-contribution (coordinated by Kendall Nelson, diablo_rojo) Next virtual sprint dates: 12,13 and 16 September (https://wiki.openstack.org/wiki/VirtualSprints#Upstream_training_Sprint) '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-09-07 Next meetings: US: Wednesday 14 September, 19:00 UTC APAC: Wednesday 21 September, 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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#9_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 1

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 08 Sep '16

08 Sep '16

Reviewed: https://review.openstack.org/319276 Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0adde01a06d81ab3… Submitter: Jenkins Branch: master commit 0adde01a06d81ab39f536794e178d0434e9783a2 Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 16:20:48 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. The obsolete check that .po and .pot files are valid is removed from tox.ini. Change-Id: I149c2254cb04297e598cfd3ca73b24efd0c8ef18 Closes-Bug: #1536226 ** Changed in: cinder Status: In Progress => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: New Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

What's Up, Doc? 2 September
by Lana Brindley 02 Sep '16

02 Sep '16

Hi everyone, We have five weeks left until the Newton release goes out, so this week has been all about getting started on testing the Install Guide. We now have beta releases for all our distros, so thanks to our lovely package maintainers for getting back to me so quickly! We can still use more testers, though, all you need to do is sign up on the wiki page and start testing: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting This week Andreas, Brian, Olga, and I will be meeting with our new release managers Olena and Alex, to make sure they're up to speed. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. == Progress towards Newton == 33 days to go! Bugs closed so far: 407 Release managers: Olena Logvinova and Alexandra Settle Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * If there's something you want to make sure we discuss at Summit, please put your ideas here: https://etherpad.openstack.org/p/Ocata-DocsSessions When we get our room allocations, I'll organise it into a schedule. * Talk acceptances have gone out, congratulations to everyone who got something accepted! * If you require a visa invitation letter to travel to Spain, then you need to fill out the form here: https://www.openstack.org/summit/barcelona-2016/travel/#visa == Docs Tools == There is a lot of cleanup happening on the docs site right now, so you might see some old and unloved content disappear. If you notice anything strange, please let Andreas or the docs mailing list know so we can get it straightened out. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 13 September August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No meeting last week in light of the ops mid cycle and OpenStack East conference Updating use cases chapter in Arch Guide Looking for more enterprise troubleshooting docs to push upstream for the ops guide '''API Guide: Anne Gentle''' New landing page for a collection of all API Reference docs and Guides in one place: https://review.openstack.org/#/c/361480/ Improvements to the sidebar link collection: https://review.openstack.org/#/c/362436/ '''Config/CLI Ref: Tomoyuki Kato''' Updated some CLI reference. Closed some bugs for Config Reference. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == For the month of August, we had a 6% increase in traffic over July. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-08-31 Next meetings: APAC: Wednesday 7 September, 00:30 UTC US: Wednesday 14 September, 19: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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#2_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Fwd: Re: [OpenStack-docs] Stopping DocBook Building
by Ian Y. Choi 30 Aug '16

30 Aug '16

Hello! Recently I have found that there has been some changes on the following landing pages : French, Japanese, Chinese (Simplified) and draft. You can check: https://review.openstack.org/#/c/362350 Thank a lot, Andreas! With many thanks, /Ian -------- Original Message -------- Subject: Re: [OpenStack-docs] Stopping DocBook Building Date: Tue, 23 Aug 2016 13:08:53 +0200 From: Andreas Jaeger <aj(a)suse.com> Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard, Graham Norton , HRB 21284 (AG Nuernberg) To: Anne Gentle <annegentle(a)justwriteclick.com> CC: openstack-docs(a)lists.openstack.org <Openstack-docs(a)lists.openstack.org> On 2016-08-22 18:03, Andreas Jaeger wrote: > On 08/22/2016 02:33 PM, Anne Gentle wrote: >> Hurray! >> >> >> >>> On Aug 22, 2016, at 2:23 AM, Andreas Jaeger <aj(a)suse.com> wrote: >>> >>> I think we're far enough with DocBook building removal that we can >>> Release openstack-doc-tools without DocBook support. >>> >>> For older branches, I'll put up a request to cap openstack-doc-tools. >>> >>> https://review.openstack.org/#/q/topic:openstack-doc-tools-1 >>> >>> One question: Can we stop building api-site DocBook documents now as >>> well? With most api-ref projects moved over, we already froze the >>> content. Is there a need to continue publishing? >> >> >> None that I can think of now that trove has migrated. >> >> I'm also going to stop building OpenAPI / swagger from that source. > > I stop building the swagger documents and also stop building the DocBook > XML content on api-site with: > https://review.openstack.org/358734 Let's continue this road - and disable DocBook XML and swagger building completely for api-site: https://review.openstack.org/358727 https://review.openstack.org/358734 I have not removed those files yet, 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-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

What's Up, Doc? 26 August
by Lana Brindley 26 Aug '16

26 Aug '16

Hi everyone, This week marks six weeks left to the Newton release, so I've been busy getting everything prepared. We're now ready to start testing the core Installation Tutorial, so check out the wiki and get signed up: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting#Testers We've also selected two new release managers to assist with this release, please welcome Olena and Alex! More on those topics in this newsletter. == Progress towards Newton == 40 days to go! Bugs closed so far: 387 Release planning: https://etherpad.openstack.org/p/NewtonRelease == Release Managers == There was an overwhelming response to my request for release managers, which was very cool! The first two responders were Olena Logvinova <ologvinova(a)mirantis.com> and Alexandra Settle <alexandra.settle(a)RACKSPACE.COM>, so please welcome them to the release team. Their main role during this process is to make sure that all the tasks we have to complete get done accurately and on schedule. It's an important job, and we're really glad to have you both on board. == Install Tutorial Testing == Install Tutorial testing is just about ready to kick off. If you're interested in helping, make sure you've added your name on to the list on our testing wiki page: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting (if you don't have wiki access, just email me directly and I'll add you in). Thanks to our package maintainers, we now have b2 pre-release packages ready for Ubuntu and Debian, so those are ready to be tested. == Docs Tools == I'm very pleased to announce that we have now removed DocBook from our build tools. The end of an era! Thanks to Anne, Andreas, and David Cramer for keeping this project alive for so long, and eventually seeing it come to fruition. Version 1.5.0 of openstackdoccstheme was released this week. In other tools news, there are plans afoot to move developer.openstack.org and docs.openstack.org away from Rackspace Cloudsites, and on to pages that OpenStack Infra control. This has been on the proverbial backburner for a long time, but the Infra team is now in a position to make it happen. You can read and comment on the Infra spec here: https://review.openstack.org/#/c/276482/ == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 30 August 0600UTC. '''Networking Guide: Edgar Magana''' Attending the OpenStack East in NYC. No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No report this week. '''API Guide: Anne Gentle''' Releasing openstackdocstheme with new sidebar and integration with os-api-ref Sphinx Extension. Many thanks to Karen Bradshaw, Sean Dague, Graham Hayes, Andreas Jaeger (and anyone I may have missed!) for their tireless efforts on this release. WOW. '''Config/CLI Ref: Tomoyuki Kato''' Merged some patches, updated a few CLI reference, nothing special. '''Training labs: Pranav Salunke, Roger Luethi''' Some minor changes, backports of features. The parser is almost done. https://github.com/dguitarbite/rst2bash Updated the openstack-manuals, install-guides with the new syntax which is parser friendly. I should start sending the required patches to manuals repo. soon after finalizing the syntax.. https://github.com/dguitarbite/openstack-manuals/commit/c9e7e1bb2c7269f02a7… '''Training Guides: Matjaz Pancur''' Upstream training improvement (https://etherpad.openstack.org/p/upstream-university-improvements) Please consider participating in the Remote content sprint (proposed timeframe: first half of September, see etherpad for details). '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == Keystone and Ceph are this week's most popular search terms. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-08-24 Next meetings: US: Wednesday 31 August, 19:00 UTC APAC: Wednesday 7 September, 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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#26_August_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Fwd: [openstack-dev] [release] Release countdown for week R-5, 29 Aug - 2 Sept
by Ian Y. Choi 26 Aug '16

26 Aug '16

Hello, Hope that everything goes well for all. I am forwarding one e-mail which recalls 'soft string freeze'! By the way, when is the next IRC i18n meeting? 06:00 UTC on September 1 is correct? If it is correct, I think it is a good time to summarize what we did and decide which projects to be translated as i18n team objectives. With many thanks, /Ian -------- Original Message -------- Subject: [openstack-dev] [release] Release countdown for week R-5, 29 Aug - 2 Sept Date: Thu, 25 Aug 2016 14:58:49 -0400 From: Doug Hellmann <doug(a)doughellmann.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: openstack-dev <openstack-dev(a)lists.openstack.org> Focus ----- The feature freeze deadline is 1 Sept. All project teams should be putting the last minute touches on feature work. General Notes ------------- Non-client libraries are frozen and will only see updates for release-critical bugs. We have not created stable branches, yet, in case we do need those releases. Teams who haven't frozen master will need to create the stable branch from their most recent release and backport fixes before doing a patch release. The third milesone occuring this week includes several freezes in our release cycle to let us shift our focus to bug fixes and generally hardening the release. * We freeze releases of all libraries and changes to requirements between the third milestone and the final release to give downstream packagers time to vet the libraries. Only emergency bug fix updates are allowed during that period, not releases for FFEs. * The overall feature freeze allows teams to wrap up Newton and start thinking about Ocata planning. * We start a soft string freeze at the milestone to give translators time to catch up with the work that has already been done this cycle. A hard string freeze will follow two weeks later at R-3. Release Actions --------------- The last day for releases for client libraries will be 1 Sept. File your release request in time to have the release done on the 1st. The milestone deadline is also 1 Sept. Please file your 0b3 tag request in time to have the release done on the 1st. Review the members of your $project-release group in gerrit, based on the instructions Thierry sent on 15 Aug. Important Dates --------------- Newton RC-1, 15 Sept. Newton release schedule: http://releases.openstack.org/newton/schedule.html __________________________________________________________________________ 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

1 0

Asking for update in some language team wiki pages
by Ian Y. Choi 25 Aug '16

25 Aug '16

Hello, First of all, thanks a lot Akihiro-san for your kind updates (e.g., [1]) on OpenStack I18n Guide [2]. I have just found that some language team Wiki pages in I18nTeam/team [3] still refer to Transifex, which is deprecated and now we use Zanata. I do not have much knowledge on interpreting and reading different languages, but from my brief observation, it seems that those language team pages need to be updated: - Catalan: https://wiki.openstack.org/wiki/I18nTeam/team/ca => mentions Transifex & wrong IRC channel #openstack-translation (changed to #openstack-i18n) - English (Austraila): https://wiki.openstack.org/wiki/I18nTeam/team/en_au => mentions www.transifex.com - Hindi: https://wiki.openstack.org/wiki/I18nTeam/team/hi => mentions www.transifex.com - Polish: https://wiki.openstack.org/wiki/I18nTeam/team/pl => mentions Transifex with web site URL and a profile - Punjabi: https://wiki.openstack.org/wiki/I18nTeam/team/pa_IN => mentions Transifex with URL and a project link - Spanish: https://wiki.openstack.org/wiki/I18nTeam/team/es => Profile IDs refer to Transifex profile links - Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi (C-DAC) : https://wiki.openstack.org/wiki/I18nTeam/team/CDACTeam => mentions www.transifex.com Let's update them :) [1] https://review.openstack.org/#/c/360663/ [2] http://docs.openstack.org/developer/i18n/ [3] https://wiki.openstack.org/wiki/I18nTeam/team With many thanks, /Ian

1 0

What's Up, Doc? 19 August
by Lana Brindley 19 Aug '16

19 Aug '16

Hi everyone, Watch out, Install Guide testing season is about to begin! If you're a package maintainer, cross-project liaison, or just a helpful testing regular, look out for an email from me real soon now! In the meantime, keep hitting those bugs, and letting us know if you spot any problems in the guide. == Progress towards Newton == 47 days to go! Bugs closed so far: 371 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' Some reviews, nothing interesting '''Install Tutorials: Lana Brindley''' Core Guide testing to kick off Real Soon Now (tm). Next meeting: 30 August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' Reorganized monitoring content in the Ops Guide Migrating ops, legal, and security content in the Arch Guide Working on use cases chapter and design chapter in the Arch Guide '''API Guide: Anne Gentle''' No report this week. '''Config/CLI Ref: Tomoyuki Kato''' A few cleanups are under going. Updated some client references. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == Just under 90,000 sessions on the docs site this week. == Doc team meeting == Next meetings: The US meeting failed to make quorum this week. We're seeing this a lot recently, is there still a need for a regular docs meeting? Next meetings: APAC: Wednesday 24 August, 00:30 UTC US: Wednesday 31 August, 19: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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#19_August_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 1

Barcelona Design Summit space needs
by Kato, Tomoyuki 19 Aug '16

19 Aug '16

Hi team, This is preparation for the Barcelona Design Summit. As of now, I'd like to request 2 spaces for I18n. due date: August 30 - 1 workroom session - 1 contributor meetup Any thought? Note that we should probably require *less* slots than in Austin because the whole Summit event starts on the Tuesday and is only 4 days. - Ops summit on Tuesday morning until 4pm - Cross-project workshops from Tuesday 4pm to Wednesday 4pm - Fishbowl/Workroom sessions from Wednesday 4pm to Friday noon - Contributors meetups on Friday afternoon * Fishbowl sessions (from Wednesday 4pm to Friday noon) Our traditional largish rooms organized in fishbowl style, with advertised session content on the summit schedule for increased external participation. Ideal for when wider feedback is essential. * Workroom sessions (from Wednesday 4pm to Friday noon) Smaller rooms organized in boardroom style, with topic buried in the session description, in an effort to limit attendance and not overcrowd the room. Ideal to get work done and prioritize work in small teams. * Contributors meetup (Friday afternoon) Half-day session on Friday afternoon to get into the Ocata action while decisions and plans are still hot, or to finish discussions started during the week, whatever works for you. Best Regards, KATO Tomoyuki

1 0

Fwd: [openstack-dev] [all][ptl][tc] extra ATCs for newton
by Akihiro Motoki 18 Aug '16

18 Aug '16

Forwarded to i18n list. My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially. Akihiro ---------- Forwarded message ---------- From: Doug Hellmann <doug(a)doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev(a)lists.openstack.org> It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton. Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status. The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC. Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug. PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review. Thanks, Doug [1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-… __________________________________________________________________________ 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

5 8

Request for OpenStack Mitaka pii files for IBM documentation translation project with quotes from OpenStack
by Monika Wolf 18 Aug '16

18 Aug '16

Hello, I am currently working on an IBM translation project which contains quoted pii strings from OpenStack Mitaka release. In order to be able to use the translated version of those strings I would need the English and German Mitaka files (including Horizon UI). When I checked with the IBM lab responsible for this project I got this answer: > Here is the response from Development: > "We're using mitaka release .More details about release dates here: > http://releases.openstack.org/ > In the past , OpenStack used to assign a certain version to the entire > > distribution . Now individual projects in OpenStack have their own > version (e.g. nova-manage --version returns 13.0.1, which is the > version of nova associated with mitaka)" Please also refer to the attached shot (which contains part of the quoted pii strings). I appreciate your support. (See attached file: TCT25_a.jpg) Mit freundlichen Grüßen / Kind regards Monika Wolf Translator/Tester Contractor IBM Sales & Distribution, Software Sales Translation Services Center (TSC) Germany Phone: 0711 83889237 IBM Deutschland GmbH Email: vcomas3(a)de.ibm.com Am Fichtenberg 1 71083 Herrenberg IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Martina Koederitz (Vorsitzende), Susanne Peter, Norbert Janzen, Dr. Christian Keller, Ivo Koerner, Markus Koerner Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 14562 / WEEE-Reg.-Nr. DE 99369940

5 5

No meeting 8/18
by Kato, Tomoyuki 18 Aug '16

18 Aug '16

Hi team, No meeting 8/18 due to my personal reason. KATO Tomoyuki

1 0

[Bug 1534418] Re: Wrong Chinese translation in OpenStack install doc
by Ian Y. Choi 12 Aug '16

12 Aug '16

Fix released (e.g., Mitaka: http://docs.openstack.org/mitaka/zh_CN /install-guide-rdo/environment-ntp-controller.html ) ** Changed in: openstack-i18n Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1534418 Title: Wrong Chinese translation in OpenStack install doc Status in openstack i18n: Fix Released 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… There is an extra "中" in the translation. It should be translated to "组织中提供的". The picture is attached. + Mitaka : http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/environment-ntp-co… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1534418/+subscriptions

1 0

[Bug 1556886] Re: zh_CN in trove-dashboard string looks wrong
by Ian Y. Choi 12 Aug '16

12 Aug '16

Merged: https://review.openstack.org/#/c/353343/ (stable/mitaka) and https://review.openstack.org/#/c/351998/ (master). Thanks, Shengjing! ** Changed in: openstack-i18n Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1556886 Title: zh_CN in trove-dashboard string looks wrong Status in openstack i18n: Fix Released Bug description: Please see https://review.openstack.org/#/c/290287/2/trove_dashboard/locale/zh_CN/LC_M…: #, python-format msgid "" "[flavor=%(flavor)s, volume=%(volume)s, name=%(name)s, type=%(type)s, " "related_to=%(related_to)s]" msgstr "" "[flavor=%(flavor)s, volume=%(volume)s, name=%(name)s, type=%(type)s, " "related_to=%(related_to)s]" As Amrid says: " This doesn't look right. Shouldn't this be <chinese characters for flavor>=..., etc., Like line 1029" j To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1556886/+subscriptions

1 0

What's Up, Doc? 12 August
by Lana Brindley 12 Aug '16

12 Aug '16

Hi everyone, I have been struck down with flu yet again this week, so a quiet one from me (I'll be glad when winter is over, let me tell you!). Anne, however, has been kicking it out of the park with her work on the API docs; I suggest you take a look at the update she sent to the mailing lists the other day to catch up: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101380.html == Progress towards Newton == 54 days to go! Bugs closed so far: 365 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Next meeting: 16 August 0600UTC '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' Bug hunt continued, all contributions are welcome, grammatical and technical alike! Focusing on the last half of the SecurityGuide, and the 'freshness' of code examples Threat analysis documentation and templates added '''User Guides: Joseph Robinson''' The Consistency and Editing patch is ready to merge, and just needs more reviews https://review.openstack.org/#/c/347641/ . Some pages in the User Guides are resulting in 404s (dashboard manage shares for example), and this bug is tracking the changes https://bugs.launchpad.net/openstack-manuals/+bug/1611792 Thanks to Maria for taking on the file name changes to the User Guide, and Anne for also patching the Admin Guide file names! '''Ops Guide: Shilla Saebi, Darren Chan''' Working on storage, networking, and compute sections in the Arch Guide. Arch Guide working group proposed a series of short sprints, working in pairs as SME/writer. Dates TBD Waiting on enterprise ops documentation to migrate to the Ops Guide. '''API Guide: Anne Gentle''' Ceilometer migrated content has landed! \o/ https://review.openstack.org/334028 Many thanks to Khushbu Parakh for sticking with it, and to Julien Danjou and Gordon Chung for accepting the (rather outdated) migrated content and taking responsiblity for it from now on. Working on a template for http-status.yaml file that teams can use for new pretty HTTP Status code tables that just landed last week. https://review.openstack.org/#/c/351835/ Ever closer to landing the API reference navigation. https://review.openstack.org/#/c/329508/ Refer to status report on -dev and -docs mailing lists: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101380.html '''Config/CLI Ref: Tomoyuki Kato''' Closed a few bugs with mitaka backport. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Updating Upstream training for the next OpenStack Summit (https://etherpad.openstack.org/p/upstream-university-improvements) Next meeting: Monday 15 August 1700 UTC in #openstack-meeting '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == This week, 385 visitors came to the docs site from Stack Overflow, 423 visitors came via searching on duckduckgo, and 508 came from ask.openstack.org. == Doc team meeting == Next meetings: The APAC meeting failed to make quorum this week, but thanks to Darren for trying anyway :) Next meetings: US: Wednesday 17 August, 19:00 UTC APAC: Wednesday 24 August, 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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#12_August_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Broken translations...
by Kato, Tomoyuki 12 Aug '16

12 Aug '16

Hi Andreas, Thanks for your help. I sent a email to the translator and coordinators directly. Regards, KATO Tomoyuki > -----Original Message----- > Same failure pattern for zh_CN, this time on sahara-dashboard and ironic-ui: > > http://logs.openstack.org/periodic/sahara-dashboard-propose-translation-upd… > > http://logs.openstack.org/periodic/ironic-ui-propose-translation-update/d53… > > Could somebody reach out to the translators that break this? > > 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 > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

5 6

[Bug 1609474] [NEW] [Chinese] ironic-ui and sahara-dashboard translation error
by Ian Y. Choi 10 Aug '16

10 Aug '16

Public bug reported: The following wrong strings generate Jenkins periodic job errors: 1) zh-CN : ironic_ui/locale/djangojs (URL: https://translate.openstack.org/webtrans/translate?project=ironic-ui&iterat… ) - #10; "Unable to delete node %s: %s" or #39; "{$ property.getDescription() $}" (IMO #10 has more possibility on the error) 2) zh-CN: sahara_dashboard/locale/django (URL: https://translate.openstack.org/webtrans/translate?project=sahara-dashboard… ) - #50; Start Verification & Start Verifications => only 1 of 2 is translated, which cause the error - 58; "Uptime" => Deleting unnecessary '\n' is needed ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: simplified-chinese ** Tags added: simplified-chinese -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1609474 Title: [Chinese] ironic-ui and sahara-dashboard translation error Status in openstack i18n: New Bug description: The following wrong strings generate Jenkins periodic job errors: 1) zh-CN : ironic_ui/locale/djangojs (URL: https://translate.openstack.org/webtrans/translate?project=ironic-ui&iterat… ) - #10; "Unable to delete node %s: %s" or #39; "{$ property.getDescription() $}" (IMO #10 has more possibility on the error) 2) zh-CN: sahara_dashboard/locale/django (URL: https://translate.openstack.org/webtrans/translate?project=sahara-dashboard… ) - #50; Start Verification & Start Verifications => only 1 of 2 is translated, which cause the error - 58; "Uptime" => Deleting unnecessary '\n' is needed To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1609474/+subscriptions

2 1

[Bug 1535501] Re: Chinese translation of Install doc
by Shengjing Zhu 10 Aug '16

10 Aug '16

Documents have been updated and these strings are not available now. ** Changed in: openstack-i18n Status: Confirmed => Invalid -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1535501 Title: Chinese translation of Install doc Status in openstack i18n: Invalid Bug description: The original link is http://docs.openstack.org/liberty/install-guide-rdo/neutron-controller-inst… The translation link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/neutron-controlle… The picture is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1535501/+subscriptions

1 0

Do you translate these...
by Adrien Cunin 09 Aug '16

09 Aug '16

Hi everyone, Working on the Horizon translation in French, I came across these translatable strings and wondered if it makes sense to keep them translatable: * "Material": as in the name of the Horizon theme inspired by Google's Material Design. Anyone wants to have that translatable for their language? As the name of the theme, I'd keep it as is in French. * "10%", "75%": I think I have a first answer with https://en.wikipedia.org/wiki/Percent_sign#Spacing - but are there more differences in some languages? Can we imagine a better way to handle this than having potentially dozens of "xx%" strings to translate? Adrien

2 1

Broken translations...
by Andreas Jaeger 06 Aug '16

06 Aug '16

FYI, these currently fail: http://logs.openstack.org/periodic/ironic-ui-propose-translation-update/3ff… http://logs.openstack.org/periodic/sahara-dashboard-propose-translation-upd… Both cases mean a broken zh-CN translation. Can we tighten the zanata settings to avoid that people introduce such bugs? Or what can be done? 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 3