unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Jimmy Aguilar Mena <jimmy.aguilar@bsc.es>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Package cleanup
Date: Fri, 01 Apr 2022 00:07:15 -0400	[thread overview]
Message-ID: <E1na8Z9-000366-4R@fencepost.gnu.org> (raw)
In-Reply-To: <20220330045602.4j55nyt52lyib3c6@Ergus> (message from Jimmy Aguilar Mena on Wed, 30 Mar 2022 06:56:02 +0200)

[[[ 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. ]]]

  > >There are many questions we'd want to check
  > >to decide what to do with each package.
  > >
  > But if they don't receive any update for years,

That's the case that was brought up.

                                                    and the bug reports
  > accumulate 

That wasn't mentioned before.  It makes a difference.  Depending on
what those bugs do, we might delete (or obsolete) the package -- but
not automatically and rigidly.

Another option would be to ask users to tell us what they think of the
package.

               (on github too)

How does that make a difference?

We don't use Github.  We won't ask anyone to make an account there,
since doing so requires running their nonfree software.

Supposing we find someone to fix bugs in the package, we can't fix
them on github.  We could change the GNU ELPA version to direct people
clearly to report bugs to us, so we can fix them.

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





      reply	other threads:[~2022-04-01  4:07 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
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 [this message]

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=E1na8Z9-000366-4R@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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 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).