Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 5437 invoked from network); 21 Apr 2008 02:31:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Apr 2008 02:31:36 -0000 Received: (qmail 92546 invoked by uid 500); 21 Apr 2008 02:31:37 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 92497 invoked by uid 500); 21 Apr 2008 02:31:36 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 92486 invoked by uid 99); 21 Apr 2008 02:31:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Apr 2008 19:31:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO py-out-1112.google.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2008 02:30:52 +0000 Received: by py-out-1112.google.com with SMTP id a25so1831288pyi.11 for ; Sun, 20 Apr 2008 19:31:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=RZBVjVqs5lfa5aoKvPXEYo8RyeD2PBdwQ3MU5d5P1JI=; b=s2uTtO3l9RL4QloJhTrbs3IEXlJXehHXsmiKFAZIen3r2ns9SFZS6nQO4vGN0/Er4eqNM22e3rB9wHoFTAnfY1jCHjjXGh1fiyBYdNRsINA4cJcmOFp4dQC8h/Z1SUob1A6u3kpTroWrqnfHxz0QJYwJJEG0Kc6YFDUUszOHElw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=s782B61w/VAl9AdBHkLUIJQj2tydTOsGzQiDJOVZQHGK1kJnH40ZBOuRwhgo6iVgcMKVrDuG8tFSow4QbgBiNeetpZAwWaTsh+PA1HtZMJKPc9btpHJRwE7UpO4OwzVMX68RI0HTEkbz+5YDbpR2V5qnmP7jyUs2rb5eho+rDNw= Received: by 10.35.77.18 with SMTP id e18mr9570097pyl.46.1208745064902; Sun, 20 Apr 2008 19:31:04 -0700 (PDT) Received: from ?10.10.10.26? ( [64.128.46.190]) by mx.google.com with ESMTPS id w38sm9256237pyg.3.2008.04.20.19.31.02 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 20 Apr 2008 19:31:02 -0700 (PDT) Message-Id: <6533347D-CB05-4579-BEA0-55802E6DA852@gmail.com> From: Kevan Miller To: dev@geronimo.apache.org In-Reply-To: <3B641173-E128-4C75-B8C7-D8A96539AE17@visi.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Re: [DISCUSS] Policy for granting write access to our Wiki Date: Sun, 20 Apr 2008 22:31:01 -0400 References: <4E1CC14F-B064-40D8-9ACA-1E84DACA66CF@gmail.com> <3B641173-E128-4C75-B8C7-D8A96539AE17@visi.com> X-Mailer: Apple Mail (2.919.2) X-Virus-Checked: Checked by ClamAV on apache.org On Apr 18, 2008, at 5:41 PM, David Blevins wrote: > It's already ASF policy that an ICLA be on file for anyone to get > write access to a confluence space used for official documentation > or a website (plain "wiki" usage is exempt). Updated a good 40~ > cwiki spaces to use the asf-cla group instead of confluence-users, > including ours, a couple weeks ago after some abuse so we're > compliant with the minimum policy. > > Some groups, like the Incubator, are talking that you need to be a > committer to get write access -- not just have a CLA on file. I'm > not sure I see the need for raising the bar that high. I like the > idea of the check box as an alternate to having a CLA on file, > assuming this is kosher with infra. All, I found the following source of documentation on the subject -- http://cwiki.apache.org/CWIKI/#Index-Ifweusethewikitomaintainprojectdocumentation%2Carethereanyspecialconsiderations%3F Looks like we have some choices. One of the decisions will be what to do about documentation that has already been contributed without a CLA. I'd like to hear what the community thinks we should do... --kevan