Perhaps I'm the only one, but I really don't see the logic going on here.

If you know there is a dedicated group of Lucene.net users, then how can you 
claim that the project is stagnant?
There are active questions on the list, etc and there is help commonly offered 
through the mailing lists.
>From time to time as the need arises, the lucene.net is updated (yes I know it 
>may be years between updates)... why is that necessarily bad?

Further, if Apache doesn't want to continue to host development in its current 
state, why hang on to the name instead of releasing it where it can back to 
SourceForge, or codeplex or somewhere else?  Why the iron fist regarding the 
name?  Has the Apache foundation provided some investment to the Lucene.net 
name that they need to protect?  
I understand if they don't want to host a slowly developing product, but the 
name issue has me totally confused.

Heath



-----Original Message-----
From: Grant Ingersoll [mailto:[email protected]] 
Sent: Wednesday, December 29, 2010 10:15 AM
To: [email protected]
Subject: FYI: Vote thread started on [email protected]

For those of you who have been following the threads about the status of 
Lucene.NET, as the Lucene PMC Chair, I have started the formal process for a 
PMC vote for shutting down this project due to stagnation on the development 
side, effective Jan. 31, 2011.   The thread is taking place on the 
[email protected] mailing list, which is where the PMC does most of 
it's business.  

I view this as a pretty unfortunate situation as I know there are a group of 
dedicated users in this community, but it is apparent that development has 
completely stagnated and also that the Lucene PMC as it is currently 
constituted is not interested in the .NET version of Lucene.  Should the vote 
pass, my sincere hope is there is enough galvanization within the community 
here to put together a list of committers and a proposal and go back to the 
Apache Incubator to become a standalone project governed by people who are 
interested in Lucene.NET moving forward.  If that works, we can simply migrate 
people on this list to the incubator lists.  If it doesn't work, I suspect we 
will shut down the dev mailing list and put JIRA into a read-only mode as well 
as put SVN into a read-only mode.  I am not sure what should be done w/ the 
user list, but it will likely be shut down too.

-Grant Ingersoll



Reply via email to