Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 8870 invoked from network); 1 Sep 2005 06:41:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Sep 2005 06:41:08 -0000 Received: (qmail 74243 invoked by uid 500); 1 Sep 2005 06:40:44 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 73878 invoked by uid 500); 1 Sep 2005 06:40:38 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 73256 invoked by uid 99); 1 Sep 2005 06:40:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2005 23:40:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2005 21:39:20 -0700 Received: from fo2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id j814d3k1027576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 31 Aug 2005 23:39:03 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by fo2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id j814d2Rj027530 for dev@forrest.apache.org; Wed, 31 Aug 2005 23:39:02 -0500 X-Authentication-Warning: fo2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Thu, 1 Sep 2005 14:38:50 +1000 From: David Crossley To: dev@forrest.apache.org Subject: Proposal for Forrest-Cocoon-Lenya commit access Message-ID: <20050901043850.GC7996@igg.indexgeo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N There have been various discussions about this topic, some of them on various PMC mailing lists. There is no need for it to be private, so now it is in the open. The developer community needs to understand the background and the related issues. Private discussions do not enable the community to be involved. We all, especially new Forrest committers, need to understand the ramifications of this. The main effect that i see is that we would be opening up the Forrest repository to people that we do not know and are not familiar with. Is everyone happy with that. This proposal is not about making people from these projects members of the Forrest PMC. The process of becoming a PMC member is up to each project. At Forrest, our process is different to Cocoon's and i don't know about Lenya's. This proposal is only about convenience. Nothing is stopping anybody from sending patches to the other projects. Here is the proposal. After a chance for discussion then we can go on to vote about it. Normally we don't need to vote on things, but we do in cases of changes in project direction and community composition. Forrest commit access to Cocoon ------------------------------- Cocoon PMC has recently asked Forrest PMC if it would be useful for our committers to have access to their SVN repository. Cocoon commit access to Forrest ------------------------------- Back in July 2003 before Forrest became a top-level project, we decided [1] to give Cocoon committers access to the Forrest CVS Repository. That is something that we need to re-decide, so now seems a good time. The reason that we need to revisit, is that the formality for creating Apache Forrest as a top-level project includes defining our project guidelines which includes deciding who gets commit access. Forrest commit access to Lenya ------------------------------ Lenya have recently decided to give Forrest committers access to their SVN repository. [2] Lenya commit access to Forrest ------------------------------ These projects are trying to collaborate on better integration. It might make that easier if Lenya committers had access. Related issues -------------- Just so that the newcomers know, normally the process of going from developer to committer happens entirely within each project. You do not get commit access to other projects (other than xml-commons). This situation between the Cocoon-based projects is some new experiment. As is the norm, the PMC of each project has the final say over their own codebases and communities. With the code, they can veto a change and roll back the SVN. Even though these committers would have access, they need to pay attention to the desired direction of the project. If they don't understand that, then they should just contribute a patch. Such access is enabled by "svn authorisation". For example, here is the current cocoon definition: [groups] ... cocoon=stefano,balld,... list of all cocoon committers ... lenya=andreas,alexmc, ... list of all lenya committers ... [/cocoon] @cocoon = rw @lenya = rw #-- begin Cocoon GSoC students [/cocoon/gsoc/mpfingsthorn] mpfingsthorn = rw ... etc. See how they restrict access to certain parts for certain groups. Forrest currently only has one "group" and that is all Forrest PMC members. We also have this new concept of committers that are not PMC members. We don't have any of those yet. When we do, they would be a separate group. For example, Lenya has a "lenya-soc" group for their GSoC people. This proposal is only about the main groups. References ---------- [1] past decision about Cocoon access to Forrest http://marc.theaimsgroup.com/?t=105645457400003 http://marc.theaimsgroup.com/?t=105738941000001 [2] decision about Forrest access to Lenya http://marc.theaimsgroup.com/?t=112551792600003