<div dir="ltr"><div>The doc team met this week for the APAC time zone. </div><div>Minutes: <a href="http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-02-03.06.html">http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-02-03.06.html</a></div>
<div>Log: <a href="http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-02-03.06.log.html">http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-02-03.06.log.html</a></div><div><br></div><div>
__In review and merged this past week__</div><div><br></div><div>The security guide has been removed from the openstack-manuals repo and moved to the security-doc repo.</div><div><br></div><div>The docs-specs repository is now active at <a href="https://github.com/openstack/docs-specs">https://github.com/openstack/docs-specs</a>. I'd like to see these three specs written for Juno for docs:</div>
<div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">* <a href="https://blueprints.launchpad.net/openstack-manuals/+spec/python-client-docs-for-app-devs" target="_blank">https://<span class="" style="color:rgb(34,34,34);background:rgb(255,255,204)">blueprints</span>.launchpad.net/openstack-manuals/+spec/python-client-docs-for-app-devs</a> I requested more discussion on exactly what work should be done. Tom, do you have time to write a spec? If not you, who is interested?<br>
</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">* <a href="https://blueprints.launchpad.net/openstack-manuals/+spec/redesign-docs-site" target="_blank">https://<span class="" style="color:rgb(34,34,34);background:rgb(255,255,204)">blueprints</span>.launchpad.net/openstack-manuals/+spec/redesign-docs-site</a> I plan to write a spec this once we get a web design plan laid out in more detail. <br>
</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">* <a href="https://blueprints.launchpad.net/openstack-manuals/+spec/heat-templates" target="_blank">https://<span class="" style="color:rgb(34,34,34);background:rgb(255,255,204)">blueprints</span>.launchpad.net/openstack-manuals/+spec/heat-templates</a> We've discussed a lot on the ML but it doesn't have a linked wiki page and could use further description and decisions. Gauvain, could you write a spec based on what we've discussed so far?</div>
</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">* <a href="https://blueprints.launchpad.net/openstack-manuals/+spec/create-networking-guide">https://blueprints.launchpad.net/openstack-manuals/+spec/create-networking-guide</a> We've got a lot of interest in this new book -- Lana's talking about a doc swarm around it, and Phil Hopkins and Matt Kassawara know this area. Matt or Phil, up for a doc spec for this one? </div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Training team, do you have "must have" specs to write? </div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">I think the review team for docs-specs can be as small as:</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">
Anne Gentle</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Sean Roberts</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Andreas Jaeger</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">
Bryan Payne</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">or as large as docs-core. Projects are going either way with it. Our setup is a separate team, but we can populate as we need.</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Any input on docs-specs? Please let us know.</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<br></div><div>__High priority doc work__</div><div><br></div><div>I've been fielding questions about good areas to work in the docs. I'd like these to be high priority:</div><div>- Networking in admin guide and the separate guide that needs to have a spec written</div>
<div>- Identity, especially v2 vs. v3 in the admin and ops docs</div><div>- Orchestration templates: reference inclusion and how-to information integrated in admin user guide</div><div><br></div><div>__Ongoing doc work__</div>
<div><br></div><div>We're reconsidering the priorities for web design work -- whether <a href="http://docs.openstack.org">docs.openstack.org</a> or <a href="http://developer.openstack.org">developer.openstack.org</a> needs the overhaul. So stay tuned as we work with the Foundation on the pre-work and planning.</div>
<div><br></div><div>__New incoming doc requests__</div><div><br></div><div>None this week.</div><div><br></div><div>__Doc tools updates__</div><div><br></div><div>Once this patch to oslosphinx merges, project indicate if they're incubating with a change to your sphinx conf.py, setting html_theme_options equal to <span style="color:rgb(0,0,0);font-size:9pt">{'incubating': True}'</span>. </div>
<div><a href="https://review.openstack.org/#/c/103935/">https://review.openstack.org/#/c/103935/</a><br></div><div>Thanks to Graham Hayes for that! The projects that need to set it when it's available are:</div><div>
-Designate</div>
<div>-Ironic</div><div>-Sahara</div><div>-Barbican</div><div>-Marconi</div><div><br></div><div>The latest version of openstack-doc-tools is 1.16.1 and has the latest RelaxNG schema included. </div><div><br></div><div>__Other doc news__</div>
<div><br></div><div> Still working on the naming for glance-provided services. Thierry noted today that the mission can evolve without the program name changing yet in <a href="https://review.openstack.org/#/c/98002/">https://review.openstack.org/#/c/98002/</a>. So we hope to keep looking for the right wording as the evolution happens.</div>
</div>