From: David Kastrup <dak@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: dominik@uva.nl, Richard M Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Copyright question
Date: Sat, 14 Jun 2008 23:36:09 +0200 [thread overview]
Message-ID: <85bq23og1i.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20080614120324.GA4589@muc.de> (Alan Mackenzie's message of "Sat, 14 Jun 2008 12:03:25 +0000")
Alan Mackenzie <acm@muc.de> writes:
> Nearly everybody agrees there are problems with the current GFDL.
This list is not for discussing the GFDL. Like other projects, it is
inherently a slowly moving target that gets improved over time.
Whether one likes the GFDL or not or whether Debian likes it or not:
that is not really a topic here. My beef is not with the GFDL per se,
but rather that the _GPL_ demands to distribute a work as a whole under
the GPL. And the increasing integration of the GFDL manuals (which is a
convenient and useful thing) makes the definition of "whole work"
increasingly arbitrary in a manner where we
a) don't want to set a precedent for people integrating incompatibly
licensed material with GPL software based on a weird "whole work"
interpretation of Emacs
b) don't want to turn the integration of documentation into a privileged
operation not compatible with the "public" in "General Public License".
The current distribution of Emacs with its incompatible GFDL/GPL
combination strains the credulity of the GPL. And the more we integrate
info manuals into the Emacs work and reference flow, the worse this
gets. I certainly hope that this will get sorted out in the long run.
A dual licensing of the technical manuals would certainly help.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2008-06-14 21:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 14:43 Copyright question Carsten Dominik
2008-06-12 19:30 ` David Hansen
2008-06-12 19:33 ` Stefan Monnier
2008-06-13 8:19 ` Carsten Dominik
2008-06-13 9:59 ` David Kastrup
2008-06-13 22:48 ` Richard M Stallman
2008-06-14 13:15 ` Carsten Dominik
2008-06-14 20:11 ` Don Armstrong
2008-06-15 17:55 ` Richard M Stallman
2008-06-12 19:40 ` Glenn Morris
2008-06-12 20:47 ` Juanma Barranquero
2008-06-12 20:51 ` İsmail Dönmez
2008-06-12 23:31 ` Glenn Morris
2008-06-13 8:55 ` Andreas Röhler
2008-06-13 9:44 ` Alan Mackenzie
2008-06-13 9:36 ` Miles Bader
2008-06-13 13:35 ` Stefan Monnier
2008-06-13 10:35 ` Andreas Röhler
2008-06-13 11:00 ` David Kastrup
2008-06-12 21:08 ` David Kastrup
2008-06-12 21:31 ` Don Armstrong
2008-06-12 23:03 ` Bastien
2008-06-13 3:13 ` Alfred M. Szmidt
2008-06-13 4:06 ` Richard M Stallman
2008-06-13 7:58 ` Stephen J. Turnbull
2008-06-13 9:51 ` David Kastrup
2008-06-13 9:58 ` Alan Mackenzie
2008-06-13 22:48 ` Richard M Stallman
2008-06-14 12:03 ` Alan Mackenzie
2008-06-14 19:16 ` Glenn Morris
2008-06-14 19:28 ` Eli Zaretskii
2008-06-14 21:36 ` David Kastrup [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85bq23og1i.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=acm@muc.de \
--cc=dominik@uva.nl \
--cc=emacs-devel@gnu.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.