[openstack-dev] Avoiding regression in project governance

James E. Blair corvus at inaugust.com
Tue Mar 10 22:23:33 UTC 2015

Russell Bryant <rbryant at redhat.com> writes:

> Part of the change is to recognize more projects as being part of the
> OpenStack community.  Another critical part was replacing the integrated
> release with a set of tags.  A project would be given a tag if it meets
> some defined set of criteria.
> I can't think of any good reason to rush into approving projects in the
> short term.  If we're not able to work out this rich tagging system in a
> reasonable amount of time, then maybe the whole approach is broken and
> we need to rethink the whole approach.

I agree that we should not rush into things if we are not ready.
However, I do think we can proceed carefully with new applications.

I believe that the new project requirements as currently written
adequately express the desire in our community to be inclusive of new
projects and have a low barrier for entry into the community.  It
removes quite a bit of process overhead and TC bottlenecks.  I'm
particularly enthused that it helps projects grow up as part of the
OpenStack community instead of demanding that they show up fully-formed.

I agree that this will create a sea of projects that will be hard to
navigate.  We knew that, and to some extent, that is part of the intent.
The next step, as is pointed out, is that we need tools to help

For the moment, our idea for that is tags (while we had a serious
conversation about whether they are needed at all, we are still
proceeding with them).

The holy grail of this system would be the "suitable for production
deployment" tag, but no one has figured out how to define it yet.

In the mean time, many of the things that are coming up could very
easily be described automatically (by tags or otherwise) -- contributor
diversity, community size, development history, etc.  We should note
these and start the process of surfacing those criteria where useful.

But all is not lost -- we do have one tag already -- the current
integrated release, and it's not going anywhere just yet.  I think we
can start to approve new projects, begin to describe them in ways that
make sense as we see what would be helpful, and rely on the existing
list of integrated projects as our signal of what is most important
right now.


More information about the OpenStack-dev mailing list