staging server draft for discussion

[Karsten Wade]

# This is my first brain dump of what a staging server should do for
# FDP

Fedora Documentation Staging Server (codename: alexandria)

The purpose of alexandria is to provide a consistent build environment.
The latest code is pulled from CVS continously and is on a rolling
autobuild.

This eliminates local differences in environment and toolchain.  A
writer can work locally with whatever envar they prefer, but the final
documentation is always pulled from alexandria.

Writers who cannot have a local toolchain may use the autobuild as a
remote build machine.  Writers then edit and check-in, using the
autobuild page to view the newly built document or check the error log.

This provides a single location that all beta documentation can be
viewed, for people inside and outside of the project.

## 30 ##
-- 
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
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-dsco-list/attachments/20050621/694210d8/attachment.sig>