From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Let's announce each new package added to GNU ELPA or NonGNU ELPA
Date: Wed, 09 Feb 2022 18:09:46 +1100 [thread overview]
Message-ID: <87wni47bph.fsf@gmail.com> (raw)
In-Reply-To: <E1nHeDC-00078W-KA@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> [[[ 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 it would be wise and helpful to announce each new package
> added for the first time to GNU ELPA or NonGNU ELPA. These
> hand-written announcements would contain a brief paragraph that
> summarizes what the package does. (This text could be stored in the
> repo so people could look at it later.)
>
> The natural place to post these announcements is on info-gnu-emacs.
> However, if the rate of new packages in NonGNU ELPA would lead to too
> many messages for that list, we could announce the NonGNU ELPA
> packages on some other list.
>
> Each package would be announced this way only once. Each _new
> version_ of a package is announced automatically on gnu-emacs-sources;
> for new versions, that is enough. But those automatic announcements
> don't say whether the package is new.
>
> What do people think?
Ignoring the question of who will generate these announcements, 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.
next prev parent reply other threads:[~2022-02-09 7:09 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 [this message]
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
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=87wni47bph.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-devel@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).