Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 83176 invoked by uid 500); 9 Aug 2002 09:08:44 -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 83159 invoked from network); 9 Aug 2002 09:08:43 -0000 Message-ID: <3D538675.5090303@apache.org> Date: Fri, 09 Aug 2002 11:08:05 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [PROPOSAL] Cocoon-apps CVS module References: 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 Morrison, John wrote: > I'm +1 for a seperate -apps module. I'm assuming that > CVS commits would still come through to xml-cocoon2-cvs cocoon committers will be cocoon-apps committers "cocoon-apps"-only committers will not automatically be cocoon committers. > and there won't (?) be a seperate email list (atm) for > discussion? +1 for no separate list atm. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org