From: John Yates <john@yates-sheets.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Jimmy Aguilar Mena <jimmy.aguilar@bsc.es>
Subject: Re: [External] : [ELPA] Package cleanup
Date: Tue, 29 Mar 2022 19:05:21 -0400 [thread overview]
Message-ID: <CAJnXXohf-oVvM1TUwBqJEkQeOJTWJ00+QcC1cUz7-bCmqnsaHw@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488C6D5CD40B233A90A76C6F31E9@SJ0PR10MB5488.namprd10.prod.outlook.com>
On Tue, Mar 29, 2022 at 6:05 PM Drew Adams <drew.adams@oracle.com> wrote:
> But again, whether some package starts to result
> in problems where it didn't previously doesn't
> follow from its not having been updated for 5
> years. Similarly, it doesn't at all follow that
> a package that's been updated a lot doesn't have
> problems, including doesn't introduce new problems
> from some recent update.
>
> Bugs and curating/testing are different from the
> question of update frequency or recentness.
Full agreement. Same holds true for a package on github.
Lack of update is merely a vague proxy for abandoned. And,
as you point out, abandonment does not imply non-functional.
But if there is no mechanism to, at least, identify decay then,
over time, the ratio of high quality packages to those of lesser
quality drops. Not a great recipe for brand maintenance.
next prev parent reply other threads:[~2022-03-29 23:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 0:43 [ELPA] Package cleanup Jimmy Aguilar Mena
2022-03-29 16:24 ` [External] : " Drew Adams
2022-03-29 21:41 ` John Yates
2022-03-29 22:04 ` Drew Adams
2022-03-29 23:05 ` John Yates [this message]
2022-03-30 1:43 ` Drew Adams
2022-03-31 4:27 ` Richard Stallman
2022-03-30 7:31 ` Michael Albinus
2022-03-30 8:35 ` [External] : " Stefan Monnier
2022-03-30 14:09 ` Jimmy Aguilar Mena
2022-03-30 21:23 ` Stefan Monnier
2022-03-31 4:27 ` Richard Stallman
2022-03-30 3:12 ` Richard Stallman
2022-03-30 3:44 ` Po Lu
2022-03-30 7:56 ` João Távora
2022-03-30 4:56 ` Jimmy Aguilar Mena
2022-04-01 4:07 ` 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=CAJnXXohf-oVvM1TUwBqJEkQeOJTWJ00+QcC1cUz7-bCmqnsaHw@mail.gmail.com \
--to=john@yates-sheets.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jimmy.aguilar@bsc.es \
/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.