From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: akib@disroot.org, arvidkrein@zedat.fu-berlin.de,
guix-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: guix emacs package MELPA/ELPA
Date: Sun, 04 Dec 2022 18:14:28 -0500 [thread overview]
Message-ID: <E1p1yBo-0000Ez-Je@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkm=U5xq+tZL10dtRCOL_LPQQx+cwkTZZm9iuDzMpqKhjSw@mail.gmail.com> (message from Stefan Kangas on Sat, 3 Dec 2022 08:57:07 -0800)
[[[ 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 packages in GNU ELPA really are part of GNU Emacs. We get
copyright assignments for them, and we work on them just as if they
were in the Emacs core. Indeed, we can move them between GNU ELPA and
the core when that is useful.
The packages in NonGNU ELPA are really not part of GNU Emacs, and you
can see that in every aspect of how we treat them. We do not maintain
them; we do not host their development; we don't deal with their
copyrights. They can't go into Emacs core.
All we do with them is inform users about the possibility of using
them.
--
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:[~2022-12-04 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 23:26 guix emacs package MELPA/ELPA Arvid Krein
2022-12-03 14:48 ` Akib Azmain Turja
2022-12-03 16:57 ` Stefan Kangas
2022-12-03 17:56 ` Eli Zaretskii
2022-12-04 23:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1p1yBo-0000Ez-Je@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=akib@disroot.org \
--cc=arvidkrein@zedat.fu-berlin.de \
--cc=emacs-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/guix.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.