From: Adam Porter <adam@alphapapa.net>
To: philipk@posteo.net
Cc: daniel@dpettersson.net, dmitry@gutov.dev, eliz@gnu.org,
emacs-devel@gnu.org, joaotavora@gmail.com, john@yates-sheets.org,
krister.schuchardt@gmail.com
Subject: Re: [ELPA] New package: dape
Date: Sat, 4 Nov 2023 10:06:17 -0500 [thread overview]
Message-ID: <5bc9bc3f-f2f3-48b2-9b91-8c7033fa37f6@alphapapa.net> (raw)
In-Reply-To: <87o7g9wq8f.fsf@posteo.net>
Hello Philip,
> In addition to this, there have on multiple occasions been authors
> who have been open and appreciative of names being suggested here on
> the mailing list, especially if they don't have a strong opinion wrt
> the name to begin with. It seems unjustified to claim that
> mentioning the topic will necessarily scare people away.
Please don't misunderstand me. I am not claiming that it will
necessarily scare people away. I am claiming that the bikeshedding can
be discouraging to authors who consider submitting to GNU ELPA. This
should not be surprising, as I don't think anyone would enjoy having to
endure a lengthy thread second-guessing their decision, which usually
seems to proceed with the assumption that the author hasn't already
spent time making it deliberately.
As well, I can go through the list of packages on GNU ELPA and find tens
of them whose names don't bear any apparent relation to their purpose or
description. Should that stop us from seeking better names? Of course
not. But at what point do we admit that Shakespeare was right?
> (I didn't want to bring this up initially, but one of the reasons I
> mentioned changing the name is due to the small edit distance between
> "dape" and "r*pe", that I can imagine would make other people more
> uncomfortable).
Well, let's see, in QWERTY order: tape, ape, gape, jape, cape, vape,
nape... I think that's not a practical reason to reject an author's
name, and not a very polite association to make with the name he chose.
next prev parent reply other threads:[~2023-11-04 15:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:35 [ELPA] New package: dape Daniel Pettersson
2023-10-13 12:24 ` Philip Kaludercic
2023-10-14 12:28 ` Daniel Pettersson
2023-10-14 14:54 ` Philip Kaludercic
2023-10-15 13:50 ` James Thomas
2023-10-15 14:12 ` Philip Kaludercic
2023-10-15 17:24 ` John Yates
2023-10-18 21:54 ` Daniel Pettersson
2023-10-19 2:08 ` Adam Porter
2023-10-19 10:52 ` Krister Schuchardt
2023-10-19 11:06 ` Dmitry Gutov
2023-10-20 14:53 ` John Yates
2023-11-01 19:13 ` Dmitry Gutov
2023-11-02 14:42 ` João Távora
2023-11-04 9:51 ` Daniel Pettersson
2023-11-04 10:00 ` Philip Kaludercic
2023-11-23 6:10 ` Philip Kaludercic
2023-12-05 8:41 ` Philip Kaludercic
2023-12-05 9:18 ` João Távora
2023-12-05 10:59 ` Philip Kaludercic
2023-12-05 11:29 ` João Távora
2023-12-06 3:57 ` Richard Stallman
2023-12-06 10:09 ` Daniel Pettersson
2023-12-06 12:30 ` Eli Zaretskii
2023-12-06 12:56 ` João Távora
2023-12-06 13:08 ` Eli Zaretskii
2023-12-06 13:38 ` João Távora
2023-12-06 17:00 ` Eli Zaretskii
2023-12-06 23:03 ` João Távora
2023-12-06 23:55 ` Daniel Pettersson
2023-12-07 7:13 ` Eli Zaretskii
2023-11-04 13:46 ` Adam Porter
2023-11-04 14:01 ` Eli Zaretskii
2023-11-04 14:24 ` Philip Kaludercic
2023-11-04 15:06 ` Adam Porter [this message]
2023-11-04 15:27 ` Philip Kaludercic
2023-11-04 14:53 ` Adam Porter
2023-11-04 15:14 ` Eli Zaretskii
2023-11-04 19:15 ` Adam Porter
2023-11-04 23:21 ` João Távora
2023-11-07 10:19 ` Daniel Pettersson
2023-11-07 10:40 ` João Távora
2023-11-08 8:31 ` Daniel Pettersson
2023-10-19 15:12 ` Philip Kaludercic
2023-10-19 17:50 ` Björn Bidar
2023-11-01 16:50 ` Philip Kaludercic
2023-10-15 13:55 ` Mauro Aranda
2023-10-17 20:39 ` Daniel Pettersson
2023-10-20 5:49 ` Milan Glacier
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=5bc9bc3f-f2f3-48b2-9b91-8c7033fa37f6@alphapapa.net \
--to=adam@alphapapa.net \
--cc=daniel@dpettersson.net \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=john@yates-sheets.org \
--cc=krister.schuchardt@gmail.com \
--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).