Return-Path: Delivered-To: apmail-lucene-lucy-dev-archive@minotaur.apache.org Received: (qmail 22962 invoked from network); 19 Jun 2010 02:55:34 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Jun 2010 02:55:34 -0000 Received: (qmail 6502 invoked by uid 500); 19 Jun 2010 02:55:34 -0000 Delivered-To: apmail-lucene-lucy-dev-archive@lucene.apache.org Received: (qmail 6442 invoked by uid 500); 19 Jun 2010 02:55:34 -0000 Mailing-List: contact lucy-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: lucy-dev@lucene.apache.org Delivered-To: mailing list lucy-dev@lucene.apache.org Received: (qmail 6434 invoked by uid 99); 19 Jun 2010 02:55:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jun 2010 02:55:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [68.116.39.62] (HELO rectangular.com) (68.116.39.62) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jun 2010 02:55:26 +0000 Received: from marvin by rectangular.com with local (Exim 4.63) (envelope-from ) id 1OPoD1-0003nQ-L8 for lucy-dev@lucene.apache.org; Fri, 18 Jun 2010 19:55:03 -0700 Date: Fri, 18 Jun 2010 19:55:03 -0700 To: lucy-dev@lucene.apache.org Subject: Self-governance Message-ID: <20100619025503.GA14433@rectangular.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) From: Marvin Humphrey X-Virus-Checked: Checked by ClamAV on apache.org Greets, A thread about Lucy recently wrapped up on the Lucene general@ list. http://markmail.org/message/iar5sbfqnzcsvro5 The board at Apache is breaking up umbrella projects. The Lucene TLP (top level project, as opposed to the Lucene Java subproject) has already spun off Tika, Mahout, and Nutch; Lucy is next. However, Lucy is not ready to become a TLP yet, so that spawned a discussion of what should happen. To summarize the outcome of the discussion: * Lucy must aim to "graduate" and become a TLP. * Lucy will stay where it is for now, rather than e.g. moving to the Incubator. * Lucy must regularly assess its progress towards graduation using the incubation checklist at http://incubator.apache.org/guides/graduation.html and report to the Lucene PMC. * No official deadline was set by the PMC, but Doug Cutting threw out "six months" and so we should probably start with that as our target. Here's a template for us laid out by Grant Ingersoll, the Lucene PMC chair: 1. Doing a release. 2. Showing some user list traction (i.e. real users) 3. Identifying and cultivating other contributors (via patches, discussions, JIRA issues, helping others, etc.) who can then become committers. The primary measure of success for a project at Apache is not technical: the goal is to create a robust meritocratic development community. In order to graduate, we will need not only committers and users, but our own PMC which takes responsibility for governing the project. http://www.apache.org/foundation/how-it-works.html#structure http://www.apache.org/dev/pmc.html Over the next week, we should perform a self-critique and create our first formal report, judging ourselves by the incubator criteria. Our biggest weakness from the ASF perspective, clearly, is that the project is too reliant on me and would be unlikely to survive my departure at this time. We should set a goal of making me dispensible. Here's where I think we stand with regards to Grant's plan, in a nutshell: Lucy's high-level design is done, and a lot of the coding is done as well. Developing and refining the Clownfish object model was the hardest part, and that finished up last fall. I think an initial release within 3 months is doable, and we may be able to accelerate that. I expect acquiring users after the release to be relatively straightforward. Near-realtime search powered by mmap is a killer feature. As for cultivating committers and PMC members, that will come naturally if we acquire a significant user base. I don't think we need to do anything special for now beyond releasing good software, publicizing it effectively, and making it easy and rewarding to contribute -- as we have tried to do over the last year with our existing contributor base, with some success. Marvin Humphrey