On 10/24/2013 11:32 AM, Thierry Carrez wrote:
> Russell Bryant wrote:
>> At the last Nova meeting we started talking about some updates to the
>> Nova blueprint process for the Icehouse cycle.  I had hoped we could
>> talk about and finalize this in a Nova design summit session on "Nova
>> Project Structure and Process" [1], but I think we need to push forward
>> on finalizing this as soon as possible so that it doesn't block current
>> work being done.
>>
>> Here is a first cut at the process.  Let me know what you think is
>> missing or should change.  I'll get the result of this thread posted on
>> the wiki.
>> [...]
> 
> +1
> 
> That's pretty much how I would like every project to handle their
> blueprints. For smaller projects I guess the "2 core signed up for
>> =Medium blueprints" requirement can be handled informally, but the rest
> is spot-on and should be applicable everywhere.
> 

If that's the case, then I can just work on updating the main Blueprints
page [1] with a little bit more detail.  I suppose there's not that much
missing.  In particular, I would add:

 - notes on blueprint review criteria

 - the use of -driver teams by some projects to review

 - some more info on prioriization based on review bandwidth, and nova's
specific requirement for reviewer support for a priority > Low

[1] https://wiki.openstack.org/wiki/Blueprints

-- 
Russell Bryant

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to