unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Sacha Chua <sacha@sachachua.com>
To: John Yates <john@yates-sheets.org>
Cc: Philip Kaludercic <philipk@posteo.net>, emacs-tangents@gnu.org
Subject: Re: A Zine/Newsletter for ELPA
Date: Sat, 15 Oct 2022 12:00:14 -0400	[thread overview]
Message-ID: <CAJGZZeLpajZg5ghzm0TB7Y89dSxuCUJBsS83qTv7DA=0AfOmkA@mail.gmail.com> (raw)
In-Reply-To: <CAJnXXohBms-8ohu4Vgc341H-k5ROYaAu2f8wMR-QB=P2-C8+dw@mail.gmail.com>

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

On Sat, Oct 15, 2022, 11:25 John Yates <john@yates-sheets.org> wrote:

>
 mechanism.  Perhaps an ELPA section in
> Sacha's Emacs News would suffice.
>

I have a list of new packages at the end of the newsletter, and I've
recently started indicating their package archive as well. In addition, I
email info-gnu-emacs@gnu.org when I notice new GNU ELPA packages.

> but also commented on and "reviewed".
> This seems to suggest a review site.  (A quick web search suggests
> that there are frameworks out there to facilitate creating such
> sites.)  That said, posting opinions seems of low value and rarely
> actionable (see below).
>

Prot does a great job of writing blog posts and often making videos about
his new packages, which are usually posted to GNU ELPA. I link to these in
Emacs News, and they'll probably come up in searches as well. I notice that
interesting new packages tend to get picked up in blog posts and Reddit
threads in the weeks after the packages are published. I currently don't
have the time to summarize posts beyond quick links, but perhaps someone
would like to do a monthly round up like the way This Month in Org does?

>
> Perhaps also a place where people can post ideas for packages
> This is a conversation.  Would not a mailing list suffice.  What is
> wrong with help-gnu-emacs?
>

I sometimes see conversations like that grow out of mailing lists or
web-based forums like Reddit. Ideas are pretty easy to float, though, and
it's hard to match them up with a person with the same itch. It seems to
work out better when people share what they've figured out so far, then
other people say they want something like that too, and then the code gets
turned into a package.

> or where abandoned packages can find new maintainers.
> How would this relate to https://github.com/emacsattic?
>

When there's an announcement, I usually put it in a Help Wanted section at
the start of Emacs News.

I am very impressed with Eli's leadership of emacs development.


Eli is awesome!

More immediately, look at his effort to drive toward better
> abstraction and unification of the existing find-file and
> find-sibling-file with Damien Cassou's pending related-files.  This is
> exactly the sort of effort I would hope to support.  I see such
> activities as curation.  Thus I could imagine an emacs-curate mailing
> list.  I would be happy to subscribe.
>

Andres Ramirez has been sending me links to interesting emacs-devel
messages for possible inclusion in 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!

Sacha

>

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

  reply	other threads:[~2022-10-15 16:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 21:13 A Zine/Newsletter for ELPA Philip Kaludercic
2022-10-15  7:10 ` Emanuel Berg
2022-10-15  9:41   ` Philip Kaludercic
2022-10-15 12:07     ` Sacha Chua
2022-10-15 15:24       ` John Yates
2022-10-15 16:00         ` Sacha Chua [this message]
2022-10-16 10:15           ` Philip Kaludercic
2022-10-16 12:32             ` Sacha Chua
2022-10-16 22:41               ` Emanuel Berg
2022-10-16 14:12             ` Eduardo Ochs
2022-10-16 14:31               ` Jean Louis
2022-10-16 22:37                 ` Emanuel Berg
2022-10-16 14:39               ` Philip Kaludercic
2022-10-15 20:42         ` Emanuel Berg
2022-10-15  7:14 ` Marcin Borkowski
2022-10-15  7:18   ` Emanuel Berg
2022-10-15  9:42 ` Lars Ingebrigtsen
2023-03-21 19:55 ` Philip Kaludercic
2023-03-22  2:42   ` orzodk
2023-03-22  8:55     ` Philip Kaludercic
2023-03-22 16:33       ` orzodk
2023-03-23 14:07         ` Philip Kaludercic

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='CAJGZZeLpajZg5ghzm0TB7Y89dSxuCUJBsS83qTv7DA=0AfOmkA@mail.gmail.com' \
    --to=sacha@sachachua.com \
    --cc=emacs-tangents@gnu.org \
    --cc=john@yates-sheets.org \
    --cc=philipk@posteo.net \
    /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.
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).