openstack team mailing list archive

[Chris Bohannon <chris.bohannon@xxxxxxxxxxxxx>]

I would like to be real light on governance here. I think self-governance, especially at the beginning, is perfectly acceptable.

-Chris

-----Original Message-----
From: openstack-bounces+chris.bohannon=rackspace.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+chris.bohannon=rackspace.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jay Pipes
Sent: Friday, October 14, 2011 4:52 PM
To: Bryan Taylor
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] openstack-satellite

On Fri, Oct 14, 2011 at 3:22 PM, Bryan Taylor <btaylor@xxxxxxxxxxxxx> wrote:
> I don't know, but there are several obvious next steps:
>  - Document publicly the criteria for a project to fit

Not really sure there needs to be criteria, really...

>  - Identify resources available to participating projects

What do you mean here? Are you referring to resources in the sense of
online source control and bug tracking, etc?

>  - Formalize it with the PPB and unleash it

There is no reason to have the PPB involved in this, IMHO...

>  - Build the Satellite community

The community will grow as projects are added to the Satellite
directory and the contributors to those projects make a big deal about
directing people to the Satellite site. I think trying to force the
growth of a community specifically around Satellite is a mistake. The
OpenStack ecosystem IS the community, and attempting to create a
separate community just around Satellite projects would unnecessarily
divide the overall community...

> A big question we didn't discuss is what the governance model for Satellite
> should be. I don't necessarily think that a contributor to Satellite should
> be treated the same as a core contributor (eg: vote on the PTLs etc). But
> there may be building blocks within Satellite that need to be governed on
> their own.

I would advise NOT having any particular governance model for
Satellite projects. The projects themselves should self-govern by the
cultural norms of the programming language communities that are
relevant to the project; since Satellite projects can be anything
related to OpenStack -- just not the core reference implementations of
the OpenStack APIs -- there really shouldn't be a governance model
that attempts to control or limit this ecosystem. At least, that's
just my opinion! :)

> I think some of the standards around APIs that cut across services are
> things that Satellite contributors should have a say in. I definitely think
> things like QA and CI matter a lot (perhaps more) to Satellite.

Sure, absolutely QA and CI matter a lot to anyone that is developing
alternate implementations of OpenStack APIs (i.e. non-core
implementations) or is developing an application that consumes the
APIs. I would expect that developers of Satellite projects that depend
on stable OpenStack APIs definitely voice their needs and concerns on
the main openstack mailing list. (hint, hint!)

Cheers,
-jay

> On 10/14/2011 11:24 AM, David Medberry wrote:
>>
>> Hi,
>>
>> I've not seen anything following the ODS about OpenStack Satellite (or
>> whatever new name has been proposed).
>>
>> Is discussion going on another list?
>>
>> I also don't see an etherpad for it posted here:
>>
>> http://wiki.openstack.org/EssexSummitEtherpads
>>
>> Was the discussion captured somewhere else?
>>
>> -dave
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
> This email may include confidential information. If you received it in
> error, please delete it.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
This email may include confidential information. If you received it in error, please delete it.