Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of marcus.mail@wtnet.de designates
 213.209.103.15 as permitted sender)
Message-ID: <50047728.8050308@wtnet.de>
Date: Mon, 16 Jul 2012 22:18:48 +0200
From: "Marcus (OOo)" <marcus.mail@wtnet.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de;
 rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: [DISCUSS] Are you ready to graduate?
References: 
 <CAPFNckjcR7F43Cx3yvBFGeeeapM0_D+32zkVYd7Xkndgh1_p-Q@mail.gmail.com>
 <CAP-ksoge9qa8etaKsvxKM9gdCKh-ddWWMqu6UhrPM5i4c9dvSw@mail.gmail.com>
In-Reply-To: 
 <CAP-ksoge9qa8etaKsvxKM9gdCKh-ddWWMqu6UhrPM5i4c9dvSw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Am 07/16/2012 08:57 PM, schrieb Rob Weir:
> On Mon, Jul 16, 2012 at 2:42 PM, Christian Grobmeier
> <grobmeier@gmail.com>  wrote:
>> Hello all,
>>
>> as a mentor of this project it is my impression that this podling is
>> ready to graduate.
>>
>> This is surely a project with much heat in it; but I also think it is
>> stable. The project made a release and constantly voted in new
>> committers/ppmc members. It is active and has proven that it can make
>> decisions by discussions.
>>
>> As mentors we have stepped into many discussions and told what we
>> think. But now it seems to me there is nothing we can bring to you.
>> The culture here is settled. You guys know whom to ask and where to go
>> if problems occur.
>>
>> Looking at this:
>> http://incubator.apache.org/projects/openofficeorg.html
>> it seems everything is done.
>>
>> My questions to you all as a project:
>>
>> Do you feel ready to graduate?
>> Are you able to vote a chair?
>> Do you think your project is ready?
>>
>> If you can answer all the questions above with "yes" I would love to
>> see graduation actions/discussions as mentioned here:
>> http://incubator.apache.org/guides/graduation.html
>>
>
> We discussed this in a thread a month or so ago.  I think the answer
> was yes, but with two concerns on the timing:
>
> 1) There was some category-b per-requisite components that we had in
> SVN.  At least one project member thought this needed to be done
> before graduation. The plan was to move them to Apache Extras.  But
> doing so would break the build in AOO 3.4 release.  So we agreed to
> fix this in AOO 3.4.1.
>
> 2) Some of us wanted to avoid the distraction of a graduation vote at
> the same time as the 3.4.1 release, a time when we're really
> heads-down on the release end game..  Especially if this would lead to
> disruptive naming changes that would have an impact on product UI
> and/or release communications due to changing URL's and email
> addresses, etc.
>
> So the discussion at that time was to push for AOO 3.4.1 release by
> end of July and then start the graduation proceedings.
>
> Of course, I'm not saying this is set in stone. But that was the
> outcome of the prior discussion.

I also think that this would interfer the last phase of creating and 
publishing 3.4.1 is not so good (even if graduation is of course a very 
positive event ;-) ). So +1 to wait a few weeks more when the 3.4.1 
release is done and some dust has settled.

Marcus