Marco,
My feeling would be to create strong automated conversion tools to allow java
Lucene to be ported in to .NET in as few steps and as possible. The .net style
goal is a noble one, but will require a significant more commitment to the
project in the future. As each new version of java
Scott,
I agree with everything you said. My opinion is that one of the
largest failings of the current Lucene.Net development effort is that
there's too much magic in the conversion process. This is assuming
we continue with Lucene.Net as a line-by-line automated port.
As Heath said, the details
Marco,
I agree with you on this front. I feel that the first tasks that a new
Lucene.Net team should focus on, in terms of development are:
- Fully automating a line-by-line port using a tool such as Sharpen.
This needs to become a commodity function requiring very little
development effort
-
Folks,
I will freely admit that I'm seizing the opportunity to raise an old
point - but that problem would be non-existent if this was a project
that implemented a methodology as opposed to being a continuous port
effort. I will even go as far as suggesting that this would broaden (and
ease) the
From everything that was said it seems apparent to me that the only way for
Lucene.Net to stay alive is to move back to incubation. So where do we go
from here? More than 4 people have said they are willing to be committers.
Is this email list the best place to start working on a proposal,
Does the conversion tool actually help or hinder?
My feeling is that the more dependency you have on a tool, the less likely
this project will ever stand on its own.
There should probably be parallelized branches. one that continues using the
tool to provide for the current gaps between .net
That is exactly what I would suggest. Sharpen looks like a great tool,
since you can customize it's behaviour. In fact, the only downside is
that you have to customize it's behaviour which requires a lot of
upfront work.
Thanks,
Troy
On Thu, Dec 30, 2010 at 11:42 AM, Prescott Nasser
I think it took be 5 deletes of this e-mail and complete rewrites to try to
say this in the best way possible:
First off, Sharpen is a java tool (from the db4o SVN I found) - using sharpen
to port lucene to .net means that people now have to install a jvm on their
computers in order to
Troy, et al,
Given the recent positive shift in attitude regarding the Lucene.Net
project, I would like to consider ways that I could help contribute
as well. As with other people in the community, while my company is
very small (I am both Chief Software Architect
It's my opinion that we can basically commoditize an automated port
which will fulfill the needs of the community, and allow the project
to, at minimum, continue to release, in a timely fashion, direct ports
of the Java Lucene releases...
Meanwhile we can continue the efforts represented in
So perhaps the proposal should allow for a combination of a mostly
automated baseline line-by-line port and the explicit provision that
embraces drop-in (API compliant) .NET-specific replacements for
specific classes?
- Ben
Yes. I'm in the process of writing that proposal at this time. It will
include language in the project description that express our intent to
develop a C#/.NET idiomatic version of the library.
Please find the in-progress draft version at:
http://wiki.apache.org/incubator/Lucene.Net%20Proposal
Grant,
I'm working on the proposal and have come to the final section where I
must list a Champion and list of Mentors.
Can I put your name for Champion and possibly as a Mentor as well? Are
there any other folk out there willing to Mentor our project during
incubation? Should I instead wait for
Sorry... I was in outer space with those dates.
To clarify, I'll submit the application on Tuesday, January 11th, 2011
which gives us exactly 12 days as a community to determine our
opinions, plans, develop our proposal and committer list.
Thanks,
Troy
On Thu, Dec 30, 2010 at 4:13 PM, Troy
Troy,
Thank you for all your work on the Incubator Proposal you have done an
excellent job.
I volunteered to be a committer and here is my brief qualification list. I
have a BS in Electrical Engineering and currently work in the Automation field.
I do extensive programming in MS SQL,
15 matches
Mail list logo
