Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 18303 invoked by uid 500); 31 Mar 2001 23:40:14 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 18292 invoked from network); 31 Mar 2001 23:40:13 -0000 Date: Sat, 31 Mar 2001 18:40:38 -0500 (EST) From: Donald Ball X-Sender: To: Subject: Re: Central repository for taglibs In-Reply-To: <3AC4398E.4379665B@denic.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Fri, 30 Mar 2001, Ulrich Mayring wrote: > > Alternatively, do you need multiple committing accounts? Since nobody seems > > to know how many people are working on/would wish to contribute taglibs, > > maybe you can afford to start out with a central figure who does the > > committing. Contributors can email new taglibs or diffs. Something like > > this method would be required for new taglibs anyway, as they'd have to be > > checked for conformance and quality. > > Well, why don't we make seperate CVS areas, so that e.g. only Donald can > commit to esql and only I can commit to my taglibs etc.? Give the taglib > authors commit access to their taglib and nothing else - what is the > security problem here? i can just about guarantee that root isn't going to go for this level of micromanagemnet. plus, if you can't trust your friendly co-developers not to mess with your code, we've got a real problem. backing out of bad patches is easy anyway. - donald --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: