From: Richard Stallman <rms@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: jschmidt4gnu@vodafonemail.de, emacs-tangents@gnu.org,
manuel.uberti@inventati.org
Subject: Re: emacs-devel/debbugs communication (was: New Package for NonGNU-ELPA: clojure-ts-mode)
Date: Mon, 04 Sep 2023 20:29:32 -0400 [thread overview]
Message-ID: <E1qdJwi-00008I-7r@fencepost.gnu.org> (raw)
In-Reply-To: <87wmx7mzcf.fsf@localhost> (message from Ihor Radchenko on Sun, 03 Sep 2023 08:32:16 +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. ]]]
> 1. Maintainers often say "no" to certain things (like code refactoring
> that does not lead to any clear improvement) because they know from
> their extensive experience that some ideas are "non-starters".
> However, they do not elaborate much why one or another thing is not
> acceptable.
> Not elaborating is actually perfectly understandable - it would be
> annoying to repeat the same thing many times and would also waste the
> maintainer's valuable time that could be spent for something more
> productive.
I think I can understand why this feels painful -- but what concretely could
we ask the maintainers to do which would be better overall?
When you say "maintainers", do you mean the Emacs maintainers
(currently Eli, Stefan and I)? Or does it mean the people who develop
whichever file you're proposing a change to?
> 3. Sometimes, replies to certain feature request feel like a show
> stopper not because the feature itself is not acceptable, but because
> the specific implementation is not deemed good.
Would it be halp if the people who respond make an effort to
distinguish between their comment about the the behavior tat could be
changed, and their comments about the specific method of implementing
that change? We might be able to get better at that, since I expect
everyone will agree it is good to do that if one can.
I'll reply to #2 privately.
--
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)
next parent reply other threads:[~2023-09-05 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87il9kksqz.fsf@dfreeman.email>
[not found] ` <83350ncbns.fsf@gnu.org>
[not found] ` <87cyzrjbd8.fsf@dfreeman.email>
[not found] ` <83zg2vav46.fsf@gnu.org>
[not found] ` <87o7j99304.fsf@dfreeman.email>
[not found] ` <CADwFkm=XLwqh1xFxGu7Nci=Z-t3F9vzRHPxwAcoE6h_a6p-WWA@mail.gmail.com>
[not found] ` <97224c4f-fad4-ae01-46c1-5755d97d9a92@gutov.dev>
[not found] ` <CADwFkmn29hGxKpWTEKPXVWcaV9evpg2CEg0GR1j_3_GkPOsUJg@mail.gmail.com>
[not found] ` <c45dffbc-6f7f-6b47-0689-0580268d6656@gutov.dev>
[not found] ` <87fs3ztq38.fsf@localhost>
[not found] ` <87cyz3qwba.fsf@posteo.net>
[not found] ` <8734zztmiz.fsf@localhost>
[not found] ` <87sf7zqs3l.fsf@yahoo.com>
[not found] ` <87il8vs6e7.fsf@localhost>
[not found] ` <87jztbqrc9.fsf@yahoo.com>
[not found] ` <877cpbs5a0.fsf@localhost>
[not found] ` <87fs3zqqgj.fsf@yahoo.com>
[not found] ` <874jkfs4o0.fsf@localhost>
[not found] ` <87y1hroz47.fsf@posteo.net>
[not found] ` <e5418514-5a15-469f-d797-0b9668fc2879@vodafonemail.de>
[not found] ` <E1qcFnL-0008QG-3Q@fencepost.gnu.org>
[not found] ` <87wmx7mzcf.fsf@localhost>
2023-09-05 0:29 ` Richard Stallman [this message]
2023-09-05 1:09 ` emacs-devel/debbugs communication (was: New Package for NonGNU-ELPA: clojure-ts-mode) Emanuel Berg
2023-09-05 4:06 ` Samuel Wales
2023-09-05 13:57 ` Emanuel Berg
2023-09-06 10:04 ` Ihor Radchenko
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=E1qdJwi-00008I-7r@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-tangents@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=manuel.uberti@inventati.org \
--cc=yantar92@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.
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).