[thelist] Collaborative Environment Suggestions

[j.d. welch]

it's actually not a particularly unique situation; a great many open
source projects are comprised of a distributed team of developers
working remotely.  the machine you mentioned already has something that
does _exactly_ what you want: CVS (Concurrent Versions System).  the
server is included in a stock RH install. CVS works brilliantly for
webish text files; the comments are entirely separate from the files
themselves, as well as automatically taking care of the locking you
want.  rolling back to older versions of files is a cinch.   the
classic interface to it is, of course, the command line, but there are
pretty GUI clients for whatever platform you're working on.

http://www.cvshome.org/ is a decent place to start, or the old standby
'man cvs.' o'reilly produces a great little book on using it as well.
it's such a widely used package, there's a ton of information to be had
online about using it.

admittedly, it is a bit complicated to get going effeciently, but a
functional repository is _well worth_ the work (i even run it on my own
local machines to have accounting of versions of things i'm working on)

-jd


On Thursday, January 9, 2003, at 06:49  PM, Burhan Khalid wrote:

> Hello All :
>
> 	Came across a unique situation, and as always, I would like to
> consult the list for opinions.  I have been retained as a
> developer/system admin for a design house, however, they don't have
> any sort of version control/collaborative development envrionment in
> place.  It is getting to be a problem since almost all of the
> developers are telecommuting, and we are having problems with people
> updating files, and then not being up with the most recent version of
> a file.
>
> 	So, I am looking for some sort of version control system.  The
> platform is RH 7.2 shared server, and I do have root access via SSH
> (if that's a factor).  Any suggestions? Places where I should look?
> The files that we will be editing will be web based (HTML & PHP
> mainly).
>
> 	What I am trying to avoid are situations where the HTML and PHP files
> (mostly HTML) are choked full with comment tags. Besides the bloat, it
> doesn't look very nice when someone does a view source.  I would like
> a system that allows people to check out files, and have a separate
> file/place to have a log for the changes. If a file is checked out --
> then it should be locked so that other people may not modify it.
>
>
> As always, your suggestions are invaluable.
>
>
> --
> Burhan Khalid
> Email : burhankhalid[at]members.evolt.org
> Web   : members.evolt.org/burhankhalid
>
>
>
>
> --
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
>
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !
>
------------------------------------------------------------------
    J.D. Welch			|    so.there at showtunepink.com
    graphic designer    	|    http://www.showtunepink.com
    web developer       	|    https://kitschparade.ath.cx
------------------------------------------------------------------