unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: Jimmy Aguilar Mena <jimmy.aguilar@bsc.es>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
	John Yates <john@yates-sheets.org>
Subject: Re: [ELPA] Package cleanup
Date: Wed, 30 Mar 2022 09:31:11 +0200	[thread overview]
Message-ID: <87r16j99s0.fsf_-_@gmx.de> (raw)
In-Reply-To: <SJ0PR10MB5488C6D5CD40B233A90A76C6F31E9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Tue, 29 Mar 2022 22:04:47 +0000")

Drew Adams <drew.adams@oracle.com> writes:

Hi,

>> I would like to assume that ELPA is a somewhat curated
>> collection of packages.  Perhaps not as rigorously tested
>> and maintained as Emacs itself, but more so than some
>> package on github that has not seen an update in 5 years.
>>
>> If the only virtue of being on ELPA is that I can install via
>> package.el then that seems like rather thin gruel.
>>
>> Perhaps the bar for admission to ELPA is too low.  Could
>> we require automated tests that can be run regularly to
>> confirm package health?
>
> Your last sentence makes sense.  (But on whom
> should the requirement fall?  The curator?  The
> package contributor?)

It is on my longer TODO list to activate automatic tests for GNU ELPA
packages on emba.gnu.org. Yes, only for "GNU" ELPA packages.

Unfortunately, these days I'm the only one who works on emba, and there
are many other TODO items. So I have no idea if/when this will happen.

Best regards, Michael.



  parent reply	other threads:[~2022-03-30  7:31 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
2022-03-30  1:43         ` Drew Adams
2022-03-31  4:27         ` Richard Stallman
2022-03-30  7:31       ` Michael Albinus [this message]
2022-03-30  8:35     ` 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

  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=87r16j99s0.fsf_-_@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jimmy.aguilar@bsc.es \
    --cc=john@yates-sheets.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).