From: orzodk <orzodk@fastmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-tangents@gnu.org
Subject: Re: A Zine/Newsletter for ELPA
Date: Wed, 22 Mar 2023 10:33:55 -0600 [thread overview]
Message-ID: <m17cv83fv0.fsf@blahblah.localdomain> (raw)
In-Reply-To: <87edph5fmp.fsf@posteo.net> (Philip Kaludercic's message of "Wed, 22 Mar 2023 08:55:58 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> orzodk <orzodk@fastmail.com> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>
>> As far as scope goes I think it wouldn't be too hard scrape the
>> Gnu/NonGnu package pages then compare what's changed since the last
>> newsletter. There was even a blog post about scraping with org-mode[1] a
>> few days ago (via irreal). (The frequency of the newsletter seems best
>> based on how often interesting changes land in these packages.)
>
> There wouldn't be any need to take that route, all the new packages are
> documented in their respective repositories:
>
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/log/?qt=grep&q=New
> https://git.savannah.gnu.org/cgit/emacs/nongnu.git/log/?qt=grep&q=New
>
>> So I think what you're asking is if there is interest in the
>> review/commentary aspect of the newsletter? I'd be interested in
>> following along on SourceHut (as I'm sure other fellow lurkers would be)
>> but I can't say that I have any great insight to contribute. If it's
>> just helping groking the CHANGELOG since the last version that's
>> something I'm more capable of.
>
> I don't think there are going to be great insights going on here. My
> plan would be to start a mailing list that contributors could sign up
> onto, where new packages would be announced, and people could respond
> with their comments, however brief or detailed, perhaps even in whatever
> format (org, markdown, blog posts, video, etc.). These would then be
> collected into a article.
Ah, understood.
>> As another note: Emanuel mentioned an Emacs newsletter would be an
>> interseting idea as well but scope was a concern[2]. As a way to boot
>> strap this whole process it might be worth while approaching some of the
>> bloggers in the community to see if they'd be interested in writing
>> "guest posts" or even giving you permission to "cross post" some of
>> their older articles.
>
> Hmm, do you have any concrete people in mind?
I don't know either of these people but I enjoy Mickey Peterson's
Mastering Emacs (https://www.masteringemacs.org/all-articles) and Vernon
Grant's Discovering Emacs podcast.
(https://github.com/VernonGrant/discovering-emacs/tree/main/show-notes)
next prev parent reply other threads:[~2023-03-22 16:33 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
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 [this message]
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=m17cv83fv0.fsf@blahblah.localdomain \
--to=orzodk@fastmail.com \
--cc=emacs-tangents@gnu.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).