Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 95401 invoked from network); 4 Apr 2007 04:23:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Apr 2007 04:23:04 -0000 Received: (qmail 74038 invoked by uid 500); 4 Apr 2007 04:23:09 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 73944 invoked by uid 500); 4 Apr 2007 04:23:09 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 73933 invoked by uid 99); 4 Apr 2007 04:23:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2007 21:23:09 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of hedhman@gmail.com designates 64.233.162.229 as permitted sender) Received: from [64.233.162.229] (HELO nz-out-0506.google.com) (64.233.162.229) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2007 21:23:00 -0700 Received: by nz-out-0506.google.com with SMTP id j2so23335nzf for ; Tue, 03 Apr 2007 21:22:40 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=d3si7SAm0LIujs9/3Co55K5p23g4Si+FGvB5T6pL+yW1yFY90GAtkfjLxgXNqsM6ibofSQuFxs//G/0cGro4S4S/N6i2I8Q7WScj7AYPjWxuhRPkKEdZVFjPcJWCqSu0NNUV1ieKgakB0PvWVAXqh4VgLUOZP6aLi8uh+NN6lWg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=RQZIWpHIG9gLc0adIoGjluq5Ye49vx2psDoaM9Y10yWraHHOnMevtHn0BBjLVVdx95ogIbIO0sCruF3NpbgQb9mKo/LyUhXOI3pFD9jPq4VlXn7teIsxcHxSBjipx7BJz4WbwTCdnV3d7ojiw8aTLPESa7Xurs4PnsxX7htLl7Q= Received: by 10.115.108.1 with SMTP id k1mr80360wam.1175660559694; Tue, 03 Apr 2007 21:22:39 -0700 (PDT) Received: from f3.local ( [202.146.77.122]) by mx.google.com with ESMTP id n22sm899781pof.2007.04.03.21.22.37; Tue, 03 Apr 2007 21:22:38 -0700 (PDT) From: Niclas Hedhman To: general@incubator.apache.org Subject: Re: Question about the PMC structure for graduating projects Date: Wed, 4 Apr 2007 12:22:31 +0800 User-Agent: KMail/1.9.5 References: <4AFC0C76-3AE8-4291-BB65-A10316C1CE90@hogstrom.org> In-Reply-To: <4AFC0C76-3AE8-4291-BB65-A10316C1CE90@hogstrom.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704041222.31086.niclas@hedhman.org> Sender: Niclas Hedhman X-Virus-Checked: Checked by ClamAV on apache.org On Wednesday 04 April 2007 11:10, Matt Hogstrom wrote: > Is it standard practice to take the existing PPMC forward to the > board or can the project, in its discretion, suggest a PMC made > up of a different group of members? The 'standard' practice is that the PPMC is moved forward to the new TLP project's PMC. It has also been 'standard' that the committers are kept as-is. However, some communities have arranged for 'clean up' operations prior to the graduation proposal in collaboration with the Incubator PMC. AFAIK, this is done in discussion with the people involved to limit any bad feelings. End of the day, the purpose has been to keep the 'active' community. But there are no policy in place (AFAIK). Discussions has occured whether 'previous to ASF active' people should be committers or not. I don't think there are any definite conclusion on that, and handled case by case. > For instance, the initial PPMC was made up of mentors as > well as committers. However, the composition of the proposed PMC is > missing many of the committers that have been active and working on > the project for sometime. Is it appropriate to include those members > in the proposal or simply stay with the PPMC and build the new PMC > after graduation? Personally, I am of the opinion that all committers should be PMC members, but it is for each PMC to decide how they handle questions like these. I hope that helps. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org