Open Stack

> From: John Griffith [mailto:john.griffith at solidfire.com] 
> Sent: Friday, November 09, 2012 9:19 AM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] The future of Incubation and Core

> There of course would need to be exceptions to this, for example a project that adds to the existing core projects in such
> a way that they end up relying upon it to provide their functionality.  I think a good example of this would be Keystone,
> Identity management wasn't included in my original definition because I don't think it's required to just stand up a cloud
> and have base functionality.  That being said it is a critical component, and has in essence been designed in to all of the
> core OpenStack projects.  It's the base reference implementation, whether others use it, something else or nothing it's
> been essential in our designs and infrastructure.

That is the exact essence of the term "recommended" in my proposed definition. What you consider "essential" or "required" is only one viewpoint. We've heard lots of viewpoints (operators vs. users, etc.) over the course of this discussion. What each one finds "essential" is different, and I don't think any single one is right. Given that, I think we need to leave ourselves as a community some latitude to "recommend" and give the TC the room to continue to exercise the judgment and vision that they're elected for to maximize the benefit to OpenStack in all its facets.

    - Gabriel