Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 3198 invoked by uid 500); 17 Aug 2000 18:18:10 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 3183 invoked from network); 17 Aug 2000 18:18:10 -0000 Date: Thu, 17 Aug 2000 12:14:47 -0600 (MDT) From: Marc Slemko To: new-httpd@apache.org Subject: Re: Removing apidoc from 2.0 In-Reply-To: <399C26AA.97FA8915@Golux.Com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, 17 Aug 2000, Rodent of Unusual Size wrote: > rbb@covalent.net wrote: > > > > If nobody complains, I would like to remove the apidoc directory > > from the 2.0-httpd-docs tree. > > The problem with this is that it defeats the purpose of enabling > non-coders to work on the documentation. The way things are now > in 2.0, only someone with commit access to the source tree can > do diddly with the docco. > > -1 until we figure out a solution to that. As I have said numerous times in the past, there is absolutely no need to put docs into a separate top level directory in the CVS repository to allow differing commit access to them. If you want to allow a different set of users to commit to a certain subdirectory, simply make all the files in that subdirectory owned by a separate group. End of story. There is nothing magic as far as permissions go WRT what level within the CVS repository the directory is at.