incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Trivial Update of "Lucene.Net Proposal" by PrescottNasser
Date Fri, 31 Dec 2010 00:25:05 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "Lucene.Net Proposal" page has been changed by PrescottNasser.
The comment on this change is: spelling and grammar updates.
http://wiki.apache.org/incubator/Lucene.Net%20Proposal?action=diff&rev1=3&rev2=4

--------------------------------------------------

  
  
  == Rationale ==
- There is great need for a search engine library in the mode of Lucene within the .NET runtime.
Individuals naturally wish to code in their language of choice.  Organizations which do not
have significant Java expertise may not want to support Java strictly for the sake of running
a Lucene installation.  Developers may want to take advantage of C#'s unique language features
and the .NET runtime's unqiue execution and interoperability model.  Lucene.Net will meet
all these demands.
+ There is great need for a search engine library in the mode of Lucene within the .NET runtime.
Individuals naturally wish to code in their language of choice.  Organizations which do not
have significant Java expertise may not want to support Java strictly for the sake of running
a Lucene installation.  Developers may want to take advantage of C#'s unique language features
and the .NET runtime's unique execution and interoperability model.  Lucene.Net will meet
all these demands.
  
  Apache is a natural home for our project given the way it has always operated: user-driven
innovation, security as a requirement, lively and amiable mailing list discussions, strength
through diversity, and so on.  We feel comfortable here, and we believe that we will become
exemplary Apache citizens.
  
  == Initial Goals (to be completed before Feb 2011) ==
   * Build a new list of committers 
   * Make a 2.9.2 compatible release as quickly as possible (this already exists, it just
needs to be packaged correctly)
-  * Update website, documention, etc.
+  * Update website, documentation, etc.
-  * Create a well documented repeatable and fully automated langauge porting process 
+  * Create a well documented repeatable and fully automated language porting process 
   * Start a ".NET style API" branch, either by incorporating some or all existing fork projects
or by starting a new branch to this end
  
  == Current Status ==
  === Meritocracy ===
- We understand meritocracy and will fully embrace this concept in our project management
methodology. Two of the proposed initial committers, Troy Howard and Chris Currens, are both
already actively involved in other open source projects, both as committers of code and in
coordination roles. They are familiar with the challenges faced with starting and maintaining
a project over time. We also understand that opportunity is essential to an effective meritocracy
and so will remain transparent, open and actively engage the community to find new contributors,
include and review thier contributions, and bring them on as committers as appropriate. 
+ We understand meritocracy and will fully embrace this concept in our project management
methodology. Two of the proposed initial committers, Troy Howard and Chris Currens, are both
already actively involved in other open source projects, both as committers of code and in
coordination roles. They are familiar with the challenges faced with starting and maintaining
a project over time. We also understand that opportunity is essential to an effective meritocracy
and so will remain transparent, open and actively engage the community to find new contributors,
include and review their contributions, and bring them on as committers as appropriate. 
  
  === Community ===
- There is already a well established, active and vibrant community surrounding the Lucene.Net
project. This is primarily a users community, as the previous committers have not engaged
the user community to find or leverage would-be contributors. There is a a lot of talent available
in the community to this end. 
+ There is already a well established, active and vibrant community surrounding the Lucene.Net
project. This is primarily a users community, as the previous committers have not engaged
the user community to find or leverage would-be contributors. There is a lot of talent available
in the community to this end. 
  
  There are a number of well established and significant .NET open source projects which are
widely used by the larger .NET community which depend on Lucene.Net. There are also countless
commercial products which use and are dependent on this project. The mailing lists are active
with numerous community members both asking and answering technical questions. The status
and activities of the project are watched closely by the larger .NET development community
and regularly commented on in blogs and other discussion forums.
  
@@ -56, +56 @@

   * TODO 
  
  === Alignment ===
- Lucene.Net has been an ASF project since 2006 and has benefitted greatly from that affiliation.
We appreciate the careful oversight and structure that Apache provides whcih ensures that
the project stays on track and productive. We also appreciate being associated with the Lucene
TLP and the sharing that provides.
+ Lucene.Net has been an ASF project since 2006 and has benefitted greatly from that affiliation.
We appreciate the careful oversight and structure that Apache provides which ensures that
the project stays on track and productive. We also appreciate being associated with the Lucene
TLP and the sharing that provides.
  
  Beyond that a very practical concern is that we would like to continue developing Lucene.Net
with its current name. The project has build a hard earned reputation and leaving the ASF
would mean a forced rebranding and losing that reputation in the process. This would not be
good for the health of the project.
  
  == Known Risks ==
  === Orphaned products ===
- The purpose of this proposal is to recover from the fact that Lucene.Net has been orphaned
by it's current list of committers. There are numerous reasons why that happened, such as;
Project vision not aligned with community needs, Committers not taking advantage of contributors
in the community, Committers not being upfront about thier ability or interest in maintaining
the project, No effort to incorporate new committers from the community or engage non-committers
in the development process. 
+ The purpose of this proposal is to recover from the fact that Lucene.Net has been orphaned
by its current list of committers. There are numerous reasons why that happened, such as;
Project vision not aligned with community needs, Committers not taking advantage of contributors
in the community, Committers not being upfront about their ability or interest in maintaining
the project, No effort to incorporate new committers from the community or engage non-committers
in the development process. 
  
  Because we will be coming from the perspective of recovering from orphaning, we will be
strongly focused on building a community, team of committers, and process to ensure our long
term stability. We will learn from the past and not repeat the mistakes of our predecessors.
  
- Beyond that, there is significant commercial interest in this project which we believe can
be converted to direct support in terms of on-the-clock work by developers working for companies
that have software products which rely on Lucene.Net. The intial committers list includes
two such developers and we hope to attract more of them. Because we understand that commercial
support of this nature can be fickle, we will also work to diversy the team and include committers
who are personally motivated. 
+ Beyond that, there is significant commercial interest in this project which we believe can
be converted to direct support in terms of on-the-clock work by developers working for companies
that have software products which rely on Lucene.Net. The initial committers list includes
two such developers and we hope to attract more of them. Because we understand that commercial
support of this nature can be fickle, we will also work to diversy the team and include committers
who are personally motivated. 
  
  We also hope to incorporate the three existing forks of Lucene.Net back into this project.
Doing so would bring a large body of reliable committers into the fold of this project (Lucere
has more than 10 active committers, Lucille and Aimee.Net are one-man projects, both of which
are very committed individuals).
  
@@ -80, +80 @@

  We incorporate both salaried and non-salaried developers, from multiple organizations. We
feel this gives us the best of both worlds and will increase our viability as a long-term
project.
  
  === Relationships with Other Apache Products ===
- Lucene.Net's relationship with the Lucene TLP has been relatively uni-drectional until now.
Lucene.Net has simply been porting the code that Lucene write in Java to C# using automated
methods. We hope to change that and feed-back more into the Java Lucene community both on
the conceptual level and in terms of API changes that we make. We have an interest in possibly
integrating the work of the Lucy project into Lucene.Net at some point as well. There is also
a strong interest in creating .NET ports of ASF's Solr, Tika, Hadoop, and others. While that
would fall outside of the scope of this project, there may be overlap in terms of the committers
between those projects and sharing of code and methodologies pioneers in the Lucene.Net project.
+ Lucene.Net's relationship with the Lucene TLP has been relatively unidirectional until now.
Lucene.Net has simply been porting the code that Lucene write in Java to C# using automated
methods. We hope to change that and feed-back more into the Java Lucene community both on
the conceptual level and in terms of API changes that we make. We have an interest in possibly
integrating the work of the Lucy project into Lucene.Net at some point as well. There is also
a strong interest in creating .NET ports of ASF's Solr, Tika, Hadoop, and others. While that
would fall outside of the scope of this project, there may be overlap in terms of the committers
between those projects and sharing of code and methodologies pioneers in the Lucene.Net project.
  
  === An Excessive Fascination with the Apache Brand ===
  Our desire to maintain Lucene.Net's affiliation with Apache has less to do with the brand
and more to do with our conviction that developing the project The Apache Way under Apache
institutions is in Lucene.Net's best interests.  However, we have to acknowledge that during
its time as a Lucene subproject, Lucene.Net has not always fulfilled certain key requirements
for an Apache project.  In particular, it has failed to "release early, release often", despite
making significant progress in expanding its user community.
@@ -95, +95 @@

  == Initial Source ==
  We will continue working with the existing Lucene.Net codebase located at: http://svn.apache.org/repos/asf/lucene/lucene.net/
  
- We will also attempt to contact the coordinators of the following Lucene.Net forks and incorporate
thier work into the Lucene.Net project:
+ We will also attempt to contact the coordinators of the following Lucene.Net forks and incorporate
their work into the Lucene.Net project:
  
   * Lucere - http://lucere.codeplex.com/
   * Lucille - http://lucille.codeplex.com/
@@ -131, +131 @@

  
  == Affiliations ==
  
-  * Troy Howard and Chris Currens both work for discover-e Legal, LLC and will work on Lucene.Net
as part of thier paid work. discover-e Legal uses the current Lucene.Net build in thier products
and so, has a vested interest in seeing the project continue. Beyond that, the reason Lucene.Net
was choosen by Troy initially for the discover-e Legal products is due to his strong interest
in the project. This interest was well established before working for discover-e Legal, and
is independent of it's needs. The same is true for Chris Currens. So, even though there is
commercial support for their work on this project it is not the primary reason or motivator
for thier interest. 
+  * Troy Howard and Chris Currens both work for discover-e Legal, LLC and will work on Lucene.Net
as part of their paid work. discover-e Legal uses the current Lucene.Net build in their products
and so, has a vested interest in seeing the project continue. Beyond that, the reason Lucene.Net
was chosen by Troy initially for the discover-e Legal products is due to his strong interest
in the project. This interest was well established before working for discover-e Legal, and
is independent of its needs. The same is true for Chris Currens. So, even though there is
commercial support for their work on this project it is not the primary reason or motivator
for their interest. 
  
  == Sponsors ==
  === Champion ===

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


Mime
View raw message