RE: TECHWR-L Digest, Vol 28, Issue 23

Subject: RE: TECHWR-L Digest, Vol 28, Issue 23
From: "Ray Saffin" <rsaffin -at- serena -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 26 Feb 2008 16:13:40 -0000

Page 2 of Version 1.5.4 of the Doxygen manual has the following sentence
at the end of the "Doxygen license" section:

"Documents produced by doxygen are derivative works derived from the
input used in their production; they are not affected by this license."


Message: 4
Date: Mon, 25 Feb 2008 20:47:10 +0530
From: "Edgar D' Souza" <edgar -dot- b -dot- dsouza -at- gmail -dot- com>
Subject: Re: Doxygen for commercial documentation?
To: "Ethan Metsger" <emetsger -at- obj-sys -dot- com>
Cc: John Harrington <beartiger -at- gmail -dot- com>, techwr-l -at- lists -dot- techwr-l -dot- com
<60ecd5ce0802250717l35b1f469qa2e6ae9e70e83560 -at- mail -dot- gmail -dot- com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Feb 25, 2008 at 6:57 PM, Ethan Metsger <emetsger -at- obj-sys -dot- com>
> On Sat, 23 Feb 2008 16:48:14 -0500, Moshe Kruger (AllWrite)
> <moshe -dot- kruger -at- gmail -dot- com> wrote:
> > The GNU GPL limits the distribution of software. It seems,
> > that
> > your question seems invalid as far as documentation goes, for in
> > case of
> > documention *no software* is distributed.
> I mentioned this off list, I think, but the GPL only applies to
> released under its provisions. The documentation you create for your
> software is not governed by the GPL,

I can't help but wonder if the original poster, should he have been
using Microsoft Word, would have assumed that all documents created
using that word processor automatically belonged to Microsoft. Or that
all pictures he sketched using a pencil from Faber-Castell
automatically belonged to that company. To borrow an old quote
attributed to Charles Babbage: I am not able rightly to apprehend the
kind of confusion of ideas that could provoke such a question!

It seems to me like the OP has been subjected to some not very
accurate "fundamentals" about open source and the GPL.

Actually, I would be more worried about a Microsoft EULA, which takes
away pretty much all my rights with respect to the software, **after**
I have broken the seal on the package (how's that for slick business
sense, boys?) and without acceptance of which the software just won't
install. Sure, open-source software has bugs. ALL software has bugs;
if you think yours doesn't, give me a week testing it...
muahahahahahaaaa!!! :-) Purely from the wallet point of view, though:
I don't pay a penny for open-source software; what, exactly, does
paying $$$ for proprietary software earn one? The privilege of calling
a helpdesk while being charged an additional rate of $$ per hour? Hah!

I don't really understand this suspicious attitude towards the GPL or
open-source software; that attitude, in my opinion, is what should be
directed at proprietary software.

<getting off soapbox with a huge sighhhhh>



This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: Peer Review Process/Best Practices?
Next by Author: RE: Adobe TC Suite
Previous by Thread: Re: Word to the wise
Next by Thread: Word to Frame Tool?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads