unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Let's announce each new package added to GNU ELPA or NonGNU ELPA
Date: Thu, 10 Feb 2022 23:37:32 -0500	[thread overview]
Message-ID: <E1nINga-0001qY-RG@fencepost.gnu.org> (raw)
In-Reply-To: <87ee4c4dne.fsf@posteo.net> (message from Philip Kaludercic on Wed, 09 Feb 2022 09:01:25 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > I think it would be wise and helpful to announce each new package
  > > added for the first time to GNU ELPA or NonGNU ELPA.  These
  > > hand-written announcements would contain a brief paragraph that
  > > summarizes what the package does.  (This text could be stored in the
  > > repo so people could look at it later.)

  > Are you thinking about an automated system, or should the people that
  > add the package to elpa.git/nongnu.git send a separate message?

If the scripts could tell the difference between a newly added package
and a new version, it could be good to make the script detect this
and change the automatic announcement accordingly.

BUT the new-package announcement should NOT be a minor variation on
the update announcement.  On the contrary, we should make the two look
quite different, to make sure readers notice new packages.

Also, it would be desirable for new package announcements
to give more info about what the package does.
(The one or two lines now included in the update announcements
are good, for the update announcements.  I wouldn't want to change that.)

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2022-02-11  4:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  4:04 Let's announce each new package added to GNU ELPA or NonGNU ELPA Richard Stallman
2022-02-09  7:09 ` Tim Cross
2022-02-11  4:37   ` Richard Stallman
2022-02-09  9:01 ` Philip Kaludercic
2022-02-09 16:15   ` Michael Albinus
2022-02-12  3:57     ` Richard Stallman
2022-02-12  4:03       ` [External] : " Drew Adams
2022-02-14  4:14         ` Richard Stallman
2022-02-14  5:09           ` Corwin Brust
2022-02-14 18:05     ` Sacha Chua
2022-02-10  3:56   ` Richard Stallman
2022-02-10  9:11     ` Philip Kaludercic
2022-02-10 12:18       ` Eli Zaretskii
2022-02-11  4:37   ` Richard Stallman [this message]
2022-02-11 13:01     ` Stefan Monnier

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=E1nINga-0001qY-RG@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).