From: Sacha Chua <sacha@sachachua.com>
To: emacs-devel@gnu.org
Subject: Re: Let's announce each new package added to GNU ELPA or NonGNU ELPA
Date: Mon, 14 Feb 2022 13:05:25 -0500 [thread overview]
Message-ID: <874k519vdm.fsf@sachachua.com> (raw)
In-Reply-To: 87wni4rp72.fsf@gmx.de
Michael Albinus <michael.albinus@gmx.de> writes:
Hello, all!
>> I don't know if it is necessary, whenever a package gets added to an
>> archive, it is marked as "new" in the package list. Given a decent
>> commentary section (something I often mention to package maintainers),
>> you also get a good overview of what the package does.
> And there are the weekly Emacs News by Sacha Chua, which summarize also
> the new packages of the week.
I can add archive source to the package lines, like this:
- New packages:
- helm-twitch: Navigate Twitch.tv via `helm' (MELPA)
- org-journal-tags: Tagging and querying system of org-journal (MELPA)
- org-remark: Highlight & annotate any text files (GNU ELPA)
- paimon: A major mode for Splunk (MELPA)
- simplicity-theme: A minimalist dark theme (MELPA)
The caps feel a little visually cluttered, though.
Here's the 2022-02-14 edition in the emacs-tangents web archive:
https://lists.gnu.org/archive/html/emacs-tangents/2022-02/msg00001.html
When I get some focused time, I might be able to get the code to notice
when something has been newly listed in an archive even though it's
already been listed in a different archive, as might be the case for
MELPA packages that get listed on GNU ELPA or NonGNU ELPA. Maybe
something like
- some-package: description goes here (newly listed on GNU ELPA, also
on MELPA)
although maybe that's a bit long?
A number of people have mentioned noticing packages from this list
before, so some people do read it. An RSS or ATOM feed of new packages
and a feed of updated packages would probably be even more handy, or
maybe having created/modified dates baked into the package contents list
or a separate file. At the moment, I compare the package archive
contents with a datestamped list I store in a file, which is very
hackish.
Sacha
next prev parent reply other threads:[~2022-02-14 18:05 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 [this message]
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=874k519vdm.fsf@sachachua.com \
--to=sacha@sachachua.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).