<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div style="-webkit-text-size-adjust: auto;">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="-webkit-text-size-adjust: auto;">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="-webkit-text-size-adjust: auto;">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>
<h4 style="margin: 10px 0px; text-rendering: optimizelegibility;"><span class="mw-headline" id="Create_a_Blueprint" style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Create a Blueprint</span></h4>
<ol style="padding: 0px; margin: 0.3em 0px 0px 3.2em;">
<li><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">The blueprint is created here <a rel="nofollow" class="external free" 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><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Submit a spec RST patch based on the template <a rel="nofollow" class="external free" 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><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Gerrit reviews are the debate and refinement</span></li><li><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Final RST patch either is rejected or approved</span></li><li><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">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><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">The blueprint can only be approved for current release</span></li><li><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Blueprints not approved or not implemented during a release cycle need the RST patch be resubmitted for the next cycle</span></li></ol>
<br>
<span style="-webkit-text-size-adjust: auto;">~sean</span></div>
</body>
</html>