<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 21, 2014 at 12:16 PM, Tim Bell <span dir="ltr"><<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
I am a strong advocate of the Blueprint-on-Blueprints process we discussed in the operator mini-summit so that experienced cloud administrators can give input before lots of code is written (<a href="https://etherpad.openstack.org/p/operators-feedback-mar14" target="_blank">https://etherpad.openstack.org/p/operators-feedback-mar14</a>) but we need to be aware that these people with real life experience of the impact of changes on production clouds may not be working with gerrit day-to-day.<br>
<br>
There has been some excellent work by the documentation team in the past year to make it easy for new contributors to work on improvements to the documentation which also helps to introduce the tools/processes to the novices.<br>
<br>
Can we find a way to keep the bar low for the review of blueprints while at the same time making sure we engage the full community spectrum in the future direction of OpenStack ?<br>
<span class=""><font color="#888888"><br></font></span></blockquote><div><br></div><div>A lot of work has gone into making code review have a very low barrier to entry, the nova-specs uses the same process.</div><div> </div>
<div>Going through the etherpad list I think we hit almost everything.</div><div><br></div><div><div id="magicdomid23" class="" style="margin:0px;padding:0px;color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:12px;line-height:16px">
<ol start="1" class="" style="margin:0px;padding:0px"><li style="margin:0px;padding:0px;display:inline"><span class="" style="margin:0px;padding:0px 0px 1px;background-color:rgb(255,227,227)">Operator Review of new features - Blueprint on Blueprints (aka BOB) - aim: apply a consistent operational view to all the things</span></li>
</ol></div><div id="magicdomid24" class="" style="margin:0px;padding:0px;color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:12px;line-height:16px"><ol start="1" class="" style="margin:0px;padding:0px;text-indent:10px">
<li style="margin:0px;padding:0px;display:inline"><span class="" style="margin:0px;padding:0px 0px 1px;background-color:rgb(255,227,227)">Specific information put into blueprints</span></li><li style="margin:0px;padding:0px;display:inline">
</li><li> <a href="http://git.openstack.org/cgit/openstack/nova-specs/tree/template.rst">http://git.openstack.org/cgit/openstack/nova-specs/tree/template.rst</a></li></ol></div><div id="magicdomid25" class="" style="margin:0px;padding:0px">
<ol start="2" class="" style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:12px;line-height:16px;margin:0px;padding:0px;text-indent:10px"><li style="margin:0px;padding:0px;display:inline"><span class="" style="margin:0px;padding:0px 0px 1px;background-color:rgb(255,227,227)">Blueprint alerts</span></li>
</ol><ol start="2" class="" style="margin:0px;padding:0px;text-indent:10px"><font color="#000000" face="Arial, sans-serif"><span style="font-size:12px;line-height:16px"> Use gerrit to watch the nova-specs repo using <a href="https://review.openstack.org/#/settings/projects">https://review.openstack.org/#/settings/projects</a>. This will let you get emails every time a new BP is posted</span></font><br>
</ol></div><div id="magicdomid26" class="" style="margin:0px;padding:0px;color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:12px;line-height:16px"><ol start="3" class="" style="margin:0px;padding:0px;text-indent:10px">
<li style="margin:0px;padding:0px;display:inline"><span class="" style="margin:0px;padding:0px 0px 1px;background-color:rgb(255,227,227)">Operators in design summit sessions</span></li><li style="margin:0px;padding:0px;display:inline">
<ol start="3" class="" style="margin:0px;padding:0px;text-indent:10px"><li style="margin:0px;padding:0px;display:inline"><span class="" style="margin:0px;padding:0px 0px 1px;background-color:rgb(255,227,227)"> </span></li>
Not sure what the blockers are on this one. nova-specs doesn't directly relate to to the summit.</ol></li></ol></div><div id="magicdomid27" class="" style="margin:0px;padding:0px"><ol start="4" class="" style="margin:0px;padding:0px;text-indent:10px">
<li style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:12px;line-height:16px;margin:0px;padding:0px;display:inline"><span class="" style="margin:0px;padding:0px 0px 1px;background-color:rgb(188,236,200)">BluePrint Review Process (gerrit?)</span></li>
<font color="#000000" face="Arial, sans-serif"><span style="font-size:12px;line-height:16px"><li style="margin:0px;padding:0px;display:inline"></li></span></font><li><div id="magicdomid25" class="" style="text-indent:0px;margin:0px;padding:0px">
<ol start="2" class="" style="margin:0px;padding:0px;text-indent:10px"><font color="#000000" face="Arial, sans-serif"><span style="font-size:12px;line-height:16px"> </span></font><a href="https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z">https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z</a><br>
</ol></div></li></ol></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><font color="#888888">
Tim<br>
</font></span><div class=""><div class="h5"><br>
> -----Original Message-----<br>
> From: Stefano Maffulli [mailto:<a href="mailto:stefano@openstack.org">stefano@openstack.org</a>]<br>
> Sent: 21 March 2014 19:55<br>
> To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
> Subject: Re: [openstack-dev] [Nova] Updates to Juno blueprint review process<br>
><br>
> On 03/20/2014 03:50 PM, Jay Lau wrote:<br>
> > It is better that we can have some diagram workflow just like<br>
> > Gerrit_Workflow <<a href="https://wiki.openstack.org/wiki/Gerrit_Workflow" target="_blank">https://wiki.openstack.org/wiki/Gerrit_Workflow</a>> to<br>
> > show the new process.<br>
><br>
> Indeed, I think it would help.<br>
><br>
> While I'm here, and for the records, I think that creating a new workflow 'temporarily' only until we have Storyboard usable, is a<br>
> *huge* mistake. It seems to me that you're ignoring or at least underestimating the amount of *people* that will need to be<br>
> retrained, the amount of documentation that need to be fixed/adjusted. And the confusion that this will create on the 'long tail'<br>
> developers.<br>
><br>
> A change like this, done with a couple of announcements on a mailing list and a few mentions on IRC is not enough to steer the ~400<br>
> developers who may be affected by this change. And then we'll have to manage the change again when we switch to Storyboard. If I<br>
> were you, I'd focus on getting storyboard ready to use asap, instead.<br>
><br>
> There, I said it, and I'm now going back to my cave.<br>
><br>
> .stef<br>
><br>
> --<br>
> Ask and answer questions on <a href="https://ask.openstack.org" target="_blank">https://ask.openstack.org</a><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>