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: Stefan Kangas <stefan@marxist.se>,  emacs-devel@gnu.org
Subject: Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package)
Date: Thu, 06 Jan 2022 09:30:31 -0500	[thread overview]
Message-ID: <jwvbl0pq6z2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87tueh3s2x.fsf@posteo.net> (Philip Kaludercic's message of "Thu,  06 Jan 2022 13:35:18 +0000")

> Do we want to collect as many packages as possible, even if the
> implementations and practices are sub-optimal, are displaced by
> alternative implementations in Emacs or ELPA, etc. or should we try to
> restrict the packages to popular, "good citizens" of the Emacs package
> space, in an effort to raise the standards and clean up "obsolete" and
> "redundant" packages.  It is probably clear that I have an inclination
> towards the latter position: Going forward it seems preferable to have
> as many useful and idiomatic packages available directly via the ELPAs,
> without burdening newcomers with duplicate functionalities.  My
> motivation in contributing to NonGNU ELPA is to further this goal.

Note that (Non)GNU ELPA in the long term will inevitably also contain
old/redundant/outdated packages unless we go and actively remove such
packages (which we haven't done so far).

So, I think if we want to improve the quality, in the long term, the way
to do that is not just by restricting which packages we add, but by
finding ways to regularly re-assess the quality of packages and coming
up with good ways to remove/demote packages based on that (and similarly
promote those packages that are currently particularly good).


        Stefan




  reply	other threads:[~2022-01-06 14:30 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         ` Stefan Monnier [this message]
2022-01-06 15:03           ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) 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
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=jwvbl0pq6z2.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=stefan@marxist.se \
    /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).