incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <>
Subject Re: [PROPOSAL] Incubate JSecurity Project
Date Sun, 01 Jun 2008 19:29:28 GMT
On Sun, Jun 1, 2008 at 2:52 PM, Craig L Russell <>

> On Jun 1, 2008, at 10:53 AM, Alan D. Cabrera wrote:
>> On May 31, 2008, at 7:27 PM, Craig L Russell wrote:
>>  I've signed on to mentor this project.
>> Great!
>>  Maybe there is a "fast track" through the incubator, and this is a good
>>> project to try it out. Can JSecurity get graduated in six months?
>> IIUC, all incubator projects are on the "fast track".
> Well, there is a big difference between entry and exit criteria for the
> incubator. Many projects entering incubation need to resolve IP issues,
> build a community, and learn how to work in open source. So, no, I don't
> think all projects are on the fast track.

It's all up to the community.  They're in charge of their destiny and it's
up to them to achieve what is required for graduation.

Bottom line, the podling must meet the Apache Incubator's criteria.  If that
occurs quickly then wonderful, if not, then it may take some more time to
cook.  It may never graduate at all if the criteria are not met and the
right community does not gel.  Furthermore, the project may decide down the
road that the Apache Way may not be the best way for them.  Who knows?  Even
with our easiest incubation (Wicket I think) we were hopeful at the start
but you just never know how long this will take.

Healthy stable communities form like a fine wine and rushing graduation is
like rushing the fermentation process.  It takes a while to get there but
when we do we've got a gem.  Regardless though, let's not impose artificial
time frames on increasing or decreasing the incubation time. Let's just get
on with meeting the criteria for graduation.  That's the best that we can

>  I personally like to see one release under incubation to see the podling
>> in action.
> And most incubator folks agree.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message