unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: What to do about unmaintained ELPA packages
Date: Sun, 29 May 2022 17:41:14 -0400	[thread overview]
Message-ID: <jwv35gs81ft.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k0a42fc9.fsf@posteo.net> (Philip Kaludercic's message of "Sun,  29 May 2022 23:34:14 +0200")

Philip Kaludercic [2022-05-29 23:34:14] wrote:
> 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?

Of course, especially for popular packages.

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

Yes, we can use `:url nil` to indicate that `elpa.git` is considered as
"the upstream".  Of course, it's better if the current upstream can be
modified to point back to us as the upstream so as to try avoiding
accidental divergence in the future.


        Stefan




  reply	other threads:[~2022-05-29 21:41 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 [this message]
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

  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=jwv35gs81ft.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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).