Re: [Fwd: Re: Bug#304316: section non-free/doc]
Michael K. Edwards wrote:
On 4/20/05, Matthew Garrett <email@example.com> wrote:
Michael K. Edwards <firstname.lastname@example.org> wrote:
For the record, so long as implementations of software freedom are
copyright-based, documents from which fragments cannot legally be cut
and pasted into the software they accompany do not belong in main.
This applies most emphatically to the GFDL and to RFCs, inconvenient
as that may be.
When did license incompatibility become a freeness issue?
When we're talking about something where the program and the
documentation arguably form a single work. Frankly, I think the case
for license incompatibility between a program and its documentation
being a legal problem (once they are modified and distributed by a
third party) is much stronger than the case against linking a GPL
library into a GPL-incompatible application.
Legally, I can't modify a glibc API and then paste my revisions into
the glibc documentation, because my changes truly are a work derived
from GPL material and can't be amalgamated with GFDL material. I
think this is an unacceptable situation, and that (in addition to
other problems with the GFDL) Debian shouldn't distribute in main
documents that can't legally be kept up to date with non-trivial
modifications to the programs they describe.
So anyone publishing a (proprietary) book about a free software may be
subject to a copyrigt infrigment? There are a lot of proprietary books
about free software (look for emacs in http://www;amazon.com).
Nobody has never complains and sincerely I doubt a court would declare
these books illegal.