SUMMARY: Document Management versus Document Version Control

Subject: SUMMARY: Document Management versus Document Version Control
From: "R. Downey" <rdowney -at- matrox -dot- com>
To: "Lisa Wright" <liwright -at- uswest -dot- net>, "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 3 Apr 2000 09:14:36 -0400

Hello List,
I received exactly three responses on this topic.

Renee L. LaPlume was the first one to respond.

As a lone tech writer, it was recommended I stick with MKS Source Integrity
as it does everything I need it to do, with little or no overhead. Renee
also sent along a copy of the presentation on configuration management
(version control and bug tracking) at an STC Management SIG
meeting. It includes a list of references which I found helpful for
additional information.

Renee you should send that file to for

John Solomon from SOLUTIONS, Inc. replied next.

He recommended I attend at least one Technical Writing conference this year
to try and solve my problems/questions. Specifically: The Publications
Management Clinic 2000
( and TECH/COMM Conference
2000 ( events.

The third was a request for a summary on the topic.

I have since tested RS-CVS and found it not as comprehensive as MKS.
Although if I did not already own a license for MKS, I would be using it.
The two programs are both designed for source code, not documents, and thus
treat anything not a text file as a binary.

For those of you out there playing with RS-CVS, or CVS specifically: a free
CVS book online and is available at
Rebecca Downey
Matrox Electronics Systems Ltd. Networks Division
Technical Writer
Email: rdowney -at- matrox -dot- com

Previous by Author: Performance Appraisal Dilemma
Next by Author: Re: The bottom line on professionalism in TW
Previous by Thread: RE: Networking (was: Silently screaming)
Next by Thread: Re. Bidding on editing work?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads