Dear Wiki user,

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

The "LucyIncubatorProposal" page has been changed by MarvinHumphrey.
The comment on this change is: Flesh out Background.
http://wiki.apache.org/lucy/LucyIncubatorProposal?action=diff&rev1=19&rev2=20

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

  A lengthier description of the proposal. Should be reasonably declarative. 
More discursive material should be included in the rationale (or other later 
sections). Example (XAP): XAP is to provide an XML-based declarative framework 
for building, deploying and maintaining rich, interactive, Ajax-powered web 
applications. A basic principal of XAP is to leverage existing Ajax ...
  
  == Background ==
- Explain terms whose meanings may be misunderstood (for example, where there 
is not a single widely adopted definition).
+ Lucy began as an ambitious, from-scratch Lucene sub-project, with initial 
committers David Balmain (author of Ferret, a Ruby/C port of Lucene), Doug 
Cutting, and Marvin Humphrey (founder of KinoSearch, a Perl/C port).  During an 
initial burst of activity, the overall architecture for Lucy was sketched out 
by Dave and Marvin.  Unfortunately, Dave became unavailable soon after, and 
without a working code base to release or any users, it proved difficult to 
replace him.  Still, Marvin carried on their work throughout a period of 
seeming dormancy.
  
- This content should be capable of being safely ignored by domain experts. It 
should probably find an eventual home on the Podling website. Example 
(Heraldry): To provide some background, the Higgins Project is being actively 
developed within Eclipse and is a framework that will enable users and 
enterprises to integrate identity, profile, and relationship information across 
multiple systems. Using context providers, existing and new systems such as 
directories, collaboration spaces ...
+ In the last year, the work has come to fruition: major technical milestones 
have been achieved and Lucy's underpinnings have been completed.  Additionally, 
other developers from the KinoSearch community have taken an interest in Lucy 
and have begun to ramp up their contributions.  The next steps for Lucy were 
articulated by the Lucene PMC in a recent review: make releases, acquire users, 
grow community.
+ 
+ To implement the Lucene PMC's recommendations and get to a release as quickly 
as possible, the Lucy community proposes to assimilate the KinoSearch code 
base, which has been retrofitted to use Lucy's core.  Lucy still lacks a number 
of important indexing and search classes; we wish to flesh these out via IP 
clearance work rather than software development. 
+ 
+ Since the Lucene PMC will not be responsible for Lucy much longer, it is more 
appropriate for the software grant to take place within the context of the 
Incubator than the Lucene TLP.  As none of our current members have Apache PMC 
experience, we also seek to take advantage of the Incubator environment to 
prepare ourselves for responsible self-governance.
  
  == Rationale ==
  Explains why this project needs to exist and why should it be adopted by 
Apache. This is the right place for discursive material. Example (Beehive): 
There is a strong need for a cohesive, easy-to-use programming model for 
building J2EE applications. Developers new to Java are forced to learn a myriad 
of APIs just to build simple applications; advanced J2EE developers are forced 
to write tedious plumbing code; and tools authors are limited in what they can 
do to simplify the experience due to the underlying complexity.
@@ -26, +30 @@

   * Expose a public C API.
  
  == Current Status ==
-  * Currently a Lucene subproject.
-  * Major technical achievements in the last year.
-  * Board policy of breaking up subprojects, Lucy asked to submit plan for  
graduation.
-  * Lucene PMC identified community building as primary task.
-  * Fastest path to a community is assimilation of KinoSearch code base.
  
  === Meritocracy ===
  Our initial committer list includes two individuals (Peter Karman and Nathan 
Kurz) who started off as KinoSearch users, demonstrated merit through 
constructive forum participation, adept negotiation, consensus building, and 
submission of high-quality contributions, and were invited to become 
committers.  Peter now rolls most releases.

Reply via email to