lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hoss...@apache.org
Subject svn commit: r933818 - /lucene/board-reports/2010/board-report-april-special.txt
Date Tue, 13 Apr 2010 23:51:53 GMT
Author: hossman
Date: Tue Apr 13 23:51:52 2010
New Revision: 933818

URL: http://svn.apache.org/viewvc?rev=933818&view=rev
Log:
reformated to consistent column-width of 74

Modified:
    lucene/board-reports/2010/board-report-april-special.txt

Modified: lucene/board-reports/2010/board-report-april-special.txt
URL: http://svn.apache.org/viewvc/lucene/board-reports/2010/board-report-april-special.txt?rev=933818&r1=933817&r2=933818&view=diff
==============================================================================
--- lucene/board-reports/2010/board-report-april-special.txt (original)
+++ lucene/board-reports/2010/board-report-april-special.txt Tue Apr 13 23:51:52 2010
@@ -1,21 +1,21 @@
 Special Report to Board on Lucene's "Umbrella" Status
 
 The Lucene Project has, for a long time, organized itself into several
-related sub projects focused on common tasks related to searching.
-As of our last board report (March 2010) the sub-projects were:
+related sub projects focused on common tasks related to searching.  As of
+our last board report (March 2010) the sub-projects were: 
 
  * Lucene-Java: Our "flagship" Java search library
- * Nutch: A server application for crawling/indexing/search the web
- * Solr: A server application for indexing/searching structured data
- * Tika: A content extraction framework/library
- * Mahout: A machine learning framework/library
+ * Nutch: A server application for crawling/indexing/search the web 
+ * Solr: A server application for indexing/searching structured data 
+ * Tika: A content extraction framework/library 
+ * Mahout: A machine learning framework/library 
  * Open Relevance Project (ORP): A new initiative aimed at producing tools
    & tests for improving relevance for search engines and machine learning
- * Several "Ports" of Lucene-Java (Lucene.Net, PyLucene, Lucy)
+ * Several "Ports" of Lucene-Java: Lucene.Net, PyLucene, Lucy
    (These are all translations, mostly automated, of the Lucene Java API)
 
 The board's chief concerns regarding umbrella projects, as communicated to
-the Lucene PMC by Greg, seem to focus on three main issues...
+the Lucene PMC by Greg, seem to focus on three main issues... 
 
 1) Can every PMC member "commit" to all of these sub-projects?
 2) Is the PMC genearlly aware of everything going on in these sub-projects?
@@ -25,59 +25,57 @@ The answers to these questions, in short
 
 1) Yes.
 2) As a whole: Yes.  Some PMC members are not directly involved in some
-   sub-projects, but every sub-project has multiple voices on the PMC.
+   sub-projects, but every sub-project has multiple voices on the PMC. 
 3) We believe so, but if the board feels like more details about the state
    of each sub-project needs to be included in each report, we will be
-   happy to elaborate more in future reports.
+   happy to elaborate more in future reports. 
 
 In this regard, we don't feel that there is any significant cause for
 concern regarding the umbrella nature of the project.  To quote Greg:
-"we're all good. no changes are necessary." 
+"we're all good. no changes are necessary."  
   
 However....
 
 Based on various discussions in the community (and in some cases spurred
 on by the Board's concerns), the Lucene PMC is pursuing some changes
-moving forward.
+moving forward. 
 
-The PMC has put up two resolutions for this Board meeting to spin out Mahout
-and Tika, both of which have solid communities that are independent
-of Lucene and search.  The PMC has also consolidated development 
-between Solr and Lucene such that there is now a single committer base
-(there was already very high overlap of code and committers) and dev
-mailing list across those two projects.  We intend to still release
-both Lucene and Solr artifacts and to keep separate user question 
-mailing lists for the foreseeable future.
-
-This leaves the following sub projects: Nutch, the Ports and 
-Open Relevance.
-
-At this point, we are discussing whether Nutch should be spun out.  
-It's focus is increasingly on crawling alone and thus will likely 
-warrant becoming a TLP at some point in the future, but the sense 
-is that it is not ready to happen just yet.  As for the Ports, these
-fill a niche within the Lucene community and are generally small, 
-have almost complete technical overlap (releases usually follow 
-shortly after Lucene Java releases) but not necessarily a lot of 
-committer overlap due to them being ports to other programming 
-languages.  Because they are nearly automated ports, there isn't 
-also a lot of contributions to them, but there are decent sized 
-communities of users for each port.  Branding wise, they make sense
-being a part of the Lucene TLP.  Thus, the PMC doesn't feel a need
-to spin these out, even though they don't share SVN, etc. with Lucene core.
-That being said, we are still evaluating the situation.
-
-The Open Relevance sub project is small community effort to 
-facilitate discussions on relevance in Lucene.  It is nice to 
-have it's own branding, but is made up of existing Lucene 
-committers, so it best fits where it is. If, at some point, 
-we start to see traction and interest from other search 
-engines and other projects (Mahout, UIMA), it may make sense 
-to spin it out.
-
-Finally, the Lucene PMC will carefully consider any future requests 
-to become a sub project of Lucene.  The PMC is currently sponsoring
-two Incubator projects: Droids and the Lucene Connectors Framework.
-Both of these will probably become TLPs when they graduate.   In all 
-likelihood, the only future sub projects we would take on are ports 
-of Lucene like those mentioned above, for the reasons mentioned above.
+The PMC has put up two resolutions for this Board meeting to spin out
+Mahout and Tika, both of which have solid communities that are independent
+of Lucene and search.  The PMC has also consolidated development between
+Solr and Lucene such that there is now a single committer base (there was
+already very high overlap of code and committers) and dev mailing list
+across those two projects.  We intend to still release both Lucene and
+Solr artifacts and to keep separate user question mailing lists for the
+foreseeable future.  
+
+This leaves the following sub projects: Nutch, the Ports and Open
+Relevance. 
+
+At this point, we are discussing whether Nutch should be spun out.  It's
+focus is increasingly on crawling alone and thus will likely warrant
+becoming a TLP at some point in the future, but the sense is that it is
+not ready to happen just yet.  As for the Ports, these fill a niche within
+the Lucene community and are generally small, have almost complete
+technical overlap (releases usually follow shortly after Lucene Java
+releases) but not necessarily a lot of committer overlap due to them being
+ports to other programming languages. Because they are nearly automated
+ports, there isn't also a lot of contributions to them, but there are
+decent sized communities of users for each port. Branding wise, they make
+sense being a part of the Lucene TLP.  Thus, the PMC doesn't feel a need
+to spin these out, even though they don't share SVN, etc. with Lucene
+core.  That being said, we are still evaluating the situation.
+
+The Open Relevance sub project is small community effort to facilitate
+discussions on relevance in Lucene.  It is nice to have it's own branding,
+but is made up of existing Lucene committers, so it best fits where it
+is. If, at some point, we start to see traction and interest from other
+search engines and other projects (Mahout, UIMA), it may make sense to
+spin it out.  
+
+Finally, the Lucene PMC will carefully consider any future requests to
+become a sub project of Lucene.  The PMC is currently sponsoring two
+Incubator projects: Droids and the Lucene Connectors Framework.  Both of
+these will probably become TLPs when they graduate.   In all likelihood,
+the only future sub projects we would take on are ports of Lucene like
+those mentioned above, for the reasons mentioned above. 



Mime
View raw message