Re: [openstack-dev] [Ironic] Should we adopt a blueprint design process

2014-04-18 Thread Thierry Carrez
Chris Behrens wrote: +1 FWIW we'll have a cross-project workshop at the design summit about tracking incoming features -- covering blueprint proposal, approval and prioritization. We'll discuss extending the -specs repositories experience and see how it fits the whole picture on the long run:

Re: [openstack-dev] [Ironic] Should we adopt a blueprint design process

2014-04-18 Thread Lucas Alvares Gomes
+1 for me as well, I'd like to have a better way to track incoming features. Also, as part of the migration progress I think that we need a good wiki page explaining the process of how propose a new feature, with a template of what's mandatory to fill out and what is optional. I wouldn't like to

Re: [openstack-dev] [Ironic] Should we adopt a blueprint design process

2014-04-18 Thread Vladimir Kozhukalov
+1 Great idea. many times you think that you know a way to do something but as you go you then realize that doing it in another way is much better, so I think that in order to propose a new feature we should not assume that the author knows _everything_ at the start. Absolutely agree. It would

Re: [openstack-dev] [Ironic] Should we adopt a blueprint design process

2014-04-17 Thread Kyle Mestery
On Thu, Apr 17, 2014 at 12:11 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all, The discussion of blueprint review has come up recently for several reasons, not the least of which is that I haven't yet reviewed many of the blueprints that have been filed recently. My biggest

Re: [openstack-dev] [Ironic] Should we adopt a blueprint design process

2014-04-17 Thread Russell Haering
Completely agree. We're spending too much time discussing features after they're implemented, which makes contribution more difficult for everyone. Forcing an explicit design+review process, using the same tools as we use for coding+review seems like a great idea. If it doesn't work we can

Re: [openstack-dev] [Ironic] Should we adopt a blueprint design process

2014-04-17 Thread Chris Behrens
+1 On Apr 17, 2014, at 12:27 PM, Russell Haering russellhaer...@gmail.com wrote: Completely agree. We're spending too much time discussing features after they're implemented, which makes contribution more difficult for everyone. Forcing an explicit design+review process, using the