[openstack-dev] [Nova] Updates to Juno blueprint review process

Tim Bell Tim.Bell at cern.ch
Fri Mar 21 19:16:05 UTC 2014

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 (https://etherpad.openstack.org/p/operators-feedback-mar14) 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. 

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.

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 ?


> -----Original Message-----
> From: Stefano Maffulli [mailto:stefano at openstack.org]
> Sent: 21 March 2014 19:55
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Updates to Juno blueprint review process
> On 03/20/2014 03:50 PM, Jay Lau wrote:
> > It is better that we can have some diagram workflow just like
> > Gerrit_Workflow <https://wiki.openstack.org/wiki/Gerrit_Workflow> to
> > show the new process.
> Indeed, I think it would help.
> While I'm here, and for the records, I think that creating a new workflow 'temporarily' only until we have Storyboard usable, is a
> *huge* mistake. It seems to me that you're ignoring or at least underestimating the amount of *people* that will need to be
> retrained, the amount of documentation that need to be fixed/adjusted. And the confusion that this will create on the 'long tail'
> developers.
> 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
> 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
> were you, I'd focus on getting storyboard ready to use asap, instead.
> There, I said it, and I'm now going back to my cave.
> .stef
> --
> Ask and answer questions on https://ask.openstack.org
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list