<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>My apologies to Sean, I didn't see his original post so now I have to reply to the digest. Arg. Now threading will be weird. Anyway, more below.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
5. docs-specs repository (Sean Roberts)<br>
<br>
</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Message: 5<br>
Date: Tue, 24 Jun 2014 05:07:32 +0000<br>
From: Sean Roberts <<a href="mailto:seanrob@yahoo-inc.com" target="_blank">seanrob@yahoo-inc.com</a>><br>
To: "openstack-docs >> <a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a>><br>
Subject: [Openstack-docs] docs-specs repository<br>
Message-ID: <<a href="mailto:D43988AC-DBE9-452E-9228-AAE4CC39C4F4@yahoo-inc.com" target="_blank">D43988AC-DBE9-452E-9228-AAE4CC39C4F4@yahoo-inc.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
The training-guides team has been seriously looking at using specs as a blueprint development step. After discussing the topic with Anne, we thought discussing having a program wide spec repo was a good idea.<br>
So I propose the documentation program use the repo Openstack/docs-spec. We would still create a wiki page as the starting point. The design would follow an RST template, so important bits of information do not get missed.</blockquote>
<div><br></div><div>Hopefully you can use the one I had in my post as a good starting point, thanks for taking this on. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Here are the steps the training guides project are considering. We were planning just a repo sub-directory, but that would change with the above plan.<br>
Create a Blueprint<br>
<br>
1. The blueprint is created here <a href="https://blueprints.launchpad.net/openstack-training-guides/+addspec" target="_blank">https://blueprints.launchpad.net/openstack-training-guides/+addspec</a>, only the name, title, and summary need to be filled out<br>
</blockquote><div><br></div><div>Yep. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2. Submit a spec RST patch based on the template <a href="https://github.com/openstack/training-guides/blob/master/specs/template.rst" target="_blank">https://github.com/openstack/training-guides/blob/master/specs/template.rst</a></blockquote>
<div><br></div><div>I'd prefer starting with a different template.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
3. Gerrit reviews are the debate and refinement<br></blockquote><div><br></div><div>Yes. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
4. Final RST patch either is rejected or approved<br></blockquote><div><br></div><div>We need to discuss whether a separate team can do approval on a subdirectory. Or does the doc-core team need to review all blueprints? </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
5. If the RST patch is approved, then it gets merged, the blueprint is approved, and the RST details are manually updated into the blueprint<br>
6. The blueprint can only be approved for current release<br></blockquote><div><br></div><div>Yes, good point. Also we do not track milestone releases for docs.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
7. Blueprints not approved or not implemented during a release cycle need the RST patch be resubmitted for the next cycle<br></blockquote><div><br></div><div>Agreed. </div><div><br></div><div>Thanks Sean! Sorry for my screw up!</div>
<div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
~sean<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-docs/attachments/20140624/04622fe5/attachment.html" target="_blank">http://lists.openstack.org/pipermail/openstack-docs/attachments/20140624/04622fe5/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
<br>
End of Openstack-docs Digest, Vol 24, Issue 40<br>
**********************************************<br>
</blockquote></div><br></div></div>