Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 41350 invoked from network); 17 Oct 2007 02:13:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Oct 2007 02:13:24 -0000 Received: (qmail 52047 invoked by uid 500); 17 Oct 2007 02:13:11 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 51877 invoked by uid 500); 17 Oct 2007 02:13:10 -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 51866 invoked by uid 99); 17 Oct 2007 02:13:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2007 19:13:10 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.208.196.171] (HELO outbound.mailhop.org) (63.208.196.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2007 02:13:13 +0000 Received: from adsl-074-229-183-095.sip.rmo.bellsouth.net ([74.229.183.95] helo=[10.0.1.7]) by outbound.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1IhyOv-0008dw-KT for general@incubator.apache.org; Tue, 16 Oct 2007 22:12:52 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 74.229.183.95 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/QeMnAoR2BkNw5hs0sAAU3 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <3C6A8656-5288-42D5-889D-8B328CC325AC@SUN.com> References: <96241AD6-E768-49E4-85D1-360F2D239F43@hogstrom.org> <471543D3.7050108@hursley.ibm.com> <3C6A8656-5288-42D5-889D-8B328CC325AC@SUN.com> Content-Type: multipart/alternative; boundary=Apple-Mail-1--468395964 Message-Id: <292B4339-96E6-443F-B484-D825C70F5DF4@hogstrom.org> From: Matt Hogstrom Subject: Re: Graduation: how do we check "three or more independent committers" ? Date: Tue, 16 Oct 2007 22:12:48 -0400 To: general@incubator.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1--468395964 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Here is a quick initial definition. I believe that it is the committer's responsibility to properly state their affiliation. For instance, if a committer contributed to a project and it was approved by their employer (company A) but not actually part of their immediate duties I wouldn't necessarily expect them to have to say I am affiliated with Company A and they might identify themselves as independent. An underpinning of this definition is trust. Affiliation: For purposes of identifying a community's diversity and independence it is useful to identify a committer's afiliation. It is useful to disclose to the community if a committer is working on a project as part of their primary job responsibility. This can be loosely defined to mean paid to work on a project more than 4-hours a day. This affiliation can be used to identify a project that would be in jeopardy should an organization that is supporting developers should those developers time be redirected to unrelated efforts. On Oct 16, 2007, at 8:21 PM, Craig L Russell wrote: > I do think it would be good to clarify the meaning of affiliations, > and make it more flexible. > > This topic has been kicked around for a while. Is there some > consensus that affiliation is project-specific, such that a > committer can be independent on project A while working on another > project B as their "day job"? --Apple-Mail-1--468395964--