From cocoon-dev-return-28952-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org Mon Jul 01 12:52:05 2002 Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 14312 invoked by uid 500); 1 Jul 2002 12:52:05 -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 14301 invoked from network); 1 Jul 2002 12:52:04 -0000 Date: Mon, 1 Jul 2002 14:52:03 +0200 From: Christian Haul To: cocoon-dev@xml.apache.org Subject: Re: [doc] policy for authorship credit Message-ID: <20020701145203.U4634@bremen.dvs1.informatik.tu-darmstadt.de> Reply-To: haul@dvs1.informatik.tu-darmstadt.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i Organization: Databases and Distributed Systems Group, Darmstadt University of Technology X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N On 01.Jul.2002 -- 08:33 AM, Diana Shannon wrote: > I need your input on how to think about bylines Cocoon docs, both > community-contributed and core docs (soon to be patched by new > volunteers). I for my part wouldn't mind a list of authors and contributors to docs in a single file and to remove them from the particular docs altogether. IMHO "authorship" with code is useful because I know who to bug for information :-) Perhaps an internal attribute who feels responsible for a particular document would suffice. Chris. -- C h r i s t i a n H a u l haul@informatik.tu-darmstadt.de fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org