From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: naesten@gmail.com, 24520@debbugs.gnu.org
Subject: bug#24520: 25.1.50; calccard.tex has somewhat unclear licensing
Date: Sun, 23 Oct 2016 20:26:08 -0400 [thread overview]
Message-ID: <E1byT5c-0002t7-Bd@fencepost.gnu.org> (raw)
In-Reply-To: <83h983nr67.fsf@gnu.org> (message from Eli Zaretskii on Sun, 23 Oct 2016 16:14:24 +0300)
[[[ 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. ]]]
> > My own take is that the "this is part of Emacs" GPL blurb in the tex source
> > should be removed, for clarity.
I agree it should not say the words "this is part of GNU Emacs".
> > > Perhaps what we need is (1) an additional permission saying that
> > > reference cards printed, or formatted for printing, may be distributed
> > > with the notice "Released under the terms of the GNU General Public
> > > License version 3 or later" and a copyright notice, without the usual
> > > GPL notice and without a copy of the GPL itself.
I think this is what we should do, in the refcard source. How about
this text?
As a special additional permission, you may distribute reference cards
printed, or formatted for printing, with the notice "Released under
the terms of the GNU General Public License version 3 or later"
instead of the usual distributed-under-the-GNU-GPL notice, and without
a copy of the GPL itself.
Then change the notice used in the formated file
to say that.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
next prev parent reply other threads:[~2016-10-24 0:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 18:58 bug#24520: 25.1.50; calccard.tex has somewhat unclear licensing naesten
2016-10-10 10:38 ` Eli Zaretskii
2016-10-15 14:07 ` Eli Zaretskii
2016-10-16 10:40 ` Richard Stallman
2016-10-16 11:28 ` Eli Zaretskii
2016-10-17 19:51 ` Richard Stallman
2016-10-17 0:43 ` Richard Stallman
2016-10-17 1:43 ` Glenn Morris
2016-10-17 19:54 ` Richard Stallman
2016-10-18 16:10 ` Glenn Morris
2016-10-18 17:26 ` Eli Zaretskii
2016-10-23 13:14 ` Eli Zaretskii
2016-10-24 0:26 ` Richard Stallman [this message]
2016-10-29 10:06 ` Eli Zaretskii
2016-10-29 16:38 ` Richard Stallman
2016-10-29 21:54 ` Eli Zaretskii
2016-10-31 19:18 ` Richard Stallman
2016-11-02 16:37 ` Eli Zaretskii
2016-11-03 1:24 ` Richard Stallman
2016-11-03 18:10 ` Eli Zaretskii
2016-11-12 7:52 ` Eli Zaretskii
2016-11-12 22:28 ` Richard Stallman
2016-11-13 16:23 ` Eli Zaretskii
2016-11-13 23:56 ` Glenn Morris
2016-11-14 15:41 ` Eli Zaretskii
2016-11-15 0:29 ` Richard Stallman
2016-11-15 17:02 ` Eli Zaretskii
2016-11-16 21:04 ` Richard Stallman
2016-11-18 7:28 ` Glenn Morris
2016-11-18 8:32 ` Eli Zaretskii
2016-11-15 0:25 ` Richard Stallman
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=E1byT5c-0002t7-Bd@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=24520@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=naesten@gmail.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 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).