From: John Yates <john@yates-sheets.org>
To: Sacha Chua <sacha@sachachua.com>
Cc: Philip Kaludercic <philipk@posteo.net>, emacs-tangents@gnu.org
Subject: Re: A Zine/Newsletter for ELPA
Date: Sat, 15 Oct 2022 11:24:53 -0400 [thread overview]
Message-ID: <CAJnXXohBms-8ohu4Vgc341H-k5ROYaAu2f8wMR-QB=P2-C8+dw@mail.gmail.com> (raw)
In-Reply-To: <CAJGZZeJFcH07qEfDH5ruCOwgT0maXRw-2K9=hdFNj01nigQ2zw@mail.gmail.com>
These goals seem to conflate multiple wishes:
> Somewhere where new packages and releases can not only be announced
Announcements have limited shelf life. They should be handled via
some form of notification mechanism. Perhaps an ELPA section in
Sacha's Emacs News would suffice.
> 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).
> 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?
> or where abandoned packages can find new maintainers.
How would this relate to https://github.com/emacsattic?
> Basically anything on the topic of Emacs packages, in one package.
Seems too amorphous to be sustainable.
My two cents...
I am very impressed with Eli's leadership of emacs development. Look
at all the goodness that is going into version 29, his commitment to
tightening the release cadence, his willingness to say 'no' to both
RMS and bikeshedders, etc. To have my support, a proposal should
serve to enhance Eli's contributions.
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.
/john
next prev parent reply other threads:[~2022-10-15 15:24 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 [this message]
2022-10-15 16:00 ` Sacha Chua
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='CAJnXXohBms-8ohu4Vgc341H-k5ROYaAu2f8wMR-QB=P2-C8+dw@mail.gmail.com' \
--to=john@yates-sheets.org \
--cc=emacs-tangents@gnu.org \
--cc=philipk@posteo.net \
--cc=sacha@sachachua.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.
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).