[prev in list] [next in list] [prev in thread] [next in thread] 

List:       incubator-general
Subject:    RE: Ruby Lucene port - directly under Lucene TLP?
From:       "Cliff Schmidt" <cliff () bea ! com>
Date:       2005-03-17 4:22:47
Message-ID: 4C2F1577F2EF2840A9AE9EC61860C88101CFCE7B () usseex01 ! amer ! bea ! com
[Download RAW message or body]

On Wednesday, March 16, 2005 8:05 PM, Noel J. Bergman wrote:

> > If an existing TLP, such as Lucene, wants to develop a port, such
> > as a Ruby port of the Lucene library, can the Lucene PMC invite
> > that port and its developers under its wings directly
> 
> > this port is not an existing external project, but a brand new port
> > that would be developed under Lucene from scratch by a group of 4-5
> > developers.
> 
> If you are developing this within the TLP in ASF resources (our
> mailing lists, source control, etc.), you do not come through the
> Incubator.  And if you are just talking about adding new Committers
> to an existing community, you don't need to come through the
> Incubator.  One can see that grey areas could exist.  It seems to me
> that it depends on whether you are creating a new community or are
> integrating new people into an existing one.      

I agree with everything Noel said, but I'll take a shot at further
defining the grey area.  If the port is being written by an entirely new
set of committers, without whom the port could not developed/maintained,
I would think the subproject should come through the incubator.

Cliff

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]