From: Richard Stallman <rms@gnu.org>
To: "Bozhidar Batsov" <bozhidar@batsov.dev>
Cc: emacs-devel@gnu.org
Subject: Re: What to do about unmaintained ELPA packages
Date: Wed, 01 Jun 2022 18:56:16 -0400 [thread overview]
Message-ID: <E1nwXGC-0004Pe-G5@fencepost.gnu.org> (raw)
In-Reply-To: <a06717fe-5f2d-41c3-b164-57358171a063@www.fastmail.com> (bozhidar@batsov.dev)
[[[ 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. ]]]
Ummaintained packages can occur in any collection of packages. This
may not be a disaster. But if the overall project wants to do a good
job, it should try to arrange to get them maintained again.
Our choices about how to organize this can get us better results or
worse results. Let's make a small effort to get the better results.
If you define "real problem" as disaster, well, I agree there isn't a
disaster. But there is an opportunity. Let's take it.
--
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:[~2022-06-01 22:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 21:34 What to do about unmaintained ELPA packages Philip Kaludercic
2022-05-29 21:41 ` Stefan Monnier
2022-05-29 21:54 ` Dmitry Gutov
2022-05-29 23:08 ` Tim Cross
2022-05-30 11:14 ` Akib Azmain Turja
2022-05-30 6:58 ` Philip Kaludercic
2022-05-30 13:45 ` Lars Ingebrigtsen
2022-05-30 14:46 ` João Távora
2022-05-30 22:51 ` Ergus
2022-05-30 23:04 ` João Távora
2022-05-31 16:42 ` Philip Kaludercic
2022-05-31 22:08 ` João Távora
2022-06-01 5:57 ` Bozhidar Batsov
2022-06-01 22:56 ` Richard Stallman [this message]
2022-05-30 22:53 ` Richard Stallman
2022-05-31 10:31 ` Akib Azmain Turja
2022-05-31 12:33 ` Stefan Monnier
2022-05-31 13:39 ` Akib Azmain Turja
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=E1nwXGC-0004Pe-G5@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bozhidar@batsov.dev \
--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 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.