From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: DISTRIB file vs. Emacs manuals and GFDL
Date: Tue, 21 Dec 2004 15:24:59 +0100 [thread overview]
Message-ID: <x5d5x3ohj8.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3y8frkbbb.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Tue, 21 Dec 2004 14:52:56 +0100")
storm@cua.dk (Kim F. Storm) writes:
> The file etc/DISTRIB explains that emacs software is licensed under GPL
> and refers to etc/COPYING.
>
> Now that an emacs distribution includes the manual and lisp reference,
> I think DISTRIB should mention that the documentation is covered by a
> different license, and give a pointer to that license?
>From the GPL
2b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
Since "to be licenced as a whole [...] under the terms of this
licence" would be binding to every redistributor, we can't declare
manual and Lisp reference to be part of Emacs. The linkage via things
like C-h F into the manual is not to be considered creation of a
derived work.
We have to make clear that the Emacs manual, the Lisp manual, the
Elisp tutorial and everything else covered by the GFDL are not to be
considered part of Emacs as a whole, or people won't be able to
redistribute Emacs at all due to GPL 2b.
The Emacs tutorial currently ends with:
This version of the tutorial, like GNU Emacs, is copyrighted, and
comes with permission to distribute copies on certain conditions:
Copyright (c) 1985, 1996, 1998, 2001, 2002 Free Software Foundation
Permission is granted to anyone to make or distribute verbatim copies
of this document as received, in any medium, provided that the
copyright notice and permission notice are preserved,
and that the distributor grants the recipient permission
for further redistribution as permitted by this notice.
Permission is granted to distribute modified versions
of this document, or of portions of it,
under the above conditions, provided also that they
carry prominent notices stating who last altered them.
As far as I can see, it might be GPL-incompatible as well, since "the
distributor grants the recipient permission for further redistribution
as permitted by this notice" appears to me to be in conflict with
distributing under the conditions of the GPL "as a whole".
So it would probably be necessary to mention that the tutorials are
not considered part of Emacs as a whole, too.
Anybody have a better idea? I remain of the opinion that we have some
sort of a problem here.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-12-21 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 13:52 DISTRIB file vs. Emacs manuals and GFDL Kim F. Storm
2004-12-21 14:24 ` David Kastrup [this message]
2004-12-22 0:17 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5d5x3ohj8.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).