Open Stack

On Oct 15, 2013, at 19:18 , Duncan Thomas <duncan.thomas at gmail.com>
 wrote:

> On 13 October 2013 00:19, Alessandro Pilotti
> <apilotti at cloudbasesolutions.com> wrote:
> 
>> If you don't like any of the options that this already long thread is
>> providing, I'm absolutely open to discuss any constructive idea. But please,
>> let's get out of this awful mess.
>> 
>> OpenStack is still a young project. Let's make sure that we can hand it on
>> to the next devs generations by getting rid of these management bottlenecks
>> now!
> 
> Get a hyper-v person trained up to the point they are a nova core
> reviewer, where they can not only prioritise hyper-v related reviews
> but also reduce the general review backlog in nova (which affects
> everybody... there are a few cinder features that required nova merges
> that didn't get in before feature freeze either and had to be disabled
> in cinder).
> 

About getting a Nova core, from a previous email that I wrote on this thread:

> …
> Our domain is the area in which me and my sub-team can add the biggest value. Being also an independent startup, we reached now the stage in which we can sponsor some devs to do reviews all the time outside of our core domain, but this will take a few months spawning one or two releases as aquiring the necessary understanding of a project like e.g. Nova cannot be done overnight.
> …

Anyway, although this will help, it won't be a solution. A central control without delegation is going to fail anyway as the project size increases.


> There's a 'tax' to contributing to openstack, which is dedicating some
> time to reviewing other people's work. The more people do that, the
> faster things go for everybody. The higher rate tax is being a core
> reviewer, but that comes with certain advantages too.
> 

Here's the point. A driver dev pays this "tax" across multiple projects, e.g.: by reviewing Hyper-V code in Nova, Neutron, Cinder, Ceilometer, Cloudbase-Init, Crowbar, OpenVSwitch and so on. 
As a consequence the amount of review work in a single project will never be enough to get a core status.


> -- 
> Duncan Thomas
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev