openstack-poc team mailing list archive

[Jay Pipes <jaypipes@xxxxxxxxx>]

On 05/03/2012 04:08 AM, Thierry Carrez wrote:
> Joshua McKenty wrote:
> > I'm a fan of c), where the "officialness" is tied to a committed
> > organization or team that is keeping the code up-to-date and tested. I'd
> > also be a fan of making that a per-release designation, with an easy
> > renewal if the commitment is still in place.
> >
> > Generally, a smaller core with a "supported" status for satellite
> > projects is my favorite model, for much of OpenStack development.
>
> I don't have very strong feelings on that subject. My gut feeling would
> be to support (c), but I could be convinced by a strong argument why we
> shouldn't.

I feel the same way. (c) sounds good, but I'm not married to it...

> If that's the decision we end up taking, the PPB discussion quickly
> shifts to defining the taxonomy of OpenStack projects. On this subject
> and others that were raised at the Design Summit (like plug-ins),
> Core/Incubated/Other doesn't really cut it anymore. In particular I'd
> like to have at least one category for projects that are essential to
> the OpenStack development community but should not be part of the
> OpenStack core "product" (the IaaS stack of projects with a coordinated
> release every 6 months).
>
> Openstack-common, openstack-ci, or things we gate the core product on
> (devstack, tempest) should never be part of OpenStack Core (or ever be
> incubated to become core). However they are necessary for us to produce
> OpenStack core, and require our collective attention and support. So
> they need to be blessed in some kind of "official" category meaning they
> are an central part of "OpenStack" as a development community. Maybe
> "OpenStack Companion project"...

I don't necessarily view openstack-ci and openstack-common in the same 
vein. I think openstack-common actually should be part of core since it 
is an important dependency for so many of the core projects (and 
becoming more so...). Openstack-ci, tempest and devstack are also 
critical pieces, but they are support projects, not necessarily 
dependencies. So I would categorize them as "OpenStack Supporting 
Projects" or similar.

> Another category could be necessary to describe external
> projects/plug-ins that are continuously tested with OpenStack Core as
> part of our integration testing and for which we therefore have a pretty
> good idea of how well they work with OpenStack. Choosing the right term
> is a bit more tricky here since most names are a bit overloaded. Maybe
> "OpenStack recommended project/plugin"...

The term "recommended" comes with a lot of baggage :) I don't want 
plugins to be recommended or suggested -- at least by the community; 
companies should feel free to recommend or suggest whatever they feel is 
best for their distro or deployment. I just want a category called 
"OpenStack Extensions" (or Plugins, depending on what the 
semantics-du-jour happen to be.

Best,
-jay