Hi fellow writers and editors:
We are mighty pleased to announce the opening of CVS for the Docs
Our intention is to have the lowest barrier to entry possible. After
getting our grubby little hands, uh, I mean, fine Elven fists on the
keys a few weeks ago, we have been formulating some philosophy and
guidelines to help make our experience nicer.
## Quick Version of How To Get CVS Access:
* Read the CVSAccess guidelines Wiki page
* Do a proper self-introduction to the list
* Show that you have something to put in CVS: as an editor by picking
something to edit, as a writer through producing a draft or working
* Use the proper process to get an account on cvs.fedora.redhat.com
. Put yourself in the 'cvsdocs' group and wait for approval.
This all presumes you have read the Documentation Quick Start and are
familiar with the Fedora Project Documentation Guide. Don't worry
about the DocBook/XML stuff right now. :)
## What Philosophy?
Golden Rule in effect. Treat others and their directories in CVS as you
would have them treat you and your files.
Only truly vital resources will have CVS ACLs. You are on your best
behavior as a community member to Do The Right Thing.
Don't put any illegal stuff in CVS. That would be BAD.
Don't attempt (or succeed) in cracking the CVS host systems, or use it
as a launchpad for crack attempts. That would be VERY BAD.
## Who Gets to Go Where?
Read the CVSAccess page for details. The quick version is that
assigned writer(s), editor(s), and a doc manager are the only ones who
should be messing around in a particular directory.
The doc manager is the single person accountable for what goes on in the
directory. It can be one of the writers, editors, or third person
otherwise not involved. To start, it's likely to be one of the FDSCo
members, lending a wise and guiding hand where needed. *cues ethereal
Each doc has one or more writers who must collaborate together within
the same repository. Thank ye gods for revision control!
An editor can edit for technical and grammatical/wordsmith details. The
editor must know and enforce the style guidelines from the Doc Guide.
There may be more than one editor to fill all the roles.
 Forthcoming URL _will_be_:
NOTE: URL does not work. We're, uh, editing it for style. Long story.
Coming Real Soon Now, with a shiny announcement.
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide