THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Flume Apache Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. Flume entered incubation on June 12th, 2011. Progress since last report * Move the active development branch - flume-728 to trunk: Completed. * Flume version 1.1.0-incubating released from trunk on March 27, 2012 * Flume PPMC voted three new committers - Hari Shreedharan, Mike Percy and Will McQueen * Flume PPMC voted in a new PPMC member - Prasad Mujumdar * Development work going strong 146 issues resolved since last submitted report. * The flume-dev list has currently 103 subscribers with traffic of 3410 messages over last three months. * The flume-user list has currently 250 subscribes with traffic of 415 messages over last three months. * A Flume user meetup is being organized on June 13 in San Francisco Bay Area and has attendance to the planned capacity. Progress on graduation: * Community vote: PASSED. Vote (1), Result (2) * Incubator PMC Vote: IN PROGRESS. Vote (3) * During the community vote a concern was raised regarding whether the podling had sufficient diversity (4). Discussion thread (5). Key points discussed in this thread are as follows: * There are at least 4 different organizations represented in the current set of committers (6). However the concern was later qualified as diversity of PPMC and not committers. * There are at least four different organizations represented in the PPMC (7). Incidentally, two of the PPMC members remain interested but have taken a back seat given that they are either busy due to family circumstances (8) or are satisfied by how the current PPMC is operating and do not feel the need to intervene given their other commitments (9). As a result the only active organizations are Cloudera and Intuit, where the representation from Intuit is that of a mentor who is also a committer. * The discussion shifted back to diversity of committers and it was noted that a vast majority of the commits were coming from a single committer and virtually all commits were from Cloudera employees (10). * It was clarified that Flume follows RTC policy where the committers do not commit their own patches and instead the reviewer does it for them. As a result the numbers pointed out in (10) were not representative of actual contributions. Actual contributions can be found from assigned Jira tickets which show that on an average a Cloudera committer has made 26 contributions while a non-Cloudera committer has made 5 (11). This is likely because Cloudera committers usually work during office hours whereas other committers may not. * It was pointed out that regardless of the average contributions Cloudera has contributed 93% of the time (12). * It was noted such scenario exists or has existed in other projects which are successful (13), and that the PPMC must work hard to ensure that it is a level playing field for all contributors. Given the above discussion and the diversity concern regarding PPMC raised by a mentor, the Flume PPMC discussed in private about the ways to address this. The Flume PPMC concluded that adopting the process of promoting all current committers to PMC status on graduation will resolve the diversity concern and allow the graduation process to proceed. The discussion of this subject was done on the Flume private list (14), with conclusion noted in (15). (1) http://s.apache.org/Ckq (2) http://s.apache.org/DBv (3) http://s.apache.org/5Am (4) http://s.apache.org/c5w (5) http://s.apache.org/iI5 (6) http://s.apache.org/lH (7) http://s.apache.org/MW7 (8) http://s.apache.org/p1w (9) http://s.apache.org/M86 (10) http://s.apache.org/Irr (11) http://s.apache.org/qO (12) http://s.apache.org/AiE (13) http://s.apache.org/4NE (14) flume-private@incbuator.apache.org Message ID: <CAHUddLNVVALXR+QyiRmNFCKs+2wcWvKpN22Pk_275p8D9SPw7g@mail.gmail.com> (15) flume-private@incubator.apache.org Message ID: <CAHUddLOrTrpQv7CSUm2Phjzof8ez6kapV=s_DpQXK6AgfGncTg@mail.gmail.com>