From: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org, xemacs-beta@xemacs.org
Subject: Re: Permission to use portions of the recent GNU Emacs Manual
Date: Sat, 11 Dec 2004 10:27:39 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1041211091557.275A-100000@acm.acm> (raw)
In-Reply-To: <E1CctyU-0007l0-D7@fencepost.gnu.org>
Hi, Richard and Ben,
On Fri, 10 Dec 2004, Richard Stallman wrote:
> The GNU Emacs user's manual has changed its license to the GFDL.
> The XEmacs manual has a different license -- the GPL. Because of
> contributions from various parties, we cannot easily change our
> license,
>Too bad. I won't relicense such a large amount of material all
>together.
There is irony in that sentence.
>If you show me specific parts you would like to use, I will consider
>relicensing them.
I'm speaking as somebody who's put a significant amount of time into
amending the Emacs manual (e.g. programs.texi). I did so under the
impression that what I was amending was free, in the same sense that
the Emacs Lisp that I contribute is free.
Some time later, my attention was drawn to the details of the GFDL.
Anybody wishing to use the contents of a GFD is obliged to copy the cover
sheets of the original. This restriction seems analogous to one that,
say, allows functions to be used for decoding a compressed graphic but
not for encoding one.
What is the purpose of the GFDL? I quote from the licence: "The purpose
of this License is to make a manual .... "free" in the sense of
freedom: to assure everyone the effective freedom to copy and
redistribute it, with or without modifying it, either commercially or
noncommercially." Since the XEmacs team's freedom here is ineffective,
the GFDL is, on its own terms, broken.
I do not understand why the GFDL exists at all. It seems to me that the
GPL is as adequate for manuals as it is for code. I also don't
understand why the Emacs Manual's licence had to be changed - a prime
effect of this change was to annul people's freedom to combine old bits
of the manual with new bits.
My feeling is that this is just not the way things should be in the free
software community. Put bluntly, having made contributions to the Emacs
manual, I feel duped. Yes, the GFDL conforms to the terms of the
assignment papers I signed, but I don't think I should have to wave the
small print past a lawyer before signing this sort of thing.
Do I really want to make any more contributions to the Emacs manual?
That's not just a rhetorical question.
Richard, the GFDL is broken. Please get it fixed, in a way which will
restore the XEmacs team's freedom to copy and modify the Emacs manual.
--
Alan Mackenzie (Munich, Germany)
next prev parent reply other threads:[~2004-12-11 10:27 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 22:28 Permission to use portions of the recent GNU Emacs Manual Ben Wing
2004-12-10 23:14 ` Richard Stallman
2004-12-11 0:59 ` Ben Wing
2004-12-11 1:06 ` Miles Bader
2004-12-11 10:27 ` Alan Mackenzie [this message]
2004-12-11 18:19 ` Eli Zaretskii
2004-12-11 20:43 ` David Kastrup
2004-12-11 19:02 ` Stefan Monnier
2004-12-12 0:26 ` Karl Fogel
2004-12-12 8:57 ` David Kastrup
2004-12-12 16:56 ` Brian Palmer
2004-12-12 13:31 ` Matthew Mundell
2004-12-12 13:40 ` David Kastrup
2004-12-12 2:03 ` Robert J. Chassell
2004-12-12 4:59 ` Karl Fogel
[not found] ` <m1CdWGG-0004R2C@rattlesnake.com>
2004-12-12 17:43 ` David Kastrup
2004-12-12 18:39 ` Florian Weimer
2004-12-12 19:24 ` David Kastrup
2004-12-12 19:49 ` Florian Weimer
2004-12-12 19:43 ` Robert J. Chassell
2004-12-12 19:59 ` David Kastrup
2004-12-12 20:46 ` Robert J. Chassell
2004-12-12 21:00 ` Andy Piper
2004-12-13 1:59 ` Robert J. Chassell
2004-12-13 2:23 ` David Kastrup
2004-12-13 12:34 ` Thien-Thi Nguyen
2004-12-13 16:53 ` Robert J. Chassell
2004-12-15 14:23 ` Stephen J. Turnbull
2004-12-15 19:14 ` Robert J. Chassell
2004-12-15 20:19 ` David Kastrup
2004-12-15 23:32 ` Robert J. Chassell
2004-12-17 5:36 ` Stephen J. Turnbull
2004-12-15 23:20 ` Richard Stallman
2004-12-16 10:58 ` David Kastrup
2004-12-16 12:18 ` Eli Zaretskii
2004-12-16 12:29 ` Kim F. Storm
2004-12-17 0:53 ` Richard Stallman
2004-12-18 10:20 ` Ben Wing
2004-12-18 23:32 ` Miles Bader
2004-12-19 6:31 ` Ben Wing
2004-12-19 6:32 ` Ben Wing
2004-12-19 13:54 ` Robert J. Chassell
2004-12-19 15:40 ` David Kastrup
2004-12-19 16:10 ` Paul Pogonyshev
2004-12-19 21:32 ` David Kastrup
2004-12-19 23:48 ` Paul Pogonyshev
2004-12-20 8:07 ` David Kastrup
2004-12-20 14:05 ` Robert J. Chassell
2004-12-20 0:19 ` Ben Wing
2004-12-20 7:20 ` David Kastrup
2004-12-20 10:58 ` Stephen J. Turnbull
2004-12-20 10:56 ` Richard Stallman
2004-12-20 12:47 ` David Kastrup
2004-12-17 1:32 ` Stephen J. Turnbull
2004-12-12 4:39 ` Richard Stallman
2004-12-12 6:16 ` Stefan Monnier
2004-12-12 21:28 ` Eli Zaretskii
2004-12-12 21:43 ` David Kastrup
2004-12-13 2:22 ` Robert J. Chassell
2004-12-13 6:48 ` Brian Palmer
2004-12-13 10:05 ` David Kastrup
2004-12-13 17:44 ` Bruce Stephens
2004-12-14 13:09 ` Stephen J. Turnbull
2004-12-14 2:56 ` Karl Fogel
2004-12-14 14:16 ` Robert J. Chassell
2004-12-13 4:23 ` Dhruva
2004-12-13 19:51 ` Richard Stallman
2004-12-13 20:03 ` David Kastrup
2004-12-14 10:03 ` Per Abrahamsen
2004-12-14 10:14 ` David Kastrup
2004-12-14 14:09 ` Robert J. Chassell
2004-12-14 14:25 ` David Kastrup
2004-12-14 20:19 ` Robert J. Chassell
2004-12-14 22:09 ` David Kastrup
2004-12-15 0:12 ` Robert J. Chassell
2004-12-15 8:03 ` Per Abrahamsen
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=Pine.LNX.3.96.1041211091557.275A-100000@acm.acm \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=xemacs-beta@xemacs.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).