From: Philip Kaludercic <philipk@posteo.net>
To: emacs-devel@gnu.org
Subject: What to do about unmaintained ELPA packages
Date: Sun, 29 May 2022 23:34:14 +0200 [thread overview]
Message-ID: <87k0a42fc9.fsf@posteo.net> (raw)
Hi,
There are some popular packages on GNU ELPA (and I expect NonGNU ELPA)
that are practically unmaintained. One example would be Yasnippet that
has been gathering issues and pull requests on GitHub, mostly without
any comments whatsoever. For example, see
https://github.com/joaotavora/yasnippet/issues. Does anyone know of any
other packages of this kind?
I'd like to ask, if there some point at which should one should go from
regarding packages like these from "de facto unmaintained" to "actually
abandoned"? Perhaps if there was no real activity for over a year,
despite constant contributions? Would it make sense to call for anyone
new to take over maintaining the package? Or depending on how long the
package has been unmaintained, how popular the package is, how much
effort it would take to apply the changes one could modify the package
in elpa.git/nongnu.git and inform the maintainers that if they decide to
start working on the package again, that there are downstream changes
that they should look at.
next reply other threads:[~2022-05-29 21:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 21:34 Philip Kaludercic [this message]
2022-05-29 21:41 ` What to do about unmaintained ELPA packages 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
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=87k0a42fc9.fsf@posteo.net \
--to=philipk@posteo.net \
--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.