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.
>...resellers... bundle our software...
>
>They also use our documentation...
>hacking it about...misrepresenting ... misinforming... do not acknowledge
>...our documentation...or mention our product, as
>a component of theirs, by name.
>
>I'd like to know what's the industry standard on this?
The rights and obligations that you have are usually spelled out in
the contract with the reseller. It's been my experience that docs are
given minor consideration in such contracts. In general, your company
is responsible for providing a functional API and source documentation;
the reseller is responsible for paying your company for each product
that they sell with yours embedded in it. They are not responsible
for maintaining the integrity of your documentation, nor are they
responsible for acknowledging your product as a part of theirs,
*unless* the contract specifically states that they must acknowledge
your copyright. And if this is true, all they need to say is
"portions of this work are the copyright of MosaicSoft..." or
some such thing.
Best advice I can give you is to ship the docs out the door and
never look at them again. "Change what you can, accept what you
can't, recognize the difference" and move on.
