[openstack-dev] RFC: Basic definition of OpenStack Programs and first batch

John Dickinson me at not.mn
Mon Jul 1 19:46:47 UTC 2013

I really like the Solution 2 proposal.

On Jul 1, 2013, at 12:32 PM, Thierry Carrez <thierry at openstack.org> wrote:

> Thierry Carrez wrote:
> Solution (2) is to make everything a "Program". Some have a goal of
> producing an 'integrated' piece and those must go through incubation.
> Something like:
> """
> 'OpenStack Programs' are efforts which are essential to the completion
> of our mission. Programs can create any code repository and produce any
> deliverable they deem necessary to achieve their goals.
> Programs are placed under the oversight of the Technical Committee, and
> contributing to one of their code repositories grants you ATC status.
> Current efforts or teams which want to be recognized as an 'OpenStack
> Program' should place a request to the Technical Committee, including a
> clear mission statement describing how they help the OpenStack general
> mission and how that effort is essential to the completion of our
> mission. Only programs which have a goal that includes the production of
> a server 'integrated' deliverable need to go through an Incubation period.
> The initial Programs are 'Nova', 'Swift', 'Cinder', 'Neutron',
> 'Horizon', 'Glance', 'Keystone', 'Heat', 'Ceilometer', 'Documentation',
> 'Infrastructure', 'QA' and 'Oslo'. 'Trove' and 'Ironic' are in
> incubation. Those programs should retroactively submit a mission
> statement and initial lead designation, if they don't have one already.
> """
> In that scenario, we could also name them "Official Teams"... because
> that's the central piece.
> -- 
> Thierry Carrez (ttx)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4082 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130701/e7b1d510/attachment.bin>

More information about the OpenStack-dev mailing list