From: "Richard M. Stallman" <rms@gnu.org>
Cc: eliz@gnu.org, mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: MH-E manual update
Date: Sat, 10 Dec 2005 11:18:55 -0500 [thread overview]
Message-ID: <E1El7R1-0006jD-11@fencepost.gnu.org> (raw)
In-Reply-To: <21266.1134174346@olgas.newt.com> (message from Bill Wohler on Fri, 09 Dec 2005 16:25:46 -0800)
The biggest is that the two licenses are incompatible which is a problem
because the docstrings in the code are cut and pasted into the manual
and vice-versa.
That is not a legal problem, since the FSF is the copyright holder for
both. However, the use of doc strings in the manual without extensive
rewriting would tend to make the manual less than ideal. Doc strings
and a manual are rather different, and the text that is good for one
is not very good for the other.
Another solution was to rewrite the GFDL so that it was compatible with
the GPL and acceptable by Debian, but I don't think that has been done
either.
This idea sounds nice, but it makes no sense. The GFDL can't be made
compatible with the GPL except by eliminating it. I hope no one ever
said that we would do this.
Failing those two solutions, one suggestion that was proposed by
Dave Turner <licensing@fsf.org> was to use a dual-license scheme and
license the manual under both the GPL and GFDL.
What we want to do is release it solely under the GFDL.
That is our policy for licensing GNU manuals.
Debian should interpret its criteria in a more sensible way
and use it under the GFDL.
next prev parent reply other threads:[~2005-12-10 16:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 0:27 MH-E manual update Bill Wohler
2005-12-09 11:58 ` Eli Zaretskii
2005-12-09 14:40 ` Bill Wohler
2005-12-09 18:50 ` Eli Zaretskii
2005-12-09 21:15 ` Richard M. Stallman
2005-12-10 0:25 ` Bill Wohler
2005-12-10 16:18 ` Richard M. Stallman [this message]
2006-03-07 1:29 ` Bill Wohler
2006-03-11 14:30 ` Eli Zaretskii
2006-03-11 20:08 ` Bill Wohler
2006-03-11 21:35 ` Luc Teirlinck
2006-03-11 22:27 ` Bill Wohler
2006-03-11 23:08 ` Luc Teirlinck
2006-03-11 23:34 ` Bill Wohler
2006-03-11 23:24 ` Luc Teirlinck
2006-03-11 23:40 ` Bill Wohler
2006-03-11 23:39 ` Luc Teirlinck
2006-03-11 23:49 ` Bill Wohler
2006-03-12 2:39 ` Luc Teirlinck
2006-03-12 3:56 ` Bill Wohler
2006-03-12 0:39 ` Luc Teirlinck
2006-03-11 22:10 ` Eli Zaretskii
2006-03-11 23:32 ` Bill Wohler
2006-03-12 11:59 ` Robert J. Chassell
2006-03-13 12:55 ` Richard Stallman
2006-03-13 15:20 ` Robert J. Chassell
2006-03-13 16:29 ` Bill Wohler
2006-03-14 4:26 ` Eli Zaretskii
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=E1El7R1-0006jD-11@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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).