incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: [PROPOSAL] Commons Incubator
Date Fri, 10 Apr 2009 10:32:11 GMT
Well, the point is: we are  talking about small libraries.

Imagine there is library X which was developed by only 2 developers.
They want to bring this code to Commons. What to do? IP clearance is
one thing. But what about the 2 developers? Just make them committers
while they have no clue about Apache? Doesn't sound like a good idea.
Just accepting their code and make them send patches until we feel
they are ready? Feels not appropriate since they are the authors of
the code. On the other hand going through the "normal" incubator is a
bit over the top for a project that is so small that it is not
targeting to become it's own project. Building a community is not
really that applicable in this case. It's rather about integrating it
into an existing community.


On Fri, Apr 10, 2009 at 08:59, Niclas Hedhman <> wrote:
> On Fri, Apr 10, 2009 at 11:59 AM, Justin Erenkrantz
> <> wrote:
>> On Thu, Apr 9, 2009 at 9:23 AM, Matt Benson <> wrote:
>>> The Commons Incubator would act as a "perpetual podling" or "mini-Incubator"
overseeing the influx of components to be adopted into Apache Commons.
>> -1 (vote, not veto).
>> If Commons PMC wants to import code, then it can file IP clearances.
>> If it wants to incubate communities, then it needs to follow the rest
>> of the Incubator procedures.  -- justin
> I'm also thinking like Justin. Incubator is all about community
> incubation and 'training' the new group of people the ApacheWay. If
> you take that out of the equation, why do you need Incubator at all.
> Be a bit more agile in IP Clearances directly into your 'sandbox' and
> take it from there...
> Cheers
> --
> Niclas Hedhman, Software Developer
> - New Energy for Java
> I  live here;
> I  work here;
> I relax here;
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message