Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAPzejYjiHxoQELGt2sSdFVmehq=Wx=ZYQhabCAtWiouqMiRHQg@mail.gmail.com>
References: 
 <CAP-ksojc2_cxv4Qf30zRAi70vxKkO6VHSiOFZZJNCiFe3quLQQ@mail.gmail.com>
	<CAPzejYjiHxoQELGt2sSdFVmehq=Wx=ZYQhabCAtWiouqMiRHQg@mail.gmail.com>
Date: Tue, 29 May 2012 12:13:33 -0400
Message-ID: 
 <CAP-ksoj1_MnY1fGsh8-b93kmjAZY4TwN2POzkRa54==utHAojQ@mail.gmail.com>
Subject: Re: [PROPOSAL] Starting the graduation process
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, May 29, 2012 at 11:42 AM, Yong Lin Ma <mayongl@apache.org> wrote:
> We are close to starting the graduation process. But I think we need
> give the project more time to demonstrate the ability to
>
> Create an Apache Release
> AOO 3.4 is an real achievement. But the major issue it solved are due
> to legal concerns. =C2=A0It has improvement in SVG just because we are
> lucky to have Armin with us.
> It is still early to say that the project is ready to get to next release=
.
> We need at least
> Close a couple of new feature cycles. Propose and discuss about new
> features -> spec review -> design review -> implementation -> QE sign
> off
> See a steady defect fix rate.

I think you misunderstand what Apache Incubation is.   There is no
requirement that we first establish a "steady defect rate" or show
that we have a process for design reviews, or any other such project
technical concerns.

The two primary goals of incubation are:

1) Ensure the initial code contribution is reviewed and brought into
conformance with Apache policy.  We did that.

2) Ensure that the community is working well, per The Apache Way and
other relevant Apache guidelines and policies.   We're doing that.

With healthy code and a healthy community we'll naturally develop
additional processes within the project.  That is a normal evolution
and part of any Top Level Project at Apache.

>
>
> Create an Open and Diverse community
> We need more committers. There still no committer from C2SC.
>

Are there any contributions yet from C2SC?  If there are, then by all
means, review them and if they are of good quality, then propose them
for becoming committers.  It would be a graduation issue if we had
volunteers making sustained contributions but we failed to make them
committers.  That would mean we were not open.  But I don't see that
happening.

>
> On Tue, May 29, 2012 at 2:10 AM, Rob Weir <robweir@apache.org> wrote:
>> I'd like to start the graduation process, with the aim of being a TLP
>> in time for the 3.4.1 release.
>>
>> The IPMC has a "Guide to Successful Graduation" page with a lot of
>> detail and advice: =C2=A0http://incubator.apache.org/guides/graduation.h=
tml
>>
>> The calendar here is especially useful:
>> http://incubator.apache.org/guides/graduation.html#toplevel
>>
>> It shows 4 steps:
>>
>> 1) a vote on ooo-dev (a community vote) on whether we want to graduate n=
ow
>>
>> 2) a discussion on ooo-dev leading to the draft of a charter for the new=
 TLP
>>
>> 3) an IPMC vote on whether or not to recommend the podling for graduatio=
n
>>
>> 4) a vote by the ASF Board on a resolution creating the new TLP
>>
>> This thread is just a proposal. =C2=A0It is not the actual vote called f=
or
>> in #1 above. =C2=A0But I'd like to gauge current sentiment. =C2=A0Are we=
 all +1
>> for going ahead? =C2=A0If not, please list what pre-graduation tasks you
>> believe need to be done first.
>>
>> Thanks!
>>
>> -Rob