September 2016 - OpenStack-I18n - lists.openstack.org

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 15 Sep '16

15 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 01 Sep '16

01 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