svn commit: r1104189 - /lucene/board-reports/2011/special-board-report-may.txt

[gs...@apache.org]

Author: gsingers
Date: Tue May 17 12:25:17 2011
New Revision: 1104189

URL: http://svn.apache.org/viewvc?rev=1104189&view=rev
Log:
final

Modified:
    lucene/board-reports/2011/special-board-report-may.txt

Modified: lucene/board-reports/2011/special-board-report-may.txt
URL: http://svn.apache.org/viewvc/lucene/board-reports/2011/special-board-report-may.txt?rev=1104189&r1=1104188&r2=1104189&view=diff
==============================================================================
--- lucene/board-reports/2011/special-board-report-may.txt (original)
+++ lucene/board-reports/2011/special-board-report-may.txt Tue May 17 12:25:17 2011
@@ -1,4 +1,3 @@
-
 === Lucene Status Report: May 2011 ===
 
 Background: Lucene has been asked by the Board to report on the state
@@ -28,18 +27,20 @@ reasoning has been clearly repudiated by
 Other concerns have arisen about the use of IRC such that we have
 started to use a logging client for IRC.  We have also reminded
 everyone to keep all decisions on list and to allow proposed decisions
-to "bake" before committing, at least when it comes to major issues.
+to "bake" before committing, at least when it comes to major issues/changes.
 
 Some in the community have also raised concerns about Lucid
 Imagination's role in development.  While Lucid does employ a good
-number (but not the majority) of committers [1], the general consensus
+number (but nowhere near the majority) of committers [1], (and which
+is almost completely balanced by IBM's presence) the general consensus
 seems to be that it is not a concern.  Furthermore, during the recent
 debates, it is quite clear that Lucid employees are free to have
 independent viewpoints on what to do.  Naturally, given a number of
-committers in one company, it warrants the PMC keep a watchful eye on
+committers in one company, it warrants the PMC keeping a watchful eye on
 it.  Likewise, however, it should also be clear that every
 PMC/committer involved in Lucene (with the exception of Andi Vajda) is
-paid to work on Lucene/Solr and they all have financial interests.
+paid to work on Lucene/Solr and they all have financial interests and
+are often in competition for the same clients.
 All should recognize that this doesn't necessarily make for problems,
 but can do so if people let it.
 
@@ -63,7 +64,7 @@ mechanism would likely benefit all the A
 2. We have added three new PMC Members: Doron Cohen, Shai Erera, Steve
 Rowe
 
-3. Rotate the Chair.  The Board should expect a resolution to change
+3. The Board should expect a resolution to change
 the PMC Chair for the June Board Meeting.  We also plan on changing
 the chair on a yearly basis.
 
@@ -74,7 +75,10 @@ symptom of this disagreement should not 
 5. To some extent, we feel this has been overblown and many of us have
 come to the conclusion that the simplest way to move forward is to get
 back to writing code and improving Lucene and Solr and getting
-releases out.  To that end, we are working on releasing 3.2 of Lucene
+releases out.  This is not intended to paper over the concerns, but
+to note that the whole point of the project is to deliver open source
+search software via the ASF guidelines.  To that end, we are working on 
+releasing 3.2 of Lucene
 and Solr as well as continuing development on 4.0.
 
 [1] Current PMC Members/Committers and their employers
@@ -104,7 +108,6 @@ and Solr as well as continuing developme
     Chris Male (chrism@...) -- JTeam
     Andi Vajda (vajda@...) -- Google
     *Scott Ganyo -- Actor
-    * Mark Harwood -- ?
+    * Mark Harwood -- Detica
     Adriano Crestani -- IBM
 
-