From: Richard Stallman <rms@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: emacs-devel@gnu.org
Subject: Re: Elisp licensing
Date: Sat, 23 Nov 2024 01:12:37 -0500 [thread overview]
Message-ID: <E1tEjNl-000755-3D@fencepost.gnu.org> (raw)
In-Reply-To: <87h680cmy8.fsf@librehacker.com> (message from Christopher Howard on Thu, 21 Nov 2024 12:10:39 -0900)
[[[ 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. ]]]
> I was actually concerned about how to relate
> to Elisp projects I've found that that are released under other
> licenses, in particular non-copyleft free software licenses.
the main question is whether those licenses are compatible
with GPLv3. See https://gnu.org/licenses/license-list.html
for that information.
If they are compatible with GPLv3, you can use that code
in GNU Emacs with no difficulty.
> So, Elisp programs "if they are meant for use in combination with GNU
> Emacs" legally must be released under a GPLv3+ compatible license, but
> not necessarily the GPLv3+ itself?
Yes.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2024-11-23 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 17:33 Elisp licensing Christopher Howard
2024-11-21 4:58 ` Richard Stallman
2024-11-21 21:10 ` Christopher Howard
2024-11-23 6:12 ` Richard Stallman [this message]
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=E1tEjNl-000755-3D@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=christopher@librehacker.com \
--cc=emacs-devel@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).