RE: Lucene.NET Community Status

Josh Handel <[email protected]>
Newsgroups gmane.comp.jakarta.lucene.net.user,gmane.comp.jakarta.lucene.net.devel,gmane.comp.apache.commons.general
Message-ID <6BF736603DBFD04FB97F35886CABF5B98A9C770C@CATINEXC04.catapultsystems.com>
A better way to put that is.. Thank you for the background, we would hate to repeat history due to being un-aware of it.. 

Now to returned to our regularly scheduled repeat of history (new and improved with "informed" action :-P).

Josh

-----Original Message-----
From: Granroth, Neal V. [mailto:[email protected]] 
Sent: Tuesday, November 02, 2010 12:21 PM
To: [email protected]; [email protected]
Cc: Lucene mailing list
Subject: RE: Lucene.NET Community Status


We've already been through this process once before.  Why repeat?
- Neal


-----Original Message-----
From: Grant Ingersoll [mailto:[email protected]] 
Sent: Sunday, October 31, 2010 6:38 AM
To: [email protected]
Cc: [email protected]; Lucene mailing list
Subject: Re: Lucene.NET Community Status


On Oct 30, 2010, at 11:07 PM, Michael Mitiaguin wrote:

> I've been using Lucene.Net since 2005 and know its history quite well. Just
> some comments :
> 
> 1.  What actually PMC expects ?

At this point, I think the PMC expects to see a plan and action for either going back to Incubation and becoming a standalone project or going to the Attic and then being maintained elsewhere. In either case, it is clear that it is in the best interest of the .NET community to have some self-determination.

Based on the messages here, I think you have enough volunteers to go back to the Incubator and try again.  I would suggest one of you volunteers browses over to http://incubator.apache.org and take a look at what it means to put together an entry proposal (basically, you need a Wiki page outlining the proposal) and then solicit mentors/champions on [email protected] and then call a vote.

-Grant
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.