unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Bozhidar Batsov <bozhidar@batsov.dev>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package)
Date: Fri, 7 Jan 2022 04:54:45 -0600	[thread overview]
Message-ID: <CADwFkmk1K-yQpsuDdtZ2+RqDsot+UZtnjpnOQDRuZA=c70pkkQ@mail.gmail.com> (raw)
In-Reply-To: <7e6e189d-0c74-4f0f-9cfc-40fb87bf1b02@www.fastmail.com>

"Bozhidar Batsov" <bozhidar@batsov.dev> writes:

> Fair enough. I'm a bit concerned that often evaluations of the
> quality/usefulness of something are subjective (e.g. the people who
> like flymake would argue that flycheck might be "redundant", etc). To
> me - it's fine to try to solve the same problem in multiple ways if
> there's no clearly superior way of doing something. I guess a package
> is never really obsolete until no one uses it and maintains it.

FWIW, this makes sense to me.

> In general I agree that some quality criteria have to be met for a
> package to be included on NGE, I just hope that those criteria are
> going to be of the objective kind.

Here's how I see the current situation:

We currently have the luxury to pick and choose which packages get
added.  In the future, users or developers will increasingly ask us to
include this or that package.  I think it will be rare that we should
have any reason to deny such requests.

Currently, I won't spend my limited time working on adding things that I
see little value in, as there are so many important packages that are
still missing.  However, if someone makes an explicit request for
something, I would think about encouraging such participation by
prioritizing it above something that I would otherwise see as higher
priority.



  reply	other threads:[~2022-01-07 10:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164145738158.2838.5769558384331859964@vcs2.savannah.gnu.org>
     [not found] ` <20220106082302.0A19CC0DA1E@vcs2.savannah.gnu.org>
2022-01-06 10:02   ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Philip Kaludercic
2022-01-06 12:00     ` Stefan Kangas
2022-01-06 13:35       ` Philip Kaludercic
2022-01-06 14:30         ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Monnier
2022-01-06 15:03           ` Bozhidar Batsov
2022-01-06 17:07             ` Packages quality Stefan Monnier
2022-01-06 19:50               ` Tim Cross
2022-01-07  7:54               ` Stefan Kangas
2022-01-07 11:45                 ` John Yates
2022-01-07 12:16                   ` Stefan Kangas
2022-01-07 15:52                     ` John Yates
2022-01-07  7:55             ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Kangas
2022-01-07 10:22               ` Bozhidar Batsov
2022-01-07 10:54                 ` Stefan Kangas [this message]
2022-01-06 17:28           ` Packages quality Philip Kaludercic
2022-01-06 19:55         ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Juri Linkov
2022-01-07  7:55         ` Stefan Kangas
2022-01-16 17:49           ` Philip Kaludercic
2022-01-16 22:19             ` Stefan Monnier
2022-01-19  8:57               ` Philip Kaludercic
2022-01-19 15:19                 ` Stefan Monnier
2022-01-16 22:32             ` Stefan Kangas
2022-01-16 23:16               ` Ergus
2022-01-19  9:05                 ` Philip Kaludercic
2022-01-16 23:47               ` Stefan Monnier
2022-01-19  9:03               ` Philip Kaludercic
2022-01-17  7:37             ` Jean Louis
2022-01-19  9:10               ` Philip Kaludercic
2022-01-07 10:02         ` Stefan Kangas
2022-01-10  1:18           ` Stefan Monnier
2022-01-07  9:38     ` Augusto Stoffel

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='CADwFkmk1K-yQpsuDdtZ2+RqDsot+UZtnjpnOQDRuZA=c70pkkQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --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 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).