[Lucene-java Wiki] Update of "SummerOfCode2011" by RobertMuir

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "SummerOfCode2011" page has been changed by RobertMuir.
The comment on this change is: update with a project list.
http://wiki.apache.org/lucene-java/SummerOfCode2011?action=diff&rev1=10&rev2=11

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

  = Lucene Google Summer of Code 2011 =
  
- == Students READ THIS! ==
+ Google Summer of Code 2011 has started! Now it's time to get some exciting projects
+ underway for this year's GSoC:
  
+ == Project List ==
- Google Summer of Code 2011 is very close and the Project Applications
- Period has started recently. Now it's time to get some excited students
- on board for this year's GSoC.
  
+ [[https://issues.apache.org/jira/browse/LUCENE-1768|LUCENE-1768]]: !NumericRange support for new Query Parser
- We encourage students to submit an application to the Google Summer of Code
- web-application. Lucene & Solr are amazing projects and GSoC is an
- incredible opportunity to join the community and push the project
- forward.
  
+ Apache Lucene supports indexing and searching for numeric types. This allows Lucene to support faster range queries, since building the field cache is much faster than using text-only numbers. One of the big limits today is the lack of support for numeric range queries in Lucene contrib query parser, which still only supports text range queries. This project proposes to implement numeric support in contrib query parser.
- If you are a student and you are interested spending some time on a
- great open source project while getting paid for it, you should submit
- your application from March 28 - April 8, 2011. There are only 3
- weeks until this process starts!
  
+ [[https://issues.apache.org/jira/browse/LUCENE-2308|LUCENE-2308]]: Separately specify a fields type
- Quote from the GSoC website: "We hear almost universally from our
- mentoring organizations that the best applications they receive are
- from students who took the time to interact and discuss their ideas
- before submitting an application, so make sure to check out each
- organization's Ideas list to get to know a particular open source
- organization better."
  
+ Goal of this project is to refactor the Field Lucene API by introducing new !FieldType class to separate Fields values from their properties and open way for easier Field extensions. This will result in more understandable instantiation of similar fields across documents. Field class, as part of core API, is very sensitive to shallow design or implementation which can cause drastic performance degradation due to its massive usage all over Lucene and Solr project, making this a challenging task.
- So if you have any ideas what Lucene & Solr should have, or if you
- find any of the GSoC [[https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+lucene-gsoc-11|pre-selected projects]] interesting, please
- join us on dev@lucene.apache.org ([[http://lucene.apache.org/java/docs/mailinglists.html|mailinglists]]).  Since you as a student must
- apply for a certain project via the [[http://www.google-melange.com|GSoC website]] , it's a good idea
- to work on it ahead of time and include the community and possible
- mentors as soon as possible.
  
+ [[https://issues.apache.org/jira/browse/LUCENE-2959|LUCENE-2959]]: Implementing State of the Art Ranking for Lucene
+ 
+ Lucene employs the Vector Space Model (VSM) to rank documents, which compares unfavorably to state of the art algorithms, such as BM25. Moreover, the architecture is tailored specifically to VSM, which makes the addition of new ranking functions a non-trivial task. This project aims to bring state of the art ranking methods to Lucene and to implement a query architecture with pluggable ranking functions.
+ 
+ [[https://issues.apache.org/jira/browse/LUCENE-2973|LUCENE-2973]], [[https://issues.apache.org/jira/browse/LUCENE-2975|LUCENE-2975]] : Enable Lucene to take advantage of low-level IO options (direct IO) and generalize it’s Directory implementation
+ 
+ Aims to generalize the current Lucene Directory implementation by making it a !UnixDirectory. This would be done by adding IOContext to the lower level API. These are two existing Lucene tasks (LUCENE-2793 and LUCENE-2795).
+ 
+ [[https://issues.apache.org/jira/browse/LUCENE-2979|LUCENE-2979]]: Simplify configuration API of contrib Query Parser
+ 
+ Lucene contrib query parser has a configuration API that was inherited from token stream API, which uses !AttributeSource and Attributes to share token information across token filters. However, the use of this Attribute API in contrib query parser makes configuration much more complex than it needs to be. This project proposes to simplify this API to something much simpler, using a map data structure instead of the complex Attribute API.
+ 
+ == Helpful Hints ==
  Open source development here at the Apache Software
  Foundation happens almost exclusively in the public and I encourage you to
  follow this. Don't mail folks privately; please use the mailing list to
@@ -54, +50 @@

  long. So try to break up your vision and the community will work with
  you to get things done!
  
- Go! join the mailing list and apply for GSoC 2011
- 
- == Project Ideas ==
-  
- New project ideas should be discussed on the mailinglist dev@lucene.apache.org and the outcome should be reflected as JIRA tickets marktd witl '''gsoc2011''' and '''lucene-gsoc-11''' labels. To find all already available ideas for Lucene and Solr klick [[https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+lucene-gsoc-11|here]] 
- 
- 
- 
- 
- 
- 
- 
- ,
-