From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Pittman <slippycheeze@google.com>,
emacs-devel@gnu.org, licensing@fsf.org
Subject: Re: Licensing for source code contained in Emacs manuals
Date: Mon, 12 Nov 2018 12:01:24 -0800 [thread overview]
Message-ID: <ff1dba3c-3d07-912e-3c62-c013f8f86578@cs.ucla.edu> (raw)
In-Reply-To: <CAC45yQs5C9=Zonsu03on=9C5ne2vmgRtEu33WV1=ascz_WQKwg@mail.gmail.com>
Daniel Pittman wrote:
> Would it be appropriate to extend the documentation to explicitly permit
> reuse of the sample code in the Emacs flymake manual, or all Emacs manuals,
> under the same license as Emacs itself? That is, sample code could be used
> under the GFDL*or* the GPLv3 (at this time).
I'm sure that could be fine. Alternatively, and without needing any special
rules about this, the distribution could contain a separate copy of the code in
question in standard source-code form, licensed under the GPL. The documentation
could explain that the code itself is also available outside the documentation
and that it is GPLed there. As a user, I'd prefer that to cutting and pasting
out of the documentation.
next prev parent reply other threads:[~2018-11-12 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 18:24 Licensing for source code contained in Emacs manuals Daniel Pittman
2018-11-12 20:01 ` Paul Eggert [this message]
2018-11-12 21:35 ` Daniel Pittman
2018-11-13 18:31 ` Glenn Morris
2018-11-14 23:13 ` Richard Stallman
2018-11-19 14:18 ` Daniel Pittman
2018-11-20 0:49 ` Richard Stallman
2018-12-24 2:26 ` Richard Stallman
2019-01-07 21:06 ` Daniel Pittman
2019-01-08 1:06 ` Paul Eggert
2019-01-08 18:57 ` Richard Stallman
2019-06-30 5:05 ` FIXME: When the reader is called in the minibuffer Spenser Truex
2019-06-30 13:50 ` Stefan Monnier
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=ff1dba3c-3d07-912e-3c62-c013f8f86578@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=licensing@fsf.org \
--cc=slippycheeze@google.com \
/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.