Hi Erik, Regarding Garrett's concern, I responded to him regarding, so therefore isn't any issue.
As for Lookout, Beagle, ets, I know for fact that Beagle, Ascirum and .Text are using dotLucene, I don't know about Lookout. Just do a Google them and you will see. As for the name of the project, I prefer Lucene.Net -- everything in the package is Lucene.Net, the project name is called dotLucene; this is inconsistent but I will take a vote on it. Regards, -- George -----Original Message----- From: Erik Hatcher [mailto:[EMAIL PROTECTED] Sent: Thursday, February 17, 2005 11:40 AM To: Lucene Developers List Subject: [VOTE] Re: Incubating Lucene.Net Lucene.Net has my +1. Other PMC members please cast your vote also. As for Garrett's concerns, it is my understanding that dotLucene is not based the previous Lucene.NET codebase. Though George mentions Lookout, Beagle, and some other projects - are these projects using the dotLucene codebase? I thought that Lookout used the previous Lucene.NET project. George - could you clarify the lineage of your project and list what projects are using it specifically? Also, perhaps we should stick with calling this dotLucene for now to avoid confusion with the other codebase. Erik On Feb 17, 2005, at 11:14 AM, George Aroush wrote: > Proposal for new project Lucene.Net (aka dotLucene) > > George Aroush -- [EMAIL PROTECTED] > > > ----------------------------------------------------------------------- > ----- > ---- > > (0) rationale > > Lucene.Net (aka dotLucene) is a source code port of Jakarta Lucene > from Java > to C#. The port is a one-to-one port of Lucene's high and low level > APIs, > public and internal APIs, and the underlying algorithms of Lucene as > well as > the index format. Every Java file released with Jakarta Lucene is > ported to > Lucene.Net C#. In addition, any index file generated with Lucene.Net > is > 100% cross compatible with Jakarta Lucene and via versa. Finally, > Lucene.Net preserves the look-and-feel of C#'s naming convention for > packages, classes, methods and documentation. > > Lucene.Net 1.4.3 is currently a six-month-old open source project, and > is > now hosted at SourceForge.net and is backed by its own non-profit > organization. Since Lucene.Net is already based on Jakarta Lucene and > thus > uses the Apache 2.0 license is therefore an appropriate candidate to be > moved to the Apache foundation. > > I anticipate that Lucene.Net will join the recently proposed > search.apache.org top-level project, with Lucene and its various ports. > > (0.1) criteria > > Community: > > Lucene.Net has an established user community. However, the development > community currently consists of primarily George Aroush, the submitter > of > this proposal. > > Core Developers: > > Currently, Lucene.Net has one active committer, George Aroush. > > Alignment: > > Lucene.Net currently users Visual Studio.Net 2003. In addition, it is > being > used by Mono. > > (0.2) warning signs > > Orphaned products: > > Lucene.Net is not an orphan. > > Inexperience with open source: > > Lucene.Net's committers are experienced with open source. > > Homogenous developers: > > Lucene.Net's committers do not all share an employer or nation. All > decisions are made openly on public mailing lists. > > Reliance on salaried developers: > > Lucene.Net has no salaried developers. > > No ties to other Apache products: > > Lucene.Net has strong ties to Lucene. > > A fascination with the Apache brand: > > Lucene.Net has a strong brand already. It has followers and projects > based > on it such as Lookout, .Text, Beagle and Ascirum. > > (1) scope of the subprojects > > All code is currently licensed under the same license as Jakarta Lucene > which is Apache 2.0 license. I have not yet signed the Contributor > License > Agreements but I look forward to it. > > (3) identify the ASF resources to be created > > (3.1) mailing list(s) > > Same as Jakarta Lucene > > (3.2) Subversion or CVS repositories > > TBD > > (3.3) Jira > > TBD > > (4) identify the initial set of committers > > Same as Jakarta Lucene. > > (5) identify apache sponsoring individual > > Erik Hatcher, Doug Cutting, and Otis Gospodnetic. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]