[openstack-dev] The future of Incubation and Core

Russell Bryant rbryant at redhat.com
Thu Nov 8 15:37:20 UTC 2012


On 11/08/2012 07:53 AM, Thierry Carrez wrote:
> Mark McLoughlin wrote:
>> I think too much of this discussion has been about the fairly arbitrary
>> names we have for different classes of projects. The term "Core" isn't
>> actually all that useful to us in the discussion, or more generally,
>> because everyone has their own idea of what the term means.
>>
>> There are two important things being discussed here - our vision for the
>> coordinated OpenStack releases and the rules around the use of the
>> OpenStack trademark.
> 
> Agreed, that's what I was hinting at in my (admittedly convoluted)
> summary. We need to define the set of projects we want to release in a
> coordinated fashion. What name(s) we put on them is more of a trademark
> question.
> 
> For example, I suspect everyone agrees Keystone needs to be part of the
> coordinated release, whereas if "core" ends up designating pure IaaS
> services, Keystone would not be part of it.
> 
> In that sense, the "core+supported" and an inclusive "product core"
> options end up covering the same set of projects, as far as coordinated
> release goes.
> 
> Incubation would be the process to become part of the coordinated
> release, whatever label the project ends up carrying. And the labels
> should be defined by the trademark rules ("You need to run all label1
> projects to be called an openstack cloud").

I like all of this and I'd be happy with either option 1
(core+supported) and 2 (product core) since they're just variations on a
theme of a fairly inclusive coordinated release.

> We just need to find a name to represent the whole group of "projects
> that are part of the coordinated release", just in case "Core" ends up
> designating a different thing.

How about the "OpenStack Collection".  The OpenStack Collection would be
the set of all projects delivered as a part of a coordinated release.
Subsets of the OpenStack Collection could carry labels that define what
is required to be an "OpenStack Cloud" (or whatever else comes up).

-- 
Russell Bryant



More information about the OpenStack-dev mailing list