Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-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 DB12DD653 for ; Thu, 15 Nov 2012 23:30:59 +0000 (UTC) Received: (qmail 10075 invoked by uid 500); 15 Nov 2012 23:30:59 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 10042 invoked by uid 500); 15 Nov 2012 23:30:58 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 10032 invoked by uid 99); 15 Nov 2012 23:30:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 23:30:58 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-we0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 23:30:51 +0000 Received: by mail-we0-f175.google.com with SMTP id t44so783862wey.6 for ; Thu, 15 Nov 2012 15:30:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=aEDaRwsNpYY/cgbzXR84GfaplY2G0NpkOQEZ177oCLs=; b=YGmTxGeuYFKKo9nWDPDgUJJY1akSJ7ypsMxcJDOED5KPJsscqThqM6AdhGiJwuXi8W kRRgG80X3zVcA+lcHHeRKLMBHE9oIFGYyNlDnMDl6UBVj2h3ofS5ddMbxTfl4ggG1waR IkjyWkmfBSyy0CxfhZg7m7z+yYja2ohtiQwWFNbq0Amnoe6/EG8WR/DyDVLo2UOLNGi3 sayA5viEzi4A2pfizzBrSQn1w4J2Kt28mUSuoLVbFwAS5daXIWXbWNG1iGaambnsI38M N09rbNi/ehPstXZ9TI+IHCIjX9Fsin8763cjneIuROp0ovmPDdCz7KQDZdfGmu7kK9++ 4GuQ== Received: by 10.216.211.19 with SMTP id v19mr1227643weo.91.1353022231841; Thu, 15 Nov 2012 15:30:31 -0800 (PST) MIME-Version: 1.0 Sender: omuppi1@gmail.com Received: by 10.194.91.176 with HTTP; Thu, 15 Nov 2012 15:30:01 -0800 (PST) In-Reply-To: References: From: Om Date: Thu, 15 Nov 2012 15:30:01 -0800 X-Google-Sender-Auth: rcfi4VXAzqox1Rl_a-Vhaj0w7eI Message-ID: Subject: Re: List of Inactive Apache Flex PPMC Members To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6dbe932808b0d04ce910942 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dbe932808b0d04ce910942 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Nov 15, 2012 at 2:13 PM, Michael A. Labriola < labriola@digitalprimates.net> wrote: > >Just to be clear, I'm not trying to kick anybody out. I only think it's > >fair that we hold the PMC members to the same standards as we do > >prospective committers, don't you? > > Well, to be fair, I sort of actually hate that too... > > What does it mean to commit time to a project like this? Is it only code > commits that count? That seems like a narrow vision of what's important to > a project like this. > > What about people who present, write about or educate on Flex? Worked on > getting/keeping Flex inside of corporations during our transition time to > Apache? People raising awareness... you get the point. If there is one > thing I find a little disturbing about the idea of PMC and Committers being > the same group is that it seems to value code commits above all else. In my > opinion that is a fraction of what makes any project/product successful. > > When I first read about Apache I actually thought these were two separate > groups most of the time and found it slightly disappointing that they seem > to be more aligned than not. > > Mike > > You are right, PMC members dont necessarily have to contribute code. But they have to contribute something - anything. Pick from the list you mentioned. We also have committers who are not PMC members. We have been careful not to automatically elevate a committer to a PMC member. There are a fairly significant number of non-coders in the current PMC. Maybe they should actively recruit folks that do interaction design, evangelism, etc. The lack of such activity does not mean that we should not invite new coders/committers into Apache Flex. More of both is what we need. I have personally reached out to non-coders who have been active on this list to see if they are interested in becoming PPMC members. And we should all be doing that regularly. But this is tangential to the current discussion. Erik raises a valid question here. We are at the cusp of graduating and we need to figure out what standards we want an Apache Flex PMC member should be held to. Lets all agree to a standard and start adhering to it. Thanks, Om --0016e6dbe932808b0d04ce910942--