From: Emanuel Berg <incal@dataswamp.org>
To: emacs-tangents@gnu.org
Subject: Re: A Zine/Newsletter for ELPA
Date: Sat, 15 Oct 2022 09:10:03 +0200 [thread overview]
Message-ID: <87tu45zho4.fsf@dataswamp.org> (raw)
In-Reply-To: 87mt9y6rdt.fsf@posteo.net
Philip Kaludercic wrote:
> I have recently been thinking if creating a little monthly±n
> zine (https://en.wikipedia.org/wiki/Zine) or newsletter for
> {GNU,NonGNU} ELPA would be a nice idea. Somewhere where new
> packages and releases can not only be announced but also
> commented on and "reviewed". Perhaps also a place where
> people can post ideas for packages or where abandoned
> packages can find new maintainers. Basically anything on the
> topic of Emacs packages, in one package.
>
> Starting and organising such a project doesn't sound easy,
> and I don't know if it is worth it to begin with. I am
> wondering if anyone else things this is a good idea and
> would be interested in participating to initiate something
> more concrete?
Good idea, but why not an Emacs newsletter in general
(including the ELPAs)?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-10-15 7:10 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 [this message]
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
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=87tu45zho4.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-tangents@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.
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).