unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: How often do we have new packages in Whichever ELPA?
Date: Wed, 16 Feb 2022 14:18:24 +0200	[thread overview]
Message-ID: <83h78z2een.fsf@gnu.org> (raw)
In-Reply-To: <E1nKBhx-00055O-KJ@fencepost.gnu.org> (message from Richard Stallman on Tue, 15 Feb 2022 23:14:25 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: philipk@posteo.net, emacs-devel@gnu.org
> Date: Tue, 15 Feb 2022 23:14:25 -0500
> 
>   > > Given that info, I think that posting these on info-gnu-emacs would be
>   > > a bad idea.  That list has a very low volume of mail.  This could make
>   > > it 10 or 20 times as much.  There are probably people on it who don't
>   > > want to get a higher volume from it.
> 
>   > We could use a telltale Subject, or some X-* header that people could
>   > use to filter out those.
> 
> I don't follow.  Could you describe that proposal more concretely?
> What would be in the messages we post, and who would filter?

If the Subject starts with "[ELPA News]", people who aren't interested
can configure their MUA to ignore those messages.

>   > So I'm unsure why this issue needs any action at this time, since we
>   > seem to be doing TRT already.  Or what am I missing?
> 
> Right now, every new version in GNU ELPA or NonGNU ELPA is announced
> on a list, gnu-emacs-sources, that not many people read.
> 
> I think that we should announce NEW packages in GNU ELPA in a bigger
> list where more people will see them.  Maybe also NEW packages in
> NonGNU ELPA.

The only bigger lists are this one and help-gnu-emacs.  Any other list
would be a new list that will suffer from the same problem as
gnu-emacs-sources.  I thought emacs-devel and help-gnu-emacs were
deemed not to be the best candidates, but if I misunderstood, I have
nothing against using them.  However, I think you should keep in mind
that most Emacs users nowadays rarely if ever read mailing lists, let
alone subscribe to them.  So I'm not at all sure the rejection of
gnu-emacs-sources is justified, especially since that is practice we
use for a long time, and people who want to know about ELPA news
learned about that list long ago.

Let's not make the perfect be the enemy of the good!



  reply	other threads:[~2022-02-16 12:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12  3:57 Misleading messages about new versions Richard Stallman
2022-02-12  4:36 ` Stefan Monnier
2022-02-14  4:14   ` How often do we have new packages in Whichever ELPA? Richard Stallman
2022-02-14  8:33     ` Philip Kaludercic
2022-02-15  4:30       ` Richard Stallman
2022-02-15 13:27         ` Eli Zaretskii
2022-02-16  4:14           ` Richard Stallman
2022-02-16 12:18             ` Eli Zaretskii [this message]
2022-02-16 10:42         ` Rudolf Schlatte
2022-02-19  4:54           ` Richard Stallman
2022-02-16 18:28         ` Tomas Hlavaty
2022-02-16 20:07           ` Philip Kaludercic
2022-02-19  4:56             ` Richard Stallman
2022-02-17 23:14           ` Richard Stallman
2022-02-14  4:14   ` Misleading messages about new versions Richard Stallman
2022-02-14 12:47     ` Stefan Monnier
2022-02-14 17:27     ` Benjamin Riefenstahl
2022-02-14 18:31       ` Corwin Brust
2022-02-14 18:44         ` Benjamin Riefenstahl
2022-02-14 19:11       ` Jean Louis
2022-02-15  4:31       ` 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=83h78z2een.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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).