<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div id="yiv7588861668" class="" style=""><div class="" style=""><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt;" class=""><div id="yiv7588861668yui_3_16_0_19_1403715950625_4" class="" style="">As a parallel thread to Anne's doc-specs repo, I propose that we start with the neutron spec template.rst and skeleton.rst found here <a href="https://github.com/openstack/neutron-specs/tree/master/specs" class="" style="">https://github.com/openstack/neutron-specs/tree/master/specs</a>. We would remove the REST API impact, security, notifications, and performance impact sections. I would modify the Data Model Impact to doc/common docs Impact.</div><div id="yiv7588861668yui_3_16_0_19_1403715950625_4"
class="" style=""><br></div><div id="yiv7588861668yui_3_16_0_19_1403715950625_4" class="" style="">Once we figure out the naming bits from the other thread and the template highlights here, then an Infra patch to create the repo would be the next step.</div><div id="yiv7588861668yui_3_16_0_19_1403715950625_6" class="" style=""></div><div id="yiv7588861668yui_3_16_0_19_1403715950625_8" class="" style=""> </div><div id="yiv7588861668yui_3_16_0_19_1403715950625_10" class="" style=""><div class="" id="yiv7588861668yui_3_16_0_1_1403715950625_108165" style=""><b class="" style=""><br clear="none" class="" style=""></b></div><div class="" id="yiv7588861668yui_3_16_0_1_1403715950625_108166" style="font-family:arial, helvetica, clean, sans-serif;font-weight:bold;"><b class="" style="">Sean Roberts</b></div><div class="" style="">Infrastructure Strategy, Yahoo</div><div class="" style=""><span class="" style=""><a rel="nofollow" shape="rect"
ymailto="mailto:seanrob@yahoo-inc.com" target="_blank" href="mailto:seanrob@yahoo-inc.com" class="" style="">seanrob@yahoo-inc.com</a></span></div><div class="" style="">(925) 980-4729</div></div> <div class="" id="yiv7588861668yui_3_16_0_19_1403715950625_13" style="display: none;"> <div class="" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt;"> <div class="" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt;"> <div class="" id="yiv7588861668yqt48653" style=""><div dir="ltr" class="" style=""> <font size="2" face="Arial" class="" style=""> On Monday, June 23, 2014 10:11 PM, Sean Roberts <seanrob@yahoo-inc.com> wrote:<br clear="none" class="" style=""> </font> </div> <br clear="none" class="" style=""><br clear="none" class="" style=""> <div class="" style=""><div id="yiv7588861668" class="" style="">
<div class="" style="">
<div style="" class="">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. </div>
<div style="" class="">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. </div>
<div style="" class="">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. </div>
<div class="" style="">
<h4 style="margin:10px 0px;" class=""><span class="" id="yiv7588861668Create_a_Blueprint" style="">Create a Blueprint</span></h4>
<ol id="yiv7588861668yui_3_16_0_1_1403715950625_108130" style="padding:0px;margin:0.3em 0px 0px 3.2em;" class=""><li class="" style=""><span style="" class="">The blueprint is created here <a rel="nofollow" shape="rect" class="" target="_blank" href="https://blueprints.launchpad.net/openstack-training-guides/+addspec" style="text-decoration:none;cursor:pointer;background-image:url(https://wiki.openstack.org/w/skins/strapping/images/lock-icon.png);padding-right:13px;background-position:100% 50%;background-repeat:no-repeat no-repeat;">https://blueprints.launchpad.net/openstack-training-guides/+addspec</a>,
only the name, title, and summary need to be filled out</span></li><li class="" style=""><span style="" class="">Submit a spec RST patch based on the template <a rel="nofollow" shape="rect" class="" target="_blank" href="https://github.com/openstack/training-guides/blob/master/specs/template.rst" style="text-decoration:none;cursor:pointer;background-image:url(https://wiki.openstack.org/w/skins/strapping/images/lock-icon.png);padding-right:13px;background-position:100% 50%;background-repeat:no-repeat no-repeat;">https://github.com/openstack/training-guides/blob/master/specs/template.rst</a></span></li><li class="" style=""><span style="" class="">Gerrit reviews are the debate and refinement</span></li><li class="" style=""><span style="" class="">Final RST patch either is rejected or approved</span></li><li class="" style=""><span style="" class="">If the RST patch is approved, then it gets merged, the blueprint is approved, and the RST details are
manually updated into the blueprint</span></li><li class="" style=""><span style="" class="">The blueprint
can only be approved for current release</span></li><li class="" style=""><span style="" class="">Blueprints not approved or not implemented during a release cycle need the RST patch be resubmitted for the next cycle</span></li></ol>
<br clear="none" class="" style="">
<span style="" class="">~sean</span></div>
</div>
</div><br clear="none" class="" style="">_______________________________________________<br clear="none" class="" style="">Openstack-docs mailing list<br clear="none" class="" style=""><a rel="nofollow" shape="rect" ymailto="mailto:Openstack-docs@lists.openstack.org" target="_blank" href="mailto:Openstack-docs@lists.openstack.org" class="" style="">Openstack-docs@lists.openstack.org</a><br clear="none" class="" style=""><a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" class="" style="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br clear="none" class="" style=""><br clear="none" class="" style=""><br clear="none" class="" style=""></div></div> </div> </div> </div> </div></div></div></div></body></html>