Re: [school-discuss] CVS vs wiki for book collaberation

["Matt Jezorek" <matt@bluelinux.org>]

I would agree 100% on that due to the abillity to step back in versions, see
more closely who made changes
and what changes are being made. And control who makes changes. You can
watch over what edits are done
by an editing team as well as you dont have to take notes on what was
edited/changed because CVS will do that
for you with timestamps and so on.

These are the basics. I can provide cvs services if needed as well

----- Original Message -----
From: "Karl O. Pinc" <kop@meme.com>
To: <schoolforge-discuss@schoolforge.net>
Cc: <Osswriters@members.iteachnet.org>
Sent: Wednesday, June 18, 2003 3:25 PM
Subject: [school-discuss] CVS vs wiki for book collaberation


> You might consider a CVS system (code versioning system)
> instead of a wiki.  It's
> designed to allow multiple people to collaberate
> without stepping on each other's toes and while keeping
> a complete log of all changes.  Changes can be rolled
> back or forward as well.  You can also authorize people
> to make changes in particular areas if you want
> authorization.
>
> http://www.cvshome.org/
>
> CVS is better suited than a wiki for projects which have
> something other than a wiki/web page final product.
>
> There are gui interfaces for windows machines,
> and maybe for Uhix too.  And the repository can be
> viewed from the web if you set up a gateway.
>
> The next generation of CVS is subversion, which you might consider
> .  It's in alpha,
> but the faq says it's usable and the subversion people
> have been using it themselves since Nov of 2001 to hold
> all the code for their project so it must work.
> It will be better than cvs.
>
> http://subversion.tigris.org/
>
> Find CVS add-ons at http://freshmeat.net.
>
> Karl <kop@meme.com>
> Free Software:  "You don't pay back, you pay forward."
>                    -- Robert A. Heinlein
>
>