all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja <akib@disroot.org>
To: Richard Stallman <rms@gnu.org>, Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: What to do about unmaintained ELPA packages
Date: Tue, 31 May 2022 16:31:17 +0600	[thread overview]
Message-ID: <87a6ayt2mi.fsf@disroot.org> (raw)
In-Reply-To: <E1nvoGG-000763-Ng@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]

Richard Stallman <rms@gnu.org> writes:

> [[[ 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. ]]]
>
>   > 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?
>
> There is no need to have a rigid rule about this, but we should have a
> rough guide to go by.  "Serious problems go unfixed for a year" sounds
> like enough reason to judge that there is a problem in maintaining
> that package.  We don't need a rule about what we do if that happens,
> but we should take note of such packages and decide what to do.

"Serious problems go unfixed for a year" - I don't think this is always
a result of maintainance problem.  It may happen that the maintainer is
unable to fix it, because either they aren't smart enough or they can't
fix it due any other problem (maybe upstream bug, or they don't own the
machine needed to reproduce and fix the problem).

>
> If a package is important enough, we might want to take action sooner
> than that.  We can fix any GNU ELPA package if we see fit.  We should
> try to discuss that with its maintainers first, but if they are
> nonresponsive, we don't have to wait to satisfy some rule.

Yeah, we can fix GNU ELPA packages, since those are part of Emacs.

But what about NonGNU ELPA packages?  I think we should try to talk with
the maintainer, and possibly send a fix if its appropiate to do so.  And
in case they aren't responding, we should add a notice like UNMAINTAINED
in the summany line.  We can also to remove the package, but I think its
not right to do so, for the user's sake.

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

-- 
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-05-31 10:31 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
2022-05-30 22:53 ` Richard Stallman
2022-05-31 10:31   ` Akib Azmain Turja [this message]
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=87a6ayt2mi.fsf@disroot.org \
    --to=akib@disroot.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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.