Re: Status of Lucene.Net

Mon, 02 Jul 2007 11:19:45 -0700

Ok guys, here are some guidelines for contributing, although George may have specific guidelines for Lucene.Net.
First checkout the source with a Subversion client, I suggest TortoiseSVN. Then you need to start giving a look at the code and if the aim is to contribute upgrading Lucene.Net to the latest Java release you need to compare the changes to the classes and edit the code on your working copy (that is, the copy you've checked out on your machine). To submit modifications you need to create a patch, that is a file which contains the modifications you have made. TortoiseSVN makes this easy with the Create Patch option (right click on the folder/file containing the modifications and choose Create Patch). Once created it has to be sent to someone which has commit permission on the repository, that is, George.

These are general guidelines, check out this post (http://www.hanselman.com/blog/ExampleHowToContributeAPatchToAnOpenSourceProjectLikeDasBlog.aspx) by Scott Hanselman for more details.

Simone

Digy wrote: 
Hi George,

I use Lucene.Net in most of the projects I develop and I think I can spend
some time on its development.
So, I am ready to contribute to this project, if I can.
But, since I have never worked on an open source project like this, I don't
know what to do or how to apply.

PS: I have never developed a code in java except a "hello world" application
:-)  and can't help in java codes much.

DIGY





-----Original Message-----
From: George Aroush [mailto:[EMAIL PROTECTED]] 
Sent: Monday, July 02, 2007 4:48 PM
To: [email protected];
[EMAIL PROTECTED]
Subject: Status of Lucene.Net

Hi Folks,

It has been some time since I last posted to the Lucene.Net mailing list.

I'm glad to see there is good activities and discussion going on from the
user base community, and judging from those post, I see some new "faces".
What's even better, I see folks are jumping in and answering questions as
well as helping out.

This is all well and great, but what Lucene.Net lacks is a development
community.  As some of you know already, I'm the only active committer to
Lucene.Net.  This is bad in many ways.  It slows down releases considerably,
and it means Lucene.Net will never graduate from incubation to say the
least.

For example, if you are following up on the Java Lucene mailing list, you
will noticed that about 2 weeks ago, Lucene 2.2 was released.  Here on the
Lucene.Net, we still haven't done any progress on Lucene.Net 2.1 since my
initial release going back to May 1st, 2007!  (see:
http://mail-archives.apache.org/mod_mbox/incubator-lucene-net-dev/200705.mbo
x/[EMAIL PROTECTED])

(I did get one important fix from DIGY, thanks DIGY -- but there is a lot
more to be done.)

So, if you are a developer (you have to be if you are a user) and want to
see Lucene.Net in par with Java Lucene, and really like Lucene.Net such that
you don't want to see it dying, consider spending few hours a week and
helping with the port.  If you need any help from me to do so, or you are
not sure how to get started, please let me know.

Regards,

-- George

Reply via email to