Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D0BA76D14 for ; Fri, 24 Jun 2011 13:49:00 +0000 (UTC) Received: (qmail 23503 invoked by uid 500); 24 Jun 2011 13:49:00 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 23467 invoked by uid 500); 24 Jun 2011 13:49:00 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 23459 invoked by uid 99); 24 Jun 2011 13:49:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2011 13:49:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rabastus@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2011 13:48:54 +0000 Received: by iym10 with SMTP id 10so2576642iym.6 for ; Fri, 24 Jun 2011 06:48:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=DDxRqg+lL6ZjriJdpAi2uQKBdETXfZg/bcxGqUKj61M=; b=Vh/spTgIY3wWbcM6cayUHcdgC7e4NBmPB3gV8IPiQmoDeTFg0Lim1LnyPwnHIxWZzt riuO9b5wxRBlreD89Yts711CICnt+/lJusennH0srwXzWsiEDDApTwDr7E0lf9pCesEn +IB7GjQ9NyVlM1OjVLnsWKS/T0EZ6uRC96ry0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=fepKubqxkeAAGQLayDmxMDIgE7gpQ8xwu2WcabEHmDhlIdYcA1E2GFw+8Ns+gcE41j UNbaCzk+1z8LJ4rkbRiq8aMUQhqze+II0xn4tHOujQGvN6dmB/TTh/ayDL/94hlyL9PZ 6J25BLPeN1OfOInMakvdnHmDbUB2tBZLQ3+6U= MIME-Version: 1.0 Received: by 10.42.225.70 with SMTP id ir6mr3541511icb.494.1308923313729; Fri, 24 Jun 2011 06:48:33 -0700 (PDT) Sender: rabastus@gmail.com Received: by 10.42.213.71 with HTTP; Fri, 24 Jun 2011 06:48:33 -0700 (PDT) Date: Fri, 24 Jun 2011 09:48:33 -0400 X-Google-Sender-Auth: CE_Caasg77M6dcPvSpGTisAYyAs Message-ID: Subject: Contributors versus Committers versus PMC members From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Since almost all of us are new to Apache we're learning a lot about how Apache projects organize themselves. Based on my reading, I understand that Apache projects have three degrees of participation: 1) Developer (or Contributor might be the preferred term, since it doesn't depend on coding), who is a project member that contributes patches, helps with support, reports bugs, etc. The main thing they cannot do is commit changes directly to the product repository. They need to submit patches, which are then reviewed and checked in by a "committer". 2) Committers are elected based on their sustained contributions to the project. They have an apache userid and email alias. They can commit changes to the repository. They are also responsible for reviewing patches submitted by other contributors. A Committer must have an ICLA on file. 3) Project Management Committee (PMC) are Committers or Contributors who are elected, based on merit, to help provide oversight to the project. They approve releases and elected new Committers and PMC members. As the Apache OpenOffice podling was bootstrapped, all of the volunteers who signed up on the wiki, before the vote, were automatically able to become Commtters and PPMC members. But to actually take on those roles, a number of steps needed to occur, mainly dependent on the new member submitting the Apache ICLA. Once that is done, account creation, etc. takes some time, but is routine. What we need to decide going forward is how we define the details of the Contributor/Committer/PPMC roles. Specifically: 1) In the future, will all Committers be PPMC members? In other words, will these two groups be identical? I've heard that other Apache projects have a subset of Committers serve on the PMC, but they rotate membership, so all Committers get a chance to be on the PMC. 2) If the Committer and PPMC groups are not identical, then what criteria should we use to determine who becomes a PPMC member? 3) If someone is offered the role of Committer, how long do they have to sign ICLA? 4) If someone is an incredible contributor to the project, say in testing or event planning, can they become a PPMC member? Would they need to sign the ICLA even if they are never actually need to commit project resources? In other words, can someone be a PMC member without being a Committer? Or should we think of these as being progressive degrees of involvement, strictly Contributor --> Committer --> PMC member? 5) Is there an term limit on PPMC membership, or criterion for sustained contributions and activity level? In other words, is it a case of "Once elected, always a PMC member"? 6) Similar for Committers. Is there a minimum threshold level of activity that is needed to sustain that role? -Rob