[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Gnus Manual License



Hubert Chan <hubert@uhoreg.ca> writes:

>>  * 3. All advertising materials mentioning features or use of this
>>  * software must display the following acknowledgment:
>
> This does not place any conditions on the distribution or modification
> of the work itself.  It only places conditions on auxiliary material.

No, the license demands that the clause 3 part of the license is
preserved together with the work itself:

 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.

So you can't redistribute OpenSSL without including

>>  * "This product includes software developed by the OpenSSL Project
>>  * for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

both in the work itself (in the license), and on any auxiliary
material (advertising material).

That seems similar to cover texts to me: you can't redistribute a GFDL
manual with cover texts without including the cover text both in the
license text and on the cover page of the book.

I would count the book cover under auxiliary material -- the cover is
typically not part of the texinfo manual.

FWIW, to me, the GFDL requirement seems less problematic than the
OpenSSL requirement: the GFDL cover text requirement only applies to
the cover of books.  It doesn't say anything about other advertising
material that is not derived from the work.

>> I believe the license clause is annoying, but, as for OpenSSL, does
>> not make it impossible to use the licensed material freely, and in
>> particular, should not prevent including it in main.
>
> Yes, I agree that it is annoying.  I think that RMS also thought it was
> annoying, which makes me wonder why he doesn't mind invariant sections
> in documentation.  I'm sure he's answered that question before, so if
> someone has a pointer to where I can look that up, I'd be interested.

There is http://www.gnu.org/philosophy/free-doc.html although it
doesn't discuss license details.

/Simon



Reply to: