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.
Re: Using Synergy configuration management system with Frame
Subject:Re: Using Synergy configuration management system with Frame From:Robert Lauriston <robert -at- lauriston -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 18 Nov 2009 09:20:57 -0800
Your original post said your development team would like you to use
Synergy "to store FrameMaker files and better track changes in
documentation."So the docs department has no goal here except to
satisfy dev, is that right? If so, you could probably just check in
everything every night and check it back out (or check it in while
keeping it checked out, if Synergy has that feature) without changing
your procedures at all. That would give you a daily backup / change
archive in the system.
As a writer, I doubt I've ever spent more than five minutes a week
dealing with a version control system. I've spent a lot of time
working with them in an administrative capacity, when setting up
automated build procedures, migrating from SourceSafe to Perforce, and
so on, but they're no big deal for end users.
I've never been in a situation where we purchased a VCS specifically
for documentation, it's always been an easy choice since the
programmers were using one anyway.
Do you have both Rational Synergy and Rational Change, or just Synergy?
2009/11/18 GILLIOTTE Valérie <vgilliotte -at- mega -dot- com>:
> @ Chris : about the screenshots being in the same directory. The reason was that some screenschots were shared between projects. But you're right, it could be a problem if we want to take a project with us ... Up till now it has not been a problem, which does not mean it won't be in the future.
>
> @ Robert about "You can get or update local read-only copies of the files without checking them out"
> I had not understood that part ...
>
> One of my developers told me it could take about 1O% extra-time to work with a source control system ... Are you OK with that as far as documentation is concerned ? It could bring advantages just before the release of a version, with a burden for the rest of the time. We have to figure out if it is worth it ... and if we are prepared to change a bit our processes.
>
> I don't kwow why, but I have the impression that a source control system would be most cost-efficient when working with a modular documentation based on small topics, which is not our case ...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. Easy to use
but still has all the power you need. Get results fast in an intuitive
authoring environment that works like a familiar word processor. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
