From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Documentation linkage or location
Date: Thu, 23 Oct 2003 11:49:16 +0200 [thread overview]
Message-ID: <20031023094916.GC1270@gentoo.org> (raw)
In-Reply-To: <20031023073846.GB21480@curie-int.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Thu, Oct 23, 2003 at 12:38:46AM -0700, Robin H. Johnson wrote:
> (3) Strongly consider implementing CVS ACL's (as used by BSD projects,
> PHP and others). This allows us to move the documents and improve on
> existing access control, such as allowing all editors and project
> members to have access to the documentation of a project.
I think it is still necessary to have a nice guideline on where certain
documentation is stored. Paul's proposal on having user documentation in
doc/, while developer documentation can be elsewhere (divided amongst the
related projects) is a nice idea which I can support.
The CVS ACLs can then be used to finetune permissions (which I also
encourage, both for security reasons as for managerial reasons).
By having all user documentation in doc/, translations are easily integrated.
Development-related documentation doesn't really need translations (my
opinion) and is therefor "safe" to reside in the project-specific structures.
Wkr,
Sven Vermeulen
--
^__^ And Larry saw that it was Good.
(oo) Sven Vermeulen
(__) http://www.gentoo.org Gentoo Documentation Project
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-23 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 7:30 [gentoo-dev] Documentation linkage or location Sven Vermeulen
2003-10-23 7:38 ` Robin H. Johnson
2003-10-23 9:49 ` Sven Vermeulen [this message]
2003-10-23 8:51 ` Paul de Vrieze
2003-10-23 9:52 ` Donnie Berkholz
2003-10-23 13:33 ` Sven Vermeulen
2003-10-23 17:09 ` donnie berkholz
2003-10-24 8:45 ` Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031023094916.GC1270@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox