unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: b.riefenstahl@turtle-trading.net
Cc: Richard Stallman <rms@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Misleading messages about new versions
Date: Mon, 14 Feb 2022 12:31:27 -0600	[thread overview]
Message-ID: <CAJf-WoRc+q+yJvwbqtcN5bU-NwYfXumwU5uVgavN6yFpCwH7iQ@mail.gmail.com> (raw)
In-Reply-To: <877d9xtl2e.fsf@turtle-trading.net>

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

On Mon, Feb 14, 2022, 11:28 Benjamin Riefenstahl <
b.riefenstahl@turtle-trading.net> wrote:

> Hi Richard,
>
> Richard Stallman writes:
> > For a new package, it could say,
> >
> >   We're glad to announce adding the new package Whatsit to XXGNU ELPA.
> >   The initial version number is X.Y.  Here's what Whatsit does:
>
> Careful, a machine (program) that pretends to have feelings is a spam
> generator in my book.  I would not subscribe to such a bot on principle.
>

Benny,

Respectfully, I consider this caution misguided as applied to the quotation
you kept.

We are not talking about a bot in the sense of interactive software that
generates responses from end-user interaction.
Any messages that we decide to send will be templates hand-crafted by Emacs
developers.  To deny "personality" in such messages is to deny personality
to ourselves in our capacity as developers, and by extension to the GNU
project.

That said, I think it makes sense to agree on terms and boundaries
quantifying any external character we reflect in automated communications
respecting Emacs. This, perhaps the only concesus persona possible would be
for none to be discernable.

I suspect we can do (in my view) more.  I least, I think it is worth
discussing in concrete terms and with examples and counter examples, what
may be possible in this area and if that would advance our goals and
honoring our principals.

How do you stand on ”Exciting news, we've added <pkg> to EPLA" vs RMS's
original proposal, above?   What if we added an exclamation point there?
(I think it's better without.)

To be clear,. I do agree that a message which is (or pretends to be) from a
program of some seeming "intelegence" and also uses/implies (e.g) the first
person, would be off-putting and, indeed, concerning.  For example, if
Richard's suggestion had been "Hi, this is the GNU ELPA upload ferry with
exciting news about a new package", or such, I think I would take your
point and agree with the need for caution.

WDYT?

[-- Attachment #2: Type: text/html, Size: 2797 bytes --]

  reply	other threads:[~2022-02-14 18:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12  3:57 Misleading messages about new versions Richard Stallman
2022-02-12  4:36 ` Stefan Monnier
2022-02-14  4:14   ` How often do we have new packages in Whichever ELPA? Richard Stallman
2022-02-14  8:33     ` Philip Kaludercic
2022-02-15  4:30       ` Richard Stallman
2022-02-15 13:27         ` Eli Zaretskii
2022-02-16  4:14           ` Richard Stallman
2022-02-16 12:18             ` Eli Zaretskii
2022-02-16 10:42         ` Rudolf Schlatte
2022-02-19  4:54           ` Richard Stallman
2022-02-16 18:28         ` Tomas Hlavaty
2022-02-16 20:07           ` Philip Kaludercic
2022-02-19  4:56             ` Richard Stallman
2022-02-17 23:14           ` Richard Stallman
2022-02-14  4:14   ` Misleading messages about new versions Richard Stallman
2022-02-14 12:47     ` Stefan Monnier
2022-02-14 17:27     ` Benjamin Riefenstahl
2022-02-14 18:31       ` Corwin Brust [this message]
2022-02-14 18:44         ` Benjamin Riefenstahl
2022-02-14 19:11       ` Jean Louis
2022-02-15  4:31       ` Richard Stallman

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=CAJf-WoRc+q+yJvwbqtcN5bU-NwYfXumwU5uVgavN6yFpCwH7iQ@mail.gmail.com \
    --to=corwin@bru.st \
    --cc=b.riefenstahl@turtle-trading.net \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.
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).