Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 37837 invoked by uid 500); 5 Feb 2003 17:35:50 -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 37800 invoked from network); 5 Feb 2003 17:35:49 -0000 Message-ID: <3E414B77.2020701@anyware-tech.com> Date: Wed, 05 Feb 2003 18:35:51 +0100 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: fr, en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Should we move mailing list names? References: <3E40FA4A.3050404@apache.org> <20030205143233.GC951@expresso.localdomain> In-Reply-To: <20030205143233.GC951@expresso.localdomain> 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 Jeff Turner wrote: >On Wed, Feb 05, 2003 at 12:22:26PM +0000, Pier Fumagalli wrote: > > >>"Stefano Mazzocchi" wrote: >> >> >> >>>Jeff Turner wrote: >>> >>> >>>>On Tue, Feb 04, 2003 at 04:53:01PM -0600, Antonio Gallardo wrote: >>>> >>>> >>>> >>>>>What about: >>>>> >>>>>devel@cocoon.apache.org >>>>>user@cocoon.apache.org >>>>>doc@cocoon.apache.org >>>>> >>>>> >>>>That would be a severe break with tradition in Jakarta and xml.apache.org >>>>projects. IMO, consistency within Apache (particularly the Java-speaking >>>>parts) is more important than saving a few characters in the list name. >>>> >>>> >>>Totally agreed on the naming part. >>> >>> >>So? What names do you guys propose? >> >> > >IMO, whatever Ant and Avalon pick. +1 for switching to whatever (user@ >and dev@ sounds good) when they agree to switch too. > >How about sending round a mail to gain consensus? There are some tricky >issues (users@ vs. user@, cvs@ vs. commits@). > We also have to take into account the future subprojects of the Cocoon top-level project. In this perspective, the current Cocoon should be considered as the "core" of a group of related projects (CMS, GIS, webapp, etc.) In that perspective, I don't like stripping the distinctive part of mailing lists for a generic "dev@" if there is to be some "xxx-dev@" in the future. Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org