Bruce Lee wrote:
1. Improved consistency of code architecture by adopting the Usecase model; therefore also improving maintainability. This assists in achieving the identified goal of Product Maturity.
maybe mention that search is one of the only components that currently does not use the usecase framework, for historical reasons.
2. Enhanced performance, flexibility and efficiency by adopting Nutch, contributing to Usability, Feature Set, Off The Shelf Components.
mention replacement of the homegrown crawler with nutch
3. Enhanced power, flexibility and ease of use for Lenya users by enabling incremental content index update and repository metadata search facilites. These changes will impact the Feature Set and Usability of Lenya and most significantly, this will assist in Lowering the Entry Barrier to Lenya and ease the adoption for newcomers. Deliverables: 1. Migrate existing search facilities to Usecase model http://lenya.apache.org/1_4/reference/usecase-framework/index.html 2. Replace existing crawl facility with Nutch http://lucene.apache.org/nutch/ 3. Enable incremental updates of Lucene index http://lucene.apache.org/java/docs/ 4. Implementing repository metadata search with Jackrabbit http://incubator.apache.org/jackrabbit/index.html
i suspect you'll need to go into more details here
Project Schedule: I would expect to spend ~1 week familiaring myself with the details of each listed deliverable, and a similar amount of time implmenting a solution. This amounts to 8 weeks in total. I can start work immediately, which also allows some room to move with the September 1st deadline.
what about milestones? it seems to me google wants to have midway checkpoints, etc
While at first glance it may seem odd to approach Google for funding on a project that seeks to work with an alternative Open Source search engine, I believe that the ideas and outcomes of the project may be beneficial for all concerned in the longer term, and hope that there is scope for a cross-pollination of ideas as search technologies are refined in the coming decades.
i am not sure, but i think google will look more for technical meat than 'vision' turn of phrases, so i'd suggest to focus on the techical more
(PS. Ironic as this may sound from someone interested in enhanced search capabilities, I have had trouble in the past being "stalked" by certain individuals who were able to find information about me via the web. I would not like to experience this again. If you need to make specific details of the Summer of Code participants public, eg: name, email, could you please contact me so that we can negotiate an appropriate way to do so. Thanks.
i think there is no need to make that public, although you'll have to sign a CLA if your code gets incorporated into the ASF codebase. as to google's requirements, i don't know
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
