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.devel Subject: Re: Let's announce each new package added to GNU ELPA or NonGNU ELPA Date: Mon, 14 Feb 2022 13:05:25 -0500 Message-ID: <874k519vdm.fsf@sachachua.com> References: <87ee4c4dne.fsf@posteo.net> <87wni4rp72.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37237"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:1pn6ebi9d9qxr8PCF/rZQozqrSw= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 14 19:07:23 2022 Return-path: Envelope-to: ged-emacs-devel@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 1nJfkw-0009Rk-HY for ged-emacs-devel@m.gmane-mx.org; Mon, 14 Feb 2022 19:07:22 +0100 Original-Received: from localhost ([::1]:59886 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nJfkv-0003hL-8H for ged-emacs-devel@m.gmane-mx.org; Mon, 14 Feb 2022 13:07:21 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:34282) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJfjG-0002Hv-SC for emacs-devel@gnu.org; Mon, 14 Feb 2022 13:05:38 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:59198) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJfjE-0006n5-3M for emacs-devel@gnu.org; Mon, 14 Feb 2022 13:05:38 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nJfjB-0006pn-R7 for emacs-devel@gnu.org; Mon, 14 Feb 2022 19:05:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286289 Archived-At: Michael Albinus writes: Hello, all! >> I don't know if it is necessary, whenever a package gets added to an >> archive, it is marked as "new" in the package list. Given a decent >> commentary section (something I often mention to package maintainers), >> you also get a good overview of what the package does. > And there are the weekly Emacs News by Sacha Chua, which summarize also > the new packages of the week. I can add archive source to the package lines, like this: - New packages: - helm-twitch: Navigate Twitch.tv via `helm' (MELPA) - org-journal-tags: Tagging and querying system of org-journal (MELPA) - org-remark: Highlight & annotate any text files (GNU ELPA) - paimon: A major mode for Splunk (MELPA) - simplicity-theme: A minimalist dark theme (MELPA) The caps feel a little visually cluttered, though. Here's the 2022-02-14 edition in the emacs-tangents web archive: https://lists.gnu.org/archive/html/emacs-tangents/2022-02/msg00001.html When I get some focused time, I might be able to get the code to notice when something has been newly listed in an archive even though it's already been listed in a different archive, as might be the case for MELPA packages that get listed on GNU ELPA or NonGNU ELPA. Maybe something like - some-package: description goes here (newly listed on GNU ELPA, also on MELPA) although maybe that's a bit long? A number of people have mentioned noticing packages from this list before, so some people do read it. An RSS or ATOM feed of new packages and a feed of updated packages would probably be even more handy, or maybe having created/modified dates baked into the package contents list or a separate file. At the moment, I compare the package archive contents with a datestamped list I store in a file, which is very hackish. Sacha