Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 37669 invoked by uid 500); 22 Apr 2002 12:27:32 -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 37651 invoked from network); 22 Apr 2002 12:27:31 -0000 Message-ID: <3CC401EE.3000601@apache.org> Date: Mon, 22 Apr 2002 08:28:30 -0400 From: "Andrew C. Oliver" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [input needed] --- documentation questionnaire --- 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 I'm fine with that as long as documentation-related posts to cocoon-dev are never considered off-topic. The developers should not get to pack themselves into an ivory tower never to have to worry about documentation ever again. Sometimes creating a new list encourages traffic, sometimes discourages. -Andy Diana Shannon wrote: > Andrew: > >>> >>> 3. Form documentation team. High priority. >> >> >> elaborate what you mean by this... > > > Sorry this wasn't clear. > > A number of people have emailed me privately with offers of help. I > want to make sure they have what they need (information, templates, > editorial/review support) to be able to start contributing. I'm *not* > trying to formalize this process or limit anyone's participation. > Still, there's probably a need -- in the future -- for a group of > people (again, no limits to participation) to discuss/debate some > narrow documentation/editing issues before proposals/plans/updates are > posted to cocoon-dev. FYI, Apache has a separate cvs/list for its > documentation subproject. Cocoon attracts a lot of content management > people who probably know volumes about documentation best practices. > IMHO, if this discussion exists *only* on cocoon-dev, I'm afraid some > Cocoon users might be overly limited in their input. Speaking as a > Cocoon user, it can be intimidating to post to cocoon-dev. > > Diana > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org