Return-Path: Delivered-To: apmail-xml-cocoon-docs-archive@xml.apache.org Received: (qmail 29475 invoked by uid 500); 29 Oct 2002 06:02:39 -0000 Mailing-List: contact cocoon-docs-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-docs@xml.apache.org Delivered-To: mailing list cocoon-docs@xml.apache.org Received: (qmail 29465 invoked from network); 29 Oct 2002 06:02:38 -0000 Received: from pop017pub.verizon.net (HELO pop017.verizon.net) (206.46.170.210) by daedalus.apache.org with SMTP; 29 Oct 2002 06:02:38 -0000 Received: from verizon.net ([141.156.160.227]) by pop017.verizon.net (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP id <20021029060249.OLBF1423.pop017.verizon.net@verizon.net> for ; Tue, 29 Oct 2002 00:02:49 -0600 Message-ID: <3DBE245F.6000909@verizon.net> Date: Tue, 29 Oct 2002 01:02:07 -0500 From: Vadim Gritsenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-docs@xml.apache.org Subject: Re: [VOTE] Use Forrest to build Cocoon docs References: <3DBC6F24.4020009@apache.org> <1035775034.2525.5421.camel@ighp> <3DBD0FB5.6070304@apache.org> <1035870155.2524.8248.camel@ighp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at pop017.verizon.net from [141.156.160.227] at Tue, 29 Oct 2002 00:02:49 -0600 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: David Crossley wrote: >Nicola Ken Barozzi wrote: > > >>David Crossley wrote: >> >> ... >>>Also, why is this being copied to cocoon-dev. We agreed >>>that documentation stuff would get discussed only on >>>cocoon-docs working under the assumption that all Cocoon >>>developers are subscribed there. >>> >>> >>This is a VOTE for a structural decision in the Cocoon >>distribution, so it should always happen in the cocoon-dev >>list IMHO. >> >> > >When it is time for a vote, then maybe. > > > >>Also, lately there have been some crosspost by other developers >>here to cocoon-dev. >> >> > >Please do not just follow the bad habits of others. When we >set up cocoon-docs, we agreed that all docs-related stuff >would get discussed here. I again stress this part: >"working under the assumption that all Cocoon developers >are subscribed to cocoon-docs". Therefore no need to create >a Cc mess which is impossible to follow and to sensibly >reply across multiple lists. > I took the pain subscribing to this list (thanks god it's quiet there ;) so now I totally agree with you, no need for mess. >That is what we decided at list inception. If we are not >going to do it that way, then we should dump cocoon-docs >now and go back to cocoon-dev. > +1 in a sense "Let's discuss here." >>I'll stick to discussing here then, but I still think that >>the VOTE needs to go to both lists. >> >> > >Conducting a vote on two lists is ridiculous. Perhaps we >should discuss the PROPOSAL here, then decide where the >actual VOTE should happen. > How about making a proposal and then vote about where the VOTE should happen? :-P Vadim >--David > >