From: David Kastrup <dak@gnu.org>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
xemacs-beta@xemacs.org, andy@xemacs.org, emacs-devel@gnu.org
Subject: Re: Permission to use portions of the recent GNU Emacs Manual
Date: Wed, 15 Dec 2004 21:19:08 +0100 [thread overview]
Message-ID: <x5hdmnl3gj.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m1Ceebe-0004QaC@rattlesnake.com> (Robert J. Chassell's message of "Wed, 15 Dec 2004 19:14:38 +0000 (UTC)")
"Robert J. Chassell" <bob@rattlesnake.com> writes:
> In any case, please do not help the bad guys passively, when you can
> help the good guys passively (except for a fairly short time when
> you choose licenses and/or handle legal paper work that is imposed
> on you by the bad guys).
Well, but that's no reason to cheer the good guys when they are
shooting themselves and their friends in the foot.
Anyway, could we keep off the picturesque rhetoric? If there is
nothing new to say about the topic, nothing is gained by repeating the
already said things in an obfuscated way.
I guess we more or less got our differing points of view presented.
We have two different problems:
A) Emacs changed its manual licence from the old licence to the GFDL,
and XEmacs can't or does not want to easily follow suit without
contacting _their_ contributors.
B) Both the old as well as the new Emacs manual licence are
GPL-incompatible and thus present problems for integrating work on
the manual and the code for derived works that are not copyrighted
all by the same legal entity.
It would appear to me that "A" is not something that we can reasonably
deal with in isolation: if we accompany every change of the licence of
the Emacs manual with an exception for old times' sakes, there is no
point in changing the licence in the first place.
However, A is in some manner an outgrowth of problem B, and if we got
B solved in a satisfactory way, it might mean that XEmacs developers
(like everybody else) would need to adapt at most _one_ more time.
One proposal of mine was dual GFDL/GPL licencing which still has the
disadvantage that third party code can be pulled into the manual by
others only while sacrificing the GFDL licence, so we probably will
still have the FSF as the primary responsible (non-public) source for
GFDL manuals. It has the advantage that it can be accomplished rather
fast, and the disadvantage that it does not seem to solve any of the
more _urgent_ problems right now (certainly not the problem of the
XEmacs developers, except that they might be less uncomfortable with
the necessary relicensing then).
On the long run, I'd hope that the next version of the GPL would
become suitable to cover the generated of printed manuals in a
satisfactory way without the need for a separate licence. However,
this will take quite long, and it does not appear to me that Richard
thinks it feasible at all.
Other choices are to let things stay as they are right now.
All of those choices don't look very appealing. And there is little
sense in dressing them up with rhetoric about how free software and
its licences are either great or completely irrelevant. Whether they
are great or irrelevant, we still have to pick them, and the cases
have more or less been made.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-12-15 20:19 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 [this message]
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=x5hdmnl3gj.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=andy@xemacs.org \
--cc=emacs-devel@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).