TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Document Control vs Source Control From:Michael Collier <mcollier -at- CSC -dot- COM> Date:Fri, 25 Sep 1998 13:43:55 -0500
I would say that this is not uncommon. Source control programs can manage all
kinds of file types. You don't get all the functionality of a document mangement
system, but then you don't have deal with all the overhead involved either (set
up, training, managing it).
joe -at- manage -dot- com on 09/25/98 01:07:45 PM
Please respond to joe -at- manage -dot- com
To: TECHWR-L -at- listserv -dot- okstate -dot- edu
cc: (bcc: Michael Collier/FSG/CSC)
Subject: Document Control vs Source Control
This is a multi-part message in MIME format.
--------------E41AF98EDF82AA7C5C17DB82
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
The engineers in this company use a source-control product called MKS
(Source Integrity). Formerly, they used StarTeam but switched over.
I've been asked to use MKS for document control (the user guides, etc.).
I'm reading the MKS manual and creating a project which includes check
in, check out, version control, etc.
However, the manual is obviously written for programmers and I'm
wondering if it's common practice for tech pubs to use the source
control software too, or whether they pay extra and use software
designed for doc projects?
