Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 37501 invoked from network); 6 Jul 2007 20:31:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jul 2007 20:31:31 -0000 Received: (qmail 16566 invoked by uid 500); 6 Jul 2007 20:31:32 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 16498 invoked by uid 500); 6 Jul 2007 20:31:32 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 16487 invoked by uid 99); 6 Jul 2007 20:31:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2007 13:31:32 -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 phil.steitz@gmail.com designates 64.233.184.226 as permitted sender) Received: from [64.233.184.226] (HELO wr-out-0506.google.com) (64.233.184.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2007 13:31:27 -0700 Received: by wr-out-0506.google.com with SMTP id i23so272717wra for ; Fri, 06 Jul 2007 13:31:07 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PTh9x8u3r9+9A7QCc0I3clFFphw20w67DcjI623kwhIO8S/eILt9A12AjXsJUsBaGNrCxIh6mmkxXDeZ8CAiAm6zMmdfjJwPtjwb2iuQL0ytLneqNW226v1n8ufe+0b/zzIppg9K02EFO/O8PlrFfzKIk6Mg/ZKr8bU8HYMtOZA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=T/lf24Eu5UyDgGE0T1xwvYokP4yaZpxLpTqJKnz1i6zQL1sbLWuQsCEe1WLtwNXn4rYwoWlStQoTDDsYKyheS/kXghY5e9F5yFul9tT2rTFBv2giHsLxxv/koMfiLBY1xKdkjkZ6ql6UijOUVK0rSU1g3+v/4wyIpqmE88lZvH8= Received: by 10.78.171.13 with SMTP id t13mr524653hue.1183753866284; Fri, 06 Jul 2007 13:31:06 -0700 (PDT) Received: by 10.78.107.15 with HTTP; Fri, 6 Jul 2007 13:31:06 -0700 (PDT) Message-ID: <8a81b4af0707061331p2ed806eh70fe09172d4480f5@mail.gmail.com> Date: Fri, 6 Jul 2007 13:31:06 -0700 From: "Phil Steitz" To: "Jakarta Commons Developers List" Subject: [proposal] No VOTE needed to elect ASF committers to commons WAS: Re: request karma to commons validator/i18n MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org On 7/6/07, Henri Yandell wrote: > On 7/6/07, Niall Pemberton wrote: > > On 7/6/07, Paul Benedict wrote: > > > I would like to commit to commons validator and commons i18n to enhance > > > them for Struts. For validator, I want to add and finish some issues in > > > the current snapshot, and, respectively, port some good i18n code from > > > other Apache projects. Can I get karma for this? > > > > Although Commons has a liberal policy on giving Karma to ASF > > committers a better (more ASF like) first step IMO would have been to > > start talking about what you want to do first - a good recent example > > of that is Dain: > > > > http://tinyurl.com/yrmgpf > > > > Even though I'm already a committer I still regularly create Jira > > tickets and post patches (for code changes) to components that I don't > > have much history on rather than diving straight in. I'm hoping > > you'll do the same, 'coz I'm going to be unhappy if I start seeing > > Validator commits with no prior discussion. > > Ack - Martin just pointed out that it's Sandbox karma on request, not > all of Commons. > > I'll adjust - ie: Paul will have commit for i18n, but we'll have to > vote to give him commit to validator. > Sorry, I thought we had changed that policy, so I guess I would like to propose that we change it now. It does not really make sense to me to distinguish the sandbox and I think we should make it as easy as possible for existing ASF committers to contribute to commons. So my proposal is that any ASF committer who wishes to become a commons committer just needs to make that request here on the commons-dev mailing list and they will granted karma for both commons proper and commons sandbox. Expectation is of course that ASF committers joining the commons will "behave" (http://wiki.apache.org/jakarta-commons/JakartaCommonsEtiquette). As an alternative, we could discuss requests for karma from ASF committers on private@ (good sign that we have not even created that yet :) but I don't personally see the need to do that. In any case, I don't think we should revert to the old practice of public committer votes (whether or not the individual is a current ASF committer). Phil --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org