From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, xemacs-beta@xemacs.org, emacs-devel@gnu.org,
bob@rattlesnake.com, stephen@xemacs.org, andy@xemacs.org
Subject: Re: Permission to use portions of the recent GNU Emacs Manual
Date: Sun, 19 Dec 2004 16:40:18 +0100 [thread overview]
Message-ID: <x5oegq1el9.fsf@lola.goethe.zz> (raw)
In-Reply-To: <014501c4e4eb$3af838d0$0300a8c0@neeeeeee2> (Ben Wing's message of "Sat, 18 Dec 2004 03:20:42 -0700")
"Ben Wing" <ben@666.com> writes:
>> The people who consider these issues for Debian have arrived
>> at an extremely strict and mechanical way of interpreting
>> their criteria, which I think is very mistaken.
>>
>> The FSF made this decision years ago, and it is not an open
>> question now. Could you please move the discussion to
>> gnu-misc-discuss@gnu.org?
>
> This is COMPLETELY relevant to this list, because the bottom issue is
>
> [a] XEmacs forked and kept the identical license
> [b] 3 or 4 years ago -- i.e. 9-10 years after the XEmacs fork -- you changed
> the license in a way that it cross-incompatible.
> [c] I made a simple request -- will you cross-license the manual for us?
> [d] you said no.
>
> This is totally relevant to GNU Emacs.
Uh, no. It is relevant to XEmacs. Since you more or less stated that
XEmacs developers are not to be bothered with issues like licences, it
is somewhat unclear what factual problem you would have with changing
the XEmacs manual licence to the GFDL. That you don't feel like it is
not really sufficient.
To the extent that your problems are related to actual practical
considerations instead of "we liked the older licence better and did
not bother asking contributors whether they'd go with changes, since
they better be fine anyhow", they might also be relevant to Emacs.
It is my personal opinion that by far the most prominent distribution
channel for the Emacs manual is as part of Emacs, and so it should
also be available under the GPL (which would probably not help your
case, incidentally). I'd be somewhat less inclined to state the same
thing for the Elisp tutorial: that is more like being a separate piece
of software, not as tightly integrated as either the Elisp manual and
the Emacs manual are with Emacs.
> Richard, please reconsider. You have a reputation of antipathy
> towards XEmacs. If you're at all interested in mending fences a
> little, this would be a very easy step -- simply declare that we are
> allowed to use the code under our license (which was your license up
> through 2000 or so). Otherwise you give the impression of actively
> hindering the XEmacs project.
The question to solve for the licences of Emacs are what benefits
Emacs first, and free software in general second.
Licences like the GPL and the GFDL retain their force by having
relevant software with suitable copyright owners willing to defend
them.
The FSF maintains a large and significant body of free software as the
sole copyright holder, and it is paying a high price for it: the price
is that the FSF itself is unable to reap the benefits of the GPL. It
can't reincorporate third party contributions without explicit
assignment.
The GPL implies the freedom to fork. XEmacs developers have decided
to make use of that freedom, and have by the same token decided that
they would make use of that freedom also by relaxing their
contribution criteria and maintaining diversified copyrights, partly
not even tracking them. Which you were free to do. A different
significant fork from FSF-maintained software was egcs. The egcs
project, in contrast, decided that they would not simplify matters in
a similar way: copyright assignments to the FSF were diligently
maintained. As a result, this fork was able to get merged with the
FSF's own variant of GCC again. Of course, egcs developers already
had seen the consequences of the Emacs/XEmacs fork, so it was easier
for them to decide differently.
Now with regard to the discussion on this list, it has not made
apparent by you
a) why the GFDL is a bad choice for Emacs manuals (I myself have
offered some opinions about that, but those mostly hold equally for
the previous licence).
b) why it would be technically impossible for you to change the XEmacs
manual licence to the GFDL: it does not seem like you have handed out
any written assurances that the licence is never going to change.
My personal guess would be "we don't like the licence". Neither do I
for this purpose and have explained why. But my dislike would be for
the old version of the licence, too.
It is pointless to say "well, everybody else but us should be affected
by the GFDL, so please give us an exception". If there are arguments
good enough for you, they should also be good enough for everybody
else. So please explain in detail what concrete problems you would
have with a licence change that other users and developers of free
software could reasonably also be expected to have.
As long as this is not particularly connected with Emacs itself, but
rather a general dislike of the GFDL, I have to agree with Richard
that this group does not seem the right place for it.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-12-19 15:40 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
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 [this message]
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=x5oegq1el9.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=andy@xemacs.org \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stephen@xemacs.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).