Having seen this burst of activity my observation is - if it is not going to be one man effort ( initial port ) the discussion in email list format becomes a bit unmanageable. The project needs a manager ( ideally also a strategic thinker technologically - i.e. a team leader ) who determines a general direction which could be discussed between volunteers ( let's say in Skype meeting ) with assigning roles to avoid the same work. I would split the current situation on two directions :
1. Releasing 2.9.2 ( potentially 2.9.3 bug fixes ) and on-going web sites activities to comply with what required by PMC . Eventually this branch will be coming to the end , as I am not sure whether Java 2.9.4 is going to be ever released. 2. Deciding what to do and assigning roles with 3.0.2 My undestanding line by line port of 3.0.2 will break existing clients ( unless they are web service consumers ) anyway , as generics ( introduced in Java ) will require upgrade at least to .Net 2 apart from methods marked as obsolete in 2.9.2 ( if used ) won't compile in 3.0.2 Perhaps, PMC would be kind enough to give some hints how to manage open source projects with multiple developers , especially at initial stage. Personally, I see 2 as initial stage where making a right decision after some trial and error ( either existing way to be used/modified or new one devised ) is very important. Michael On Wed, Nov 3, 2010 at 3:05 PM, George Aroush <geo...@aroush.net> wrote: > Hi Everyone, > > > > 3) .NET'fying Lucene.Net: If you really want this, just start a new > project > at ASF or someone where else. I really don't see Lucene.Net achieving this > anytime soon per reasons that I pointed out earlier and over the years on > this mailing list. If you start such a project, it shouldn't be called > Lucene.Net because that new project will produce a C# Lucene which is no > longer compatible with existing Lucene.Net clients as the public API will > now diverge. In addition, you will also lose, based on how deep .NET'es > you > make your Lucene, existing available resources about Lucene (web, books, > mailing list, etc). You will also need good knowledge of search engines, > and the internals of Lucene to make this happen. > > > >
