From: Richard Stallman <rms@gnu.org>
To: Tim Cross <theophilusx@gmail.com>
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 23:37:34 -0500 [thread overview]
Message-ID: <E1nINgc-0001rG-5h@fencepost.gnu.org> (raw)
In-Reply-To: <87wni47bph.fsf@gmail.com> (message from Tim Cross on Wed, 09 Feb 2022 18:09:46 +1100)
[[[ 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. ]]]
> I think
> a regular (weekly, fortnightly, monthly, whatever - monthly probably
> sufficient) summary type message which contains new packages since the
> last summary would be better than multiple messages containing details
> of only one package at a time.
I have to disagree. Announcing each separately would help/encourage
people to look at each one and think about it for a few seconds --
"Would this be useful for me?"
By contrast, announcing several packages together would help/encourage
people not to look at all of them. Many would only notice the first
one. The only benefit would be to reduce the total number of
messages.
How much is that benefit? With some data, we could see.
Can anyone find the last 10 packages added to GNU ELPA,
and the date each one was added?
--
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)
next prev parent reply other threads:[~2022-02-11 4:37 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 [this message]
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
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=E1nINgc-0001rG-5h@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@gmail.com \
/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).