On Wed, Feb 13, 2013 at 10:49 AM, Sebastien Goasguen <run...@gmail.com> wrote:
>
> On Feb 13, 2013, at 4:43 PM, David Nalley <da...@gnsa.us> wrote:
>
>> On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers
>> <chip.child...@sungard.com> wrote:
>>> On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote:
>>>> On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers
>>>> <chip.child...@sungard.com> wrote:
>>>>> Hi all,
>>>>>
>>>>> I started a conversation within cloudstack-private@i.a.o about the
>>>>> prospect of graduation from the incubator, and have received positive
>>>>> reactions from everyone that replied.
>>>>>
>>>>> I wanted to kick off the discussion here on the public list, to see if
>>>>> anyone has any concerns or objections to us starting down the path of
>>>>> trying to graduate?
>>>>>
>>>>> My general impression is that we have come a long way as a community
>>>>> since CloudStack entered the incubator. While there are still rough edges
>>>>> for us to work through over time, we are dealing with our problems quite
>>>>> well as a community. The simple reason that I believe we are in a
>>>>> position to ask to graduate, is that we are no longer getting value from
>>>>> the incubation process!  That's a good thing, because it means that we
>>>>> have managed to learn quite a bit about the ASF processes, rules,
>>>>> methods and preferences.
>>>>>
>>>>> Thoughts, comments, discussion?
>
> Are you thinking to do this prior to 4.2 release ?
>
> With my individual hat on, I think it might be best to put up a strong 4.2 
> release and then vote for graduation. It would strengthen our case.
>


So I had similar thoughts originally and actually meant 4.2.

Here is what changed my mind:

I don't see us actively receiving any benefit from continuing in
incubation. We are far from perfect, but the project seems to be
policing itself. so I am not seeing a huge incentive to staying.

There are also some downsides to remaining in incubation. First
there's the label 'incubation' that follows almost everything we do,
and is potentially off-putting to potential community members. Second
as a community there are a number of things we can't do for ourselves,
and thus have to ask permission or for help - this includes votes on
releases, creating new user accounts, etc. I think of this as the
overhead of being in the incubator.

And finally, while this isn't really a big deal from our perspective,
we have 8 mentors, and their continued focus on us means more of their
time they can't focus on other incubating projects. And given our -dev
list volume, I imagine us to be a handful to keep up with.

--David

Reply via email to