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.
I think this unlikely in most open source developments,
where the developers often only "explain things" to each
other through the message boards. A tech writer would
need to self-familiarize with the project the same way its
developers and users do - by downloading the various
builds, installing them, using them and scanning the
message boards for discoveries made by everyone else
on the project.
Gene Kim-Eng
----- Original Message -----
From: "voxwoman" <voxwoman -at- gmail -dot- com>
> I wish more tech writers would document open source software, because the
> documentation that is there reads like it was written by developers. Do
you
> have experience with the open source community - are the developers
willing
> to spend time explaining things to the writers so the writer can write
about
> it?
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-