<div dir="ltr">
<p class="">Here are six things you want to know from OpenStack doc-land. </p><p class="">I've cross posted to openstack-docs and openstack-dev, so please reply only to the openstack-docs list with any questions or feedback.</p>
<p class="">We had our team meeting this week, and you can read the log and minutes at <a href="https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2013-08-13">https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2013-08-13</a>.</p>
<p class="">1. In review and merged this past week:</p>
<p class="">We've had nearly 100 patches merged in the last two weeks including some changes to the way the validation script works. I know this caused some churn and consternation, sorry about that. But I do believe the tidying of the markup will make the docs more consistent and easier to walk up to and change. </p>
<p class="">Cleanup is all good but we do want more doc bug fixing. Many bugs were fixed (like over 20) with the autodoc work. However there are many bugs from DocImpact. Which leads me to the high priority doc work.</p>
<p class="">2. High priority doc work:</p>
<p class=""><a href="https://launchpad.net/openstack-manuals/+milestone/havana">https://launchpad.net/openstack-manuals/+milestone/havana</a> is the list of doc bugs and blueprints we're focusing on for the Havana release. Feature freeze is Sept 5th for all the projects. We need to have the repos ready for bug fixing. </p>
<p class="">I've directed Shaun McCance, contractor at Cisco, to get a draft for the Install Guide going. The draft architectures are here: <a href="https://etherpad.openstack.org/havanainstall">https://etherpad.openstack.org/havanainstall</a>. </p>
<p class="">I am meeting with the teams at their weekly meetings or PTLs individually to determine what happens to the Administration Guides. Our initial analysis shows that much content moves to the Configuration Reference and Admin User Guide. I'll talk to each team about the net changes there.<br>
</p>
<p class="">3. Doc work going on that I know of:</p>
<p class="">Diane Fleming is working on a new Admin User Guide currently. </p><p class="">The review queue has lots of markup changes, refer to <a href="http://wiki.openstack.org/Documentation/Conventions">http://wiki.openstack.org/Documentation/Conventions</a> to see what markup is correct.<br>
</p><p class="">The Compute v3 API documentation is being sourced by IBM and the docs team is ready to help as needed.</p>
<p class="">4. New incoming doc requests:</p>
<p class="">I talked with representatives from the Heat team last week about a Template guide, and it looks like someone wrote it - - great! </p>
<p class="">5. Doc tools updates:</p>
The Maven plugin that builds our docs is sourced at <a href="https://github.com/rackerlabs/clouddocs-maven-plugin">https://github.com/rackerlabs/clouddocs-maven-plugin</a> and just released version 1.9.0. <div><br></div>
<div>Our pom.xml files still point to 1.8.0 but we could start testing 1.9.0 which adds supports for olinks. By using olinks instead of our current linking with xrefs would prevent Oxygen from showing non-valid file warnings in individual chapter files and adds an easier interface for finding cross-reference links. David Cramer can demo at the Boot Camp, and then we'll need to make decisions about how much cross-referencing we want. With fewer books going to a "released" docs site, we may want to limit the use of cross-references altogether, but let's discuss in person. Our current linking conventions are here: <a href="https://wiki.openstack.org/wiki/Documentation/Conventions#Linking">https://wiki.openstack.org/wiki/Documentation/Conventions#Linking</a>.<div>
<div><br></div><div>Another addition for 1.9.0 is adding parameter style and type to the <a href="http://api.openstack.org/api_ref.html">http://api.openstack.org/api_ref.html</a> page. Review for testing at <a href="https://review.openstack.org/42011">https://review.openstack.org/42011</a>.
<p class="">6. Other doc news:</p><p class="">Docs Boot Camp is less than a month away and Tom, Nick, Shaun and I are working on the details. We should have over 20 attendees, and more than half are quite new to docs. Looking forward to it!</p>
<p class="">Nick Chase at Mirantis is finalizing a "how to contribute" guide for docs and hopefully we can go over it at the Doc Boot Camp. <br></p><p class="">Any other exciting doc news to share? Let us know at <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>.</p>
<p class="">Thanks,</p><p class="">Anne</p></div></div></div></div>