<div dir="ltr">Hi all, <div>First of all, I'm sorry we had to skip last week's doc team meeting and that I didn't send this note out last week -- had to take care of my son's health. As Pa from Little House on the Prairie would say, "All's well that ends well." </div>
<div><br></div><div>Thanks to the APAC team for holding the docs team meeting this week. Minutes and logs:</div><div><a href="http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-16-03.06.html">http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-16-03.06.html</a><br>
</div><div><a href="http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-16-03.06.log.html">http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-16-03.06.log.html</a><br><div><br></div><div>
<div>__In review and merged this past week__</div><div>The CLI Reference has been updated for the release of:</div><div> python-novaclient 2.18.1</div><div> python-keystoneclient 0.9</div><div> <a class="" href="https://review.openstack.org/106553" style="text-decoration:none;font-family:sans-serif;color:rgb(34,34,34)!important;background-image:none!important;background-repeat:initial!important">python-cinderclient 1.0.9</a><br>
</div><div> python-glanceclient 0.13.1</div><div><br></div><div>We're now labeling the release name in a running sidebar of text on older releases and the current release for all docs pages that correlate with an integrated release. </div>
<div><br></div><div>The neutron.conf advanced configuration info has been updated to use the alias openvswitch rather than, for example, neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2.</div><div><br></div>
<div>__High priority doc work__</div><div><br></div><div>I'm as eager as you are to get my hands on the results of the Architecture and Design Guide! We're working on the best output and should have it available soon. <br>
</div><div><br></div><div>__Ongoing doc work__</div><div><br></div><div>To clarify the request for docs-specs, while we have some wiki page specifications for Launchpad blueprints, I was hoping to try out the docs-specs repo for the networking guide, the HOT template user guide chapter, and for app developer deliverables. We are trying out the docs-specs repo rather than wiki pages. So far Andreas has proposed one for a common glossary, and Gauvain is working on another for the HOT template user guide chapter. Phil and Matt are working on the networking guide, so that leaves Tom and me working on developer deliverables. Training guides, do you have any blueprints you want reviewed? Let's get them proposed. </div>
<div><br></div><div>Or, if we think we should stick to wiki pages for specs, that's okay too. </div><div><br></div><div>__New incoming doc requests__</div><div><br></div><div>The Trove team gets a gold star for outlining their doc gaps here: <a href="https://etherpad.openstack.org/p/trove-doc-items">https://etherpad.openstack.org/p/trove-doc-items</a>. Their goal is to get those items at least in draft by 7/24. </div>
<div><br></div><div>Mostly the interest is in the HOT templates doc and the upcoming Networking doc swarm and spec. </div><div><br></div><div>__Doc tools updates__</div><div><br></div><div>I want to be clear that there's no Foundation support for any purchased licenses of a proprietary toolchain. Our entire docs toolchain is open. Some of us choose to use Oxygen for authoring, and Oxygen XML, the company, chooses to support open source projects by providing free licenses for a longer trial than their 30 day trial. So as far as I know, something like Prince for output wouldn't be supported. </div>
<div><br></div><div>The clouddocs-maven-plugin has a 2.1.2 release (release notes: <a href="https://github.com/stackforge/clouddocs-maven-plugin/blob/master/RELEASE_NOTES.rst#clouddocs-maven-plugin-212-july-15-2014">https://github.com/stackforge/clouddocs-maven-plugin/blob/master/RELEASE_NOTES.rst#clouddocs-maven-plugin-212-july-15-2014</a>) which enables hyphenation. To update to 2.1.2, update the <version> indicated for the plugin in the pom.xml and try out hyphenation! </div>
<div><br></div><div>__Other doc news__</div></div><div><br></div></div><div>I plan to attend the Ops Meetup in San Antonio Aug. 25-26th. More details at <a href="https://etherpad.openstack.org/p/SAT-ops-meetup">https://etherpad.openstack.org/p/SAT-ops-meetup</a>. Please let me know your Ops Docs Needs prior to or at that event.</div>
<div><br></div><div>I absolutely love this blog post by Mark McLoughlin at <a href="http://blogs.gnome.org/markmc/2014/06/06/an-ideal-openstack-developer/">http://blogs.gnome.org/markmc/2014/06/06/an-ideal-openstack-developer/</a> - an excellent example of satire and how we should all watch each other for burnout. :) Best paragraph:<br>
"And then there’s docs, always the poor forgotten child of any open source project. Yet OpenStack has some relatively awesome docs and a great team developing them. They can never hope to cope with the workload themselves, though, so they need you to pitch in and help perfect those docs in your area of expertise."</div>
<div>Great job docs team, for working so hard on docs.</div></div>