incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject Re: Ruby Lucene port - directly under Lucene TLP?
Date Thu, 17 Mar 2005 11:35:28 GMT
At least two of the developers (myself and Brian McCallister) for the 
port of the Java Lucene to Ruby are already official Apache committers. 
  Brian is new to the Lucene development community, but a seasoned 
Apache guy.

My preference would be to get the other developers as committers to a 
/ruby tree under and start the project there rather 
than come through incubation.  Are there any reasons why we should come 
through the incubator in this case?


On Mar 16, 2005, at 11:22 PM, Cliff Schmidt wrote:

> 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:
> For additional commands, e-mail:

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

View raw message