From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Sacha Chua Newsgroups: gmane.emacs.tangents Subject: Re: A Zine/Newsletter for ELPA Date: Sun, 16 Oct 2022 08:32:49 -0400 Message-ID: References: <87mt9y6rdt.fsf@posteo.net> <87tu45zho4.fsf@dataswamp.org> <87zgdx5sqk.fsf@posteo.net> <871qr85b1w.fsf@posteo.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000050df2305eb260fd5" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38936"; mail-complaints-to="usenet@ciao.gmane.io" Cc: John Yates , emacs-tangents@gnu.org To: Philip Kaludercic Original-X-From: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Sun Oct 16 14:45:14 2022 Return-path: Envelope-to: get-emacs-tangents@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ok30z-0009tt-Sy for get-emacs-tangents@m.gmane-mx.org; Sun, 16 Oct 2022 14:45:14 +0200 Original-Received: from localhost ([::1]:46166 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ok30y-000327-T9 for get-emacs-tangents@m.gmane-mx.org; Sun, 16 Oct 2022 08:45:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54298) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ok2pG-0006Zb-47 for emacs-tangents@gnu.org; Sun, 16 Oct 2022 08:33:06 -0400 Original-Received: from mail-io1-xd35.google.com ([2607:f8b0:4864:20::d35]:42745) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ok2pD-00016s-O7 for emacs-tangents@gnu.org; Sun, 16 Oct 2022 08:33:05 -0400 Original-Received: by mail-io1-xd35.google.com with SMTP id 137so7185717iou.9 for ; Sun, 16 Oct 2022 05:33:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sachachua-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=P2VFnAPXwN3h+V9IPApsAhdmRC+DPHjZSUP8Dzqulis=; b=oyMkfon1/ABcE/Pa8vmYDGb4u6KL3vlmUltbLxF5xspVxQ4wtI8QGzN/NX4Greyezl HyqLufuWI52IyzzJn38hd/6RIwdIcVYuqNl+AzR1R3UXhXujiNhHGPZzMVo+kYvLKX4u X/UyBmXY6YJcRShXPSg6pZZ0K/Uc9iRE9XIcsR+y74N2XSFiuIw5NATXfMfhoAWpziMw 64ys2Jp8f2UEdKx0T1WRluTb44lJQmAs+IwRczBQdYzKHfZIsCR0sEg3DRY2t49YzWc3 j4lhlDJc2Ke/qlELzwrqadvCBS8/K7mM8spe/BuQzPC8dyRt/03JURGhKf1BoUpRphBe pcAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=P2VFnAPXwN3h+V9IPApsAhdmRC+DPHjZSUP8Dzqulis=; b=kv9aXDLoJjp2x3/HVG8gKWNFyNF2cMGPKq77sXUD4TZoI+OOzBLzClxp1crS3ElX46 Mc5KWl0xLsv36vXUcK5l+UD/s3664xO9GqHfJ4hRIkZrIXvptlfx7WZ9I/xaqUYgNFcw wPJDeZfwymCFGDckn0tEiSwZ6BAV1KX5YdguGYjb7Ls6DdPg1NZ/SIOnaS5qYHkRoSka xIkmuLQRCiDfol/z60ZXbRNbDhgRu41AQ0sCMN4XkgvwbPyJmvVmTL+70HhSStXlAYnU 4mFc7Y6WaQ29Au6Yuz+tmPOd3FTOcrETvinoGGBsQQIXNOmfvuUECEVnQD+2XxvRKVND BIxg== X-Gm-Message-State: ACrzQf38h2c1aXsa3OEnVI3DpDnIqEXmKJM6LzYUf2sxTlhpaTm5Hiqb Tv94Csbj45fIpeTeaY2SzgwGdxLwEVShzcrJuJsnqEoo9zg= X-Google-Smtp-Source: AMsMyM7a85aeEBKPydLc6QFi15MMVdiART6ILXV8i8TpDMoycog1vSH1CjZuDdqFOzD48EoGuLwbqpo8xf3UC+C20so= X-Received: by 2002:a05:6638:2602:b0:35a:66ec:8d99 with SMTP id m2-20020a056638260200b0035a66ec8d99mr3248095jat.170.1665923581789; Sun, 16 Oct 2022 05:33:01 -0700 (PDT) In-Reply-To: <871qr85b1w.fsf@posteo.net> Received-SPF: none client-ip=2607:f8b0:4864:20::d35; envelope-from=sacha@sachachua.com; helo=mail-io1-xd35.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-tangents@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-tangents" Xref: news.gmane.io gmane.emacs.tangents:937 Archived-At: --00000000000050df2305eb260fd5 Content-Type: text/plain; charset="UTF-8" On Sun, Oct 16, 2022, 06:15 Philip Kaludercic 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 > --00000000000050df2305eb260fd5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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<= br> to a package, so that a replacement could been found sooner.
> When there's an announcement, I usually put it in a Help Wanted se= ction 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 the= y 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 fo= r noverlay testing and feedback on Emacs Survey.
https://= sachachua.com/blog/2022/10/2022-10-03-emacs-news/ That way, it doesn= 9;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 cur= sory
> level (mostly looking at subjects and what Eli replies :) ), so extra<= br> > context would be great!
I didn't know this either, I will keep this in mind.=C2=A0 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 peop= le might as well watch emacs-devel instead. If interesting conversations gr= ow out of them, though, such as detailed explanations of Emacs internals or= system limitations, more general requests for feedback, the context for de= cisions, or other things we could use more eyes on, then that might be some= thing 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. So= metimes 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 l= ocal cache with dates so that I can include packages when they appear.=C2= =A0

I also have some cod= e that includes commit summaries for things that touch etc/NEWS in Emacs an= d Org, so clear commit messages are helpful. The=C2=A0 I manually remove li= nes for some=C2=A0 commits (typo fixes, etc.) and reword others if the mess= age is not clear.

I pull= in things from the Planet Emacslife feed, my Reddit upvotes, my YouTube pl= aylist 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, ca= tegorize, 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 . Improvem= ents welcome!

Sacha