Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <474790F9.1020604@dubioso.net>
Date: Sat, 24 Nov 2007 03:48:25 +0100
From: Roland Weber <ossfwot@dubioso.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.9) Gecko/20071109 SeaMonkey/1.1.6
MIME-Version: 1.0
To: general@incubator.apache.org
Subject: Re: Interested to work on it!
References: <693442.19748.qm@web94003.mail.in2.yahoo.com>
In-Reply-To: <693442.19748.qm@web94003.mail.in2.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello Kaushik,

kaushik sarkar wrote:
> Hi there,
> 
> I worked for Kazeon Search Engine. Where it uses Java Lucene Library.
> I am interested to work for it's c counter part. Please provide me necessary 
> information and pointer to start from.

I take it you are referring to this retired podling:
http://incubator.apache.org/lucene4c/

It was retired over a year ago due to lack of developer
activity, as you can see on the Incubator project list:
http://incubator.apache.org/projects/index.html

I'm afraid that the notice about posting to general@incubator
on the retired podling's page is just a standard notice. In
order to be reactivated, Lucene4c would have to go through
the regular entry process again:
http://incubator.apache.org/incubation/Incubation_Policy.html#Entry+to+Incubation

Apart from requiring a champion and sponsor, this would also
mean that three Apache members have to volunteer as mentors,
and that infrastructure resources such as mailing list are
set up again. The simple truth is: it's not going to happen
until a whole community of developers shows up.

While it is a Herculean task to form a developer community,
it is not altogether impossible. You can get started by
taking the current Lucene4c code from svn and playing with it:
http://svn.apache.org/repos/asf/incubator/lucene4c/trunk/

Maybe some of the people who used to work on it can still
be found on one of the mailing lists of Lucene (Java) and
CLucene (C++):
http://lucene.apache.org/mail.html
http://sourceforge.net/mail/?group_id=80013
You will have to work with those communities anyway to
understand the file formats to which Lucene4c wanted to
be compatible.

If you played around with the code long enough to know you
like it, and you are willing to commit yourself to a long-
term engagement, you can take your private fork to Sourceforge
or Google Code or some other OSS project hoster. At this point,
the gathering of a developer community really starts. You
should expect that to take years, unless you happened to
find some fellow developers already waiting in the existing
communities. Once the forked project is running well, it is
finally time to consider taking it to Apache again. That will
be the decision of the newly formed developer community.


I'm sorry to have no better news for you.

cheers anyway,
  Roland

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org