Open Stack

On Nov 7, 2012, at 11:47 AM, Gabriel Hurley <Gabriel.Hurley at nebula.com> wrote:

> We need to step back for a minute and question the supposition that a “non-core but blessed by OpenStack” category is benefical. I don’t believe it is.
>  <snip>
> There should be Core, and then there should be a thriving community which is supported equally by the foundation. Nothing in between. We can’t play favorites there.
>  
> I also think we’re placing too much weight on the value of CI infrastructure and release management. Projects have been doing that for themselves forever and there’s lots of free (or nearly free) services for Open Source projects readily available.
>  
> Ultimately making another category is just a way to dodge the hard issue of what is truly core. Whether core is Iaas or a viable cloud at all levels of the stack… that’s the real debate here.
>  <snip>
> Long story short, I don’t see value in creating another category; I think we need to fundamentally define Core, let things be in or out, and then devote the foundation’s resources to supporting the *entire* ecosystem, not just a handful of projects.


This is very well put, and I agree completely.

Is core for infrastructure projects only or should it include more of the full platform projects? I believe OpenStack Core should be defined by basic infrastructure projects. You can compute, store, and move data. Those are the things that should be represented as core projects.

--John



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4329 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121107/4e6f1ea0/attachment.bin>