- OpenStack-I18n - lists.openstack.org

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