version-control-system: CVS server should be removed

It is still available as a package for raring, so why would we not document it in the serverguide? The serverguide doesn't recommend it, it just documents it.

I *strongly* support the removal of this section as well, for what it's worth.

The section is outdated and simply doesn't work anymore:
- The cvs package does not create a /srv/cvs directory automatically anymore (thankfully!), since something like hardy.
- The "importing a project" section is wrong, and "Project" is confusing in CVS parlance since the same concept was called "modules" at the time.
- Importing a project like this doesn't work (you need to login first)
- Setting up access rights for the newly created repository is a long stretch to document. The idea was originally to let all CVS users share a common login on the server system (yay!).

Furthermore, setting up CVS is an excercise in pain, and setting it up correctly (securely) is outside of the scope of this guide: by default CVS will send plaintext passwords over the wire.

People relying on CVS in this day and age will either not need this guide, or should really use a more modern source control system (bzr, svn, git, whatever) instead. If users *really* want to, they can still go through the CVS manual here: http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs.html

O.K. Chris: can this be assigned to you? I see you have taken on the entire Chapter 17 anyhow.

Sounds good!
Will push that asap.