Re: A Zine/Newsletter for ELPA

[Sacha Chua <sacha@sachachua.com>]

[-- Attachment #1: Type: text/plain, Size: 2923 bytes --]

On Sun, Oct 16, 2022, 06:15 Philip Kaludercic <philipk@posteo.net> wrote:

could announce that they don't have the interest or the time to attend
> to a package, so that a replacement could been found sooner.

> When there's an announcement, I usually put it in a Help Wanted section at
> > the start of Emacs News.
> I did not know that you do that, in that case this specific idea is
> superfluous.
>

It was helpful to discuss it, as people might not know that they can let me
know about such things. :) I use that section for other kinds of requests
for help as well, such as the recent requests for volunteers for noverlay
testing and feedback on Emacs Survey.
https://sachachua.com/blog/2022/10/2022-10-03-emacs-news/ That way, it
doesn't get lost in emacs-devel. Sometimes I notice the posts on my own,
but it also helps when people let me know.

>
> Emacs News. I'd love to get other
> > people's links and notes as well. I read emacs-devel on a very cursory
> > level (mostly looking at subjects and what Eli replies :) ), so extra
> > context would be great!
> I didn't know this either, I will keep this in mind.  If there are
> interesting bug reports, would you be interested in my notifying you?
>

Sure! I tend to not check out individual bug reports as much. All of them
matter a lot to someone, so I'd get tempted to include too many, and then
people might as well watch emacs-devel instead. If interesting
conversations grow out of them, though, such as detailed explanations of
Emacs internals or system limitations, more general requests for feedback,
the context for decisions, or other things we could use more eyes on, then
that might be something that more people might find useful. I'm sure there
are plenty of gems I miss in my quick glance, so a quick email with a link
could help. Sometimes people even cc or bcc me.

Also, since a different conversation brought up automated package
announcements: I use some code that identifies packages recently added to
GNU ELPA, NonGNU ELPA, and MELPA by comparing the archive contents with a
local cache with dates so that I can include packages when they appear.

I also have some code that includes commit summaries for things that touch
etc/NEWS in Emacs and Org, so clear commit messages are helpful. The  I
manually remove lines for some  commits (typo fixes, etc.) and reword
others if the message is not clear.

I pull in things from the Planet Emacslife feed, my Reddit upvotes, my
YouTube playlist for Emacs News (which I populate from a search for emacs,
org mode, or org roam - magit used to be a good keyword until some game
used it too), and the Emacs Calendar. Then I remove duplicates and
irrelevant things, categorize, and reorder. I also check HN, lobste.rs,
lemmy, emacs-devel, and occasionally help-gnu-emacs.

The code I use is near the bottom of the index.org in
https://github.com/sachac/emacs-news . Improvements welcome!

Sacha

>

[-- Attachment #2: Type: text/html, Size: 4540 bytes --]