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: Green Field ! From:Me Too <klhra -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 4 May 2006 10:22:40 -0700 (PDT)
Congratulations. IF you are given the autonomy and
authority to really do the job. If not, John Posada is
right and the car behind those headlights is about to
do a number on you.
Before you do anything else, talk to the
managers/execs and get yourself officially plugged
into the project planning teams. Make sure you really
are in the pipeline for distribution of info about
design changes, project schedules, etc.
For version control, might as well just stick with
VSS. It does *everything* you need for documentation,
it's fairly simple and easy to use, and pretty well
known so if any problems do erupt, there's lots of
users who can provide advice. For version control,
avoid Perforce and Rational like the plague. They are
WAY more difficult to use and they do not one tiny
thing more for documentation - 99% of their "features"
are completely useless on binary files.
A more important thing for version control is getting
everyone else to agree to a standard file name
convention. I wasn't able to do that here, so the BAs
and PMs do their own 'versioning' by sticking their
own version numbers in the file names. I wind up with
the VSS database containing 7 different file names,
which sort of defeats the purpose of having a version
control system.
I recommend (if you can do it) setting up the VCS so
you are the only one with access to the area where
documents are kept. You can put a site on the company
intranet where other people can download the latest
versions of your docs - and of course keep the files
accessible there always up to date. That way everyone
can always get the latest thing quickly and easily,
but they can't get their hands on the working copies.
And of course, talk to the local webmaster/system
admin and make sure you're the only one who has
write/delete permissions on the intranet directory
where you put the distribution copies.
Good luck and have fun.
----------------
Keith Hood
Senior (only) tech writer
ACS, Inc.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l