Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 33355 invoked by uid 500); 21 Feb 2003 21:19:27 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 33332 invoked from network); 21 Feb 2003 21:19:27 -0000 Received: from fo1.kc.aoindustries.com (209.15.201.17) by daedalus.apache.org with SMTP; 21 Feb 2003 21:19:27 -0000 Received: from apache.org ([66.208.12.130]) (authenticated) by fo1.kc.aoindustries.com (8.11.6/8.11.6) with ESMTP id h1LLJWf09411 for ; Fri, 21 Feb 2003 15:19:32 -0600 Message-ID: <3E5697E0.10704@apache.org> Date: Fri, 21 Feb 2003 16:19:28 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [PMC] bootstrapping the PMC References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Giacomo Pati wrote: > On Thu, 30 Jan 2003, Berin Loritsch wrote: > >>The PMC is not responsible >>for code, they are responsible for community. > > > Hmm.. IIRC I remember dicussions held at Apache Con in Las Vegas where the > general expectation was that a PMC *is* responsible for the code > at least concerning licensing issues (Jakarta being to big for code > oversight of the PMC). This is one of the reasons why this restructuring > of ASF projects (promoting sub project like Cocoon and Avalon as top > level projects) takes place. That doesn't negate what I was trying to communicate. The PMC is responsible for legal issues--which is essentially a community issue. We all are responsible for making sure that the code and JARs stored in the CVS is compatible with ASF licensing (in the code example it has to be ASF license...). All I was saying is that the PMC does not direct the technical direction of the Cocoon project.