From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Documentation on the command-line?
Date: Wed, 2 Jul 2014 20:46:32 -0600 [thread overview]
Message-ID: <20140703024632.GA26627@hysteria.proulx.com> (raw)
In-Reply-To: <87y4wb2n7u.fsf@robertthorpeconsulting.com>
Robert Thorpe wrote:
> Emanuel Berg writes:
> > Yeah, what is the reason?
>
> Most free-software/open-source licenses require someone passing on the
> code to pass on the license. The GNU Free Documentation License als
> requires them to include a little essay by RMS. The Debian maintainers
> objected to that and labeled GFDL a "non-free" license. There was a
> kerfuffle about it a few years ago.
Not quite. The main problem was Invariant Sections. That was
specifically the problem with the Emacs documentation.
Rather than summarize let me refer you to the official statement of
why the GFDL is considered to be a non-free license. Then I will
avoid errors in paraphrasing.
http://www.debian.org/vote/2006/vote_001
Bob
next prev parent reply other threads:[~2014-07-03 2:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4692.1404265508.1147.help-gnu-emacs@gnu.org>
2014-07-02 8:05 ` Documentation on the command-line? Emanuel Berg
2014-07-03 2:24 ` Robert Thorpe
2014-07-03 2:46 ` Bob Proulx [this message]
[not found] <87mwcshia0.fsf@robertthorpeconsulting.com>
2014-07-01 22:13 ` Emanuel Berg
2014-07-02 1:44 ` Robert Thorpe
[not found] <mailman.4651.1404228752.1147.help-gnu-emacs@gnu.org>
2014-07-01 16:36 ` Emanuel Berg
2014-07-01 18:53 ` Sharon Kimble
[not found] ` <mailman.4672.1404240819.1147.help-gnu-emacs@gnu.org>
2014-07-01 20:58 ` Emanuel Berg
2014-07-01 15:32 Sharon Kimble
2014-07-01 16:46 ` Eric Abrahamsen
2014-07-01 18:40 ` Sharon Kimble
[not found] ` <mailman.4665.1404233238.1147.help-gnu-emacs@gnu.org>
2014-07-01 21:12 ` Emanuel Berg
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=20140703024632.GA26627@hysteria.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@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.