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] Update of "Lucene.Net Proposal" by ScottLombard
Date Sun, 02 Jan 2011 05:03:13 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 ScottLombard.
http://wiki.apache.org/incubator/Lucene.Net%20Proposal?action=diff&rev1=7&rev2=8

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

  
  = Lucene.Net - A .NET port of Lucene =
  == Preface ==
+ Lucene.Net is a sub-project which is being spun off from the Lucene TLP but is not yet ready
for graduation. We propose to address certain needs of the project by transitioning to an
Incubator Podling.
- Lucene.Net is a sub-project which is being spun off from the Lucene TLP but is not yet ready
for graduation.  
- We propose to address certain needs of the project by transitioning to an Incubator Podling.
  
  == Abstract ==
- 
  Lucene.Net will be a port of the Lucene search engine library, written in C# and targeted
at .NET runtime users.
  
  == Proposal ==
- Lucene.Net has three aims. First, it will maintain the existing line-by-line port from Java
to C#, fully automating and commoditizing that process, making releases such that the project
can easily release in sync with the Java Lucene release schedule. Second, it will be a high-performance
C# search engine library.  Third, it will maximize its usability and power when used within
the .NET runtime. To that end, it will present a highly idiomatic, carefully tailored API
that takes advantage of many of the special features of the .NET runtime.
+ Lucene.Net has three aims. First, it will maintain the existing line-by-line port from Java
to C#, fully automating and commoditizing that process, making releases such that the project
can easily release in sync with the Java Lucene release schedule. Second, it will be a high-performance
C# search engine library. Third, it will maximize its usability and power when used within
the .NET runtime. To that end, it will present a highly idiomatic, carefully tailored API
that takes advantage of many of the special features of the .NET runtime.
  
  == Background ==
- Lucene.Net, began as a independent project focused on creating a line-by-line, API for API
port of Java Lucene to C#. It continued successfully in this way and eventually became a ASF
Incubator project in April of 2006 and graduated as a sub-project of Lucene in October of
2009. 
+ Lucene.Net, began as a independent project focused on creating a line-by-line, API for API
port of Java Lucene to C#. It continued successfully in this way and eventually became a ASF
Incubator project in April of 2006 and graduated as a sub-project of Lucene in October of
2009.
  
  The last year has been challenging for the project. The committers who originally lead the
project have stopped maintaining it and development has stagnated since June of 2010. The
user community has spoken out requesting a change in philosophy and direction for the project,
but those requested have been unheeded. This has led to a number of forks outside of the ASF.
We would like to bring those forks back in as branches and eventually, be responsive to the
needs of community without the need for multiple non-ASF forks.
  
- The Lucene PMC wants to see the project continue to thrive and has indicated that a return
to the Incubator is an appropriate step, with the end goal to build of building a new team
of committers and maintaining a steady release cycle meeting the previously stated goals.
Because Lucene is working to move away from being an "umbrella project", a long term goal
of the Lucene.Net project is to graduate to an ASF TLP.  
+ The Lucene PMC wants to see the project continue to thrive and has indicated that a return
to the Incubator is an appropriate step, with the end goal to build of building a new team
of committers and maintaining a steady release cycle meeting the previously stated goals.
Because Lucene is working to move away from being an "umbrella project", a long term goal
of the Lucene.Net project is to graduate to an ASF TLP.
- 
  
  == 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 unique 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.
+ 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 
+  * 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, documentation, etc.
-  * Create a well documented repeatable and fully automated language 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 their 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 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.
  
  Because of the size of the community and the fact that it's audience is largely developers,
finding new committers over time should remain an easy task. The user base is also constantly
growing, because Lucene.Net is one of the very few high quality products in this space (either
commercial or open source). Index and Search is an essential part of many web-based applications
which are developed on the .NET framework, and Lucene.Net is widely used to support that scenario.
This will only grow with time.
  
  A brief list of known commercial products using Lucene.Net (alphabetical):
+ 
   * Autodesk - http://autodesk.com/
   * BBC UK Top Gear site - http://www.topgear.com/
   * Epro, Bluewire Technologies - http://www.epro.com/
-  * Intelli``Enterprise Intranet Suite - http://www.adenin.com/
+  * IntelliEnterprise Intranet Suite - http://www.adenin.com/
   * Koders.com, Black Duck Software - http://www.koders.com/
   * Oxford Analytica - http://www.oxan.com
-  * Paradigm  - http://discover-e-legal.com/aboutparadigm.html
+  * Paradigm - http://discover-e-legal.com/aboutparadigm.html
-  * Power``Search - http://datassimilate.com/PSindex.html
+  * PowerSearch - http://datassimilate.com/PSindex.html
  
  A brief list of open source projects depending on Lucene.Net (alphabetical):
+ 
   * iReaper - http://ireaper.codeplex.com/
   * Linq to Lucene - http://linqtolucene.codeplex.com/
   * Lucandra.NET - http://lucandranet.codeplex.com/
-  * Mind``Touch - http://www DOT mindtouch DOT com/ (not sure why the wiki disallows this)
+  * MindTouch - http://www DOT mindtouch DOT com/ (not sure why the wiki disallows this)
   * Orchard - http://orchard.codeplex.com/
   * RavenDB - http://ravendb.net/
-  * Sub``Text - http://subtextproject.com/
+  * SubText - http://subtextproject.com/
   * Umbraco - http://umbraco.codeplex.com
  
  There are of course many, many more.
  
- 
  === Core Developers ===
- The core developers are a diverse group of developers many of which are already very experienced
open source developers. 
+ The core developers are a diverse group of developers many of which are already very experienced
open source developers.
  
   * Troy Howard is an experienced developer and software development project manager in the
commercial world. He has founded and been a committer on numerous open source projects over
the years, including most recently, a fork of Lucene.Net which he hopes to integrate back
into the main project.
-  
+ 
   * Chris Currens is a passionate developer who works with Troy at his day job and has worked
together with Troy one two previous open source projects. Together they make a solid and productive
team.
-  
+ 
-  * TODO 
+  * 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 which ensures that
the project stays on track and productive. We also appreciate being associated with the Lucene
TLP and the sharing that provides.
@@ -85, +83 @@

  
  == Known Risks ==
  === Orphaned products ===
- 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. 
+ 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 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. 
+ 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).
  
  === Inexperience with Open Source ===
- The core developers all have significant experience with open source development.  We recognize
that we lack PMC experience and seek to address that deficiency by using the Incubator environment
to educate ourselves and prepare for responsible self-governance.
+ The core developers all have significant experience with open source development. We recognize
that we lack PMC experience and seek to address that deficiency by using the Incubator environment
to educate ourselves and prepare for responsible self-governance.
  
  === Homogenous Developers ===
- Our community is geographically dispersed, with members in many areas of the USA, Canada,
Russia, UK, and other countries.  We all work for different organizations.
+ Our community is geographically dispersed, with members in many areas of the USA, Canada,
Russia, UK, and other countries. We all work for different organizations.
  
  === Reliance on Salaried Developers ===
  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.
@@ -106, +104 @@

  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.
+ 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.
  
  By rebooting the project with a new list of motivated and engaged committers, we expect
to avoid the trap that ensnared Lucene.Net's first incarnation: we will release early, release
often, accumulate users, nurture contributors, and grow our community.
  
@@ -114, +112 @@

   * Current Lucene.Net website: http://lucene.apache.org/lucene.net/
   * Current Lucene.Net Subversion repository: http://svn.apache.org/repos/asf/lucene/lucene.net/
   * Current Lucene.Net mailing lists: http://lucene.apache.org/lucene.net/ (See info under
"Mailing Lists" heading)
-  
+ 
  == Initial Source ==
  We will continue working with the existing Lucene.Net codebase located at: http://svn.apache.org/repos/asf/lucene/lucene.net/
  
@@ -123, +121 @@

   * Lucere - http://lucere.codeplex.com/
   * Lucille - http://lucille.codeplex.com/
   * Aimee.Net - http://aimee.codeplex.com/
-  
+ 
  == Source and Intellectual Property Submission Plan ==
- All source code referred to in this project (existing codebase and that of forks) is already
licensed under the Apache 2.0 License. There should be no conflicts in this regard. 
+ All source code referred to in this project (existing codebase and that of forks) is already
licensed under the Apache 2.0 License. There should be no conflicts in this regard.
  
  == External Dependencies ==
- The only external dependencies represented in any of the proposed code are on unit testing
and mocking frameworks, all of which have ASF compatible licenses. 
+ The only external dependencies represented in any of the proposed code are on unit testing
and mocking frameworks, all of which have ASF compatible licenses.
  
  == Required Resources ==
  === Mailing lists ===
@@ -136, +134 @@

   * lucene-net-commits
   * lucene-net-users
  
- Lucene.Net already has lucene-net-dev, lucene-net-users, and lucene-net-commits mailing
lists under lucene.apache.org.  While these could be deactivated and the memberships migrated
to the appropriate lists under incubator.apache.org, leaving the lucene.apache.org archives
as read-only, we would prefer to keep the mailing lists the same, rather than moving to incubator.apache.org.
The purpose of that would be to remain engaged with our community, with minimal disruption.
+ Lucene.Net already has lucene-net-dev, lucene-net-users, and lucene-net-commits mailing
lists under lucene.apache.org. While these could be deactivated and the memberships migrated
to the appropriate lists under incubator.apache.org, leaving the lucene.apache.org archives
as read-only, we would prefer to keep the mailing lists the same, rather than moving to incubator.apache.org.
The purpose of that would be to remain engaged with our community, with minimal disruption.
  
  === Subversion Directory ===
  Lucene.Net already has a Subversion directory at https://svn.apache.org/repos/asf/lucene/lucene.net.
In keeping with naming conventions, it could be moved to http://svn.apache.org/repos/asf/incubator/lucene.net.
@@ -145, +143 @@

  Lucene.Net already has a JIRA tracker: Lucene.Net (LUCENENET)
  
  === Other Resources ===
- Lucene.Net already has a MoinMoin wiki at http://wiki.apache.org/jakarta-lucene/lucene.Net.
 It can be moved to standard Incubator wiki placement as there is currently no content of
value in the wiki.
+ Lucene.Net already has a MoinMoin wiki at http://wiki.apache.org/jakarta-lucene/lucene.Net.
It can be moved to standard Incubator wiki placement as there is currently no content of value
in the wiki.
  
  == Initial Committers ==
  ||'''Name''' ||'''Email''' ||'''CLA''' ||
- ||Troy Howard||thoward37 AT gmail DOT com||No||
+ ||Troy Howard ||thoward37 AT gmail DOT com ||No ||
- ||Chris Currens||currens.chris AT gmail DOT com||No||
+ ||Chris Currens ||currens.chris AT gmail DOT com ||No ||
- ||Michael Herndon||mherndon  AT wickedsoftware DOT net||No||
+ ||Michael Herndon ||mherndon AT wickedsoftware DOT net ||No ||
- ||Prescott Nasser||prescott.nasser AT hotmail DOT com||No||
+ ||Prescott Nasser ||prescott.nasser AT hotmail DOT com ||No ||
+ ||Scott Lombard ||lombardenator AT gmail DOT com ||No ||
+ 
  
  == Affiliations ==
- 
-  * 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. 
+  * 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