From: Daniel Pittman <slippycheeze@google.com>
To: rms@gnu.org
Cc: licensing@fsf.org, emacs-devel@gnu.org
Subject: Re: Licensing for source code contained in Emacs manuals
Date: Mon, 7 Jan 2019 16:06:41 -0500 [thread overview]
Message-ID: <CAC45yQtydsv1qFjCHTDUDoipX7pZv+5SVXhegCDXaxuVrX72PQ@mail.gmail.com> (raw)
In-Reply-To: <E1gbFws-000799-8c@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
Thank you very much for the time spent on this. Shall I submit an
appropriate patch to the Emas list, to do this for that one existing
flymake example, or shall I leave that to y'all?
On Sun, Dec 23, 2018 at 9:26 PM Richard Stallman <rms@gnu.org> wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> The solution I've come up with for code examples that are useful to
> copy into programs is to put a copy of the code example in a code
> source file, which would be released under a free license for software.
>
> For a large and specialized example, put it under the GPL.
> For a smaller example (but long enough to matter for copyright),
> you can use CC0.
>
>
> --
> Dr Richard Stallman
> President, Free Software Foundation (https://gnu.org, https://fsf.org)
> Internet Hall-of-Famer (https://internethalloffame.org)
>
>
>
[-- Attachment #2: Type: text/html, Size: 1543 bytes --]
next prev parent reply other threads:[~2019-01-07 21:06 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
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 [this message]
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
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=CAC45yQtydsv1qFjCHTDUDoipX7pZv+5SVXhegCDXaxuVrX72PQ@mail.gmail.com \
--to=slippycheeze@google.com \
--cc=emacs-devel@gnu.org \
--cc=licensing@fsf.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 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).