all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eliz@gnu.org, 59609@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual
Date: Sun, 10 Sep 2023 20:40:17 -0400	[thread overview]
Message-ID: <E1qfUyP-0006Tl-I2@fencepost.gnu.org> (raw)
In-Reply-To: <jwv8r9gbfzv.fsf-monnier+emacs@gnu.org> (bug-gnu-emacs@gnu.org)

[[[ 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. ]]]

  > > Only because we decide not to do that, or are lazy, or whatever.
  > > Basically, it's our decision for GNU ELPA, and not so for NonGNU ELPA.

  > We have just as much control in one as in the other, in practice.

Does "have" here stand for "exercise"?  I think so.

With GNU ELPA packages, in principle we can make the changes we wish.
However, for several reasons, we normally let the package developers
alone, except when there is an important reason to do otherwise, which
is rare.  When it makes sense for them to work independently, it is
better that they do.

It's the same for packages in core Emacs, those that have specific
developers.  We likewise let them do their work on their own as much
as possible.

However, it's different for NonGNU ELPA packages.  We would not want
to do more on them than fix small instances of bit-rot or simple
failures to fit into Emacs, even if the package becomes unmaintained.
Beyond that is not our responsibility.

If in practice we get involved in most of the packages that are part
of Emacs so rarely that it doesn't look very different from NonGNU
ELPA, that means we are doing well -- but that doesn't change the fact
that those categories are different in principle.


-- 
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)







  reply	other threads:[~2023-09-11  0:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 13:44 bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual Stefan Kangas
2022-11-26 14:20 ` Eli Zaretskii
2023-09-08 11:25   ` Stefan Kangas
2023-09-08 11:56     ` Eli Zaretskii
2023-09-08 15:04       ` Stefan Kangas
2023-09-11  0:40         ` Richard Stallman
2023-09-11  2:49           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:47       ` Drew Adams
2023-09-08 16:43       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 18:29         ` Eli Zaretskii
2023-09-08 18:47           ` Michael Albinus
2023-09-08 20:10           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11  0:40             ` Richard Stallman [this message]
2022-11-27 22:54 ` Richard Stallman
2022-11-30 23:54 ` Richard Stallman
2022-12-01  3:49   ` Stefan Kangas
2022-12-03 23:40     ` Richard Stallman
2022-12-04  0:00       ` Stefan Kangas
2022-12-14 22:20         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1qfUyP-0006Tl-I2@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=59609@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.