From: Richard Stallman <rms@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: is GPL2 or later enough for having a package in ELPA?
Date: Sun, 09 Jul 2023 21:58:51 -0400 [thread overview]
Message-ID: <E1qIgAt-0005Mu-Ny@fencepost.gnu.org> (raw)
In-Reply-To: <87y1jqtn8g.fsf@mat.ucm.es> (message from Uwe Brauer on Sat, 08 Jul 2023 17:51:59 +0200)
[[[ 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. ]]]
> Is it ok if all lisp files are under GLP 2 or later?
That question has multiple possible meanings. But each meaning
results in the conclusion that we could do what we need to do.
1, If we get the programs listing GNU GPL 2 or later as the license,
we can change them to say GPL 3 or later, which is simply dropping the
GPL 2 option. Anyone can do that.
2. If we get copyright assignments for that code, which we would want
in order to put them in GNU ELPA, we can relicense them. We would
relicense them to GPL 3 or later.
--
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)
next prev parent reply other threads:[~2023-07-10 1:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 15:51 is GPL2 or later enough for having a package in ELPA? Uwe Brauer
2023-07-09 3:26 ` Yuchen Pei
2023-07-10 1:58 ` Richard Stallman [this message]
2023-07-10 7:49 ` Uwe Brauer
2023-07-10 9:27 ` Dr. Arne Babenhauserheide
2023-07-10 12:09 ` Uwe Brauer
2023-07-10 18:48 ` Dr. Arne Babenhauserheide
2023-07-12 3:04 ` Richard Stallman
2023-07-12 15:08 ` Uwe Brauer
2023-07-17 2:20 ` Richard Stallman
2023-07-17 6:07 ` Uwe Brauer
2023-07-17 7:21 ` Dr. Arne Babenhauserheide
2023-07-19 2:19 ` 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=E1qIgAt-0005Mu-Ny@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).