From: Glenn Morris <rgm@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: Sebastien Delafond <sdelafond@gmx.net>, emacs-devel@gnu.org
Subject: Re: Dual licensing of Org manual?
Date: Thu, 13 Dec 2012 18:05:38 -0500 [thread overview]
Message-ID: <4z1uetzh6l.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877golv9st.fsf@bzg.ath.cx> (Bastien's message of "Thu, 13 Dec 2012 23:58:42 +0100")
It's possible that the GNU position may have softened wrt invariant
sections and cover texts. GFDL with no invariant sections and no cover
texts is acceptable for Debian "free" IIUC.
http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Documentation.html
If your manual is not published by the FSF, and under 400 pages, you
can omit both cover texts.
The Org manual is under 400 pages, but at ~ 250 pages it is pretty
substantial. I do not know if it is published.
Anyway, you need rms to answer this. If he doesn't respond anyway within
a week or so then ask him directly about the invariant sections and
cover texts if you want to.
next prev parent reply other threads:[~2012-12-13 23:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:31 Dual licensing of Org manual? Bastien
2012-12-13 22:51 ` Glenn Morris
2012-12-13 22:58 ` Bastien
2012-12-13 23:05 ` Glenn Morris [this message]
2012-12-13 23:13 ` Bastien
2012-12-14 9:02 ` Sébastien Delafond
2012-12-14 11:04 ` Bastien
2012-12-14 16:42 ` Stephen J. Turnbull
2012-12-14 17:45 ` Bastien
2012-12-15 3:28 ` Richard Stallman
2012-12-15 5:52 ` Bastien
2012-12-15 19:46 ` Richard Stallman
2012-12-16 23:18 ` Bastien
2012-12-19 5:27 ` Bill Wohler
2012-12-20 2:25 ` Richard Stallman
2012-12-20 8:11 ` Bastien
2012-12-20 15:29 ` Bill Wohler
2012-12-20 15:40 ` Bastien
2012-12-21 17:43 ` Richard Stallman
2012-12-21 2:08 ` Richard Stallman
2012-12-14 15:23 ` Richard Stallman
2012-12-14 15:35 ` Bastien
2012-12-14 17:22 ` Glenn Morris
2012-12-15 5:43 ` Bastien
2012-12-15 5:46 ` Bastien
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=4z1uetzh6l.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sdelafond@gmx.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 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.