openstack team mailing list archive

[Christian Berendt <berendt@xxxxxxxxxxxxx>]

Hello together.

> I was wondering if the community could elevate devstack to a
> "official" openstack project, instead of being a "unofficial
> project".

I think devstack.org is already some kind of official project (provided
by Rackspace Cloud Builders).

Where is the benefit of becoming a core project? At the moment I only
see a lot of overhead (release management, downstream distribution,
technical lead, feature frozen zones, ..) without any benefits.

Also it would take a lot of efforts (see [0] for details) to set up a
new core project.

Devstack is an instrument to help and improve the development. I think
a core component must have the opportunity to be used in a productive
environment and should not "only" be used to support the development.

Can you please describe in more detail what are the benefits of
becoming a core project?

An other point is that the official CI systems (and I think everybody
else, too) are using devstack.org and and that the script is doing a
well job.

You're starting two discussions in this mail: Should devstack become a
part of the core and should devstack be rewritten to Python. I think
the discussions should be splitted and I don't see any motivation of
the devstack.org developers to join the discussion of a Python rewrite
at the moment (maybe I'm wrong).

I don't find the definition and requirements of a core project at the
moment, but I'm pretty sure that there exist some documents.

Maybe it makes sense to define some kind of requirements about OpenStack
specific tools used by the official CI, but that's an other discussion.

[0] http://wiki.openstack.org/Governance/Approved/NewProjectProcess

Bye, Christian.

-- 
Christian Berendt
Linux / Unix Consultant & Developer
Mail: berendt@xxxxxxxxxxxxx

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537