From: Philip Kaludercic <philipk@posteo.net>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Let's announce each new package added to GNU ELPA or NonGNU ELPA
Date: Thu, 10 Feb 2022 09:11:00 +0000 [thread overview]
Message-ID: <87h79713yz.fsf@posteo.net> (raw)
In-Reply-To: <E1nI0Zl-0008S7-BA@fencepost.gnu.org> (Richard Stallman's message of "Wed, 09 Feb 2022 22:56:57 -0500")
Richard Stallman <rms@gnu.org> writes:
> > Does it have to be immediate, or could a weekly-summary (something like
> > "new packages and releases") also do it?
>
> I think it will be more effective if each package gets a separate message.
> If you put two or three packages in one message, people's eyes may glaze over.
The same argument can be made for the opposite approach. If there are
too many "New package" or "Package updated" messages, I am particularly
inclined to read ever one of them in detail. The only value of separate
messages in my eyes would be that you could respond to them directly,
but that would create too much traffic, and would probably require a
separate mailing list.
I guess the real question remains who the "target audience" of these
messages would be. As Michael said, Sasha Chua's weekly update already
mentions new packages (though not package updates).
--
Philip Kaludercic
next prev parent reply other threads:[~2022-02-10 9:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 4:04 Let's announce each new package added to GNU ELPA or NonGNU ELPA Richard Stallman
2022-02-09 7:09 ` Tim Cross
2022-02-11 4:37 ` Richard Stallman
2022-02-09 9:01 ` Philip Kaludercic
2022-02-09 16:15 ` Michael Albinus
2022-02-12 3:57 ` Richard Stallman
2022-02-12 4:03 ` [External] : " Drew Adams
2022-02-14 4:14 ` Richard Stallman
2022-02-14 5:09 ` Corwin Brust
2022-02-14 18:05 ` Sacha Chua
2022-02-10 3:56 ` Richard Stallman
2022-02-10 9:11 ` Philip Kaludercic [this message]
2022-02-10 12:18 ` Eli Zaretskii
2022-02-11 4:37 ` Richard Stallman
2022-02-11 13:01 ` Stefan Monnier
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=87h79713yz.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--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).