[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Discuss new features/enhancements or large changes for users in emac
From: |
Eli Zaretskii |
Subject: |
Re: Discuss new features/enhancements or large changes for users in emacs-devel |
Date: |
Thu, 05 Dec 2024 08:33:13 +0200 |
> From: Richard Stallman <rms@gnu.org>
> Cc: drew.adams@oracle.com, adam@alphapapa.net, emacs-devel@gnu.org
> Date: Thu, 05 Dec 2024 00:08:07 -0500
>
> > . a discussion could wander into a tangent, in which case TRT is to
> > ask people to make the tangent a separate discussion, instead of
> > moving it to emacs-devel
>
> If the new topic is a tangent to the bug discussion, where that should go
> depends on what it is about.
>
> It might be of little importance to Emacs, in which case maybe it
> ought to move to emacs-tangents. Or it be a suggestion for some
> bigger change in Emacs. That should go to emacs-devel, I think.
When we tell people to make the tangent a separate discussion, it goes
without saying that the separate discussion should have its best place
determined as part of starting it.
> > . we encourage people to submit "feature-request" bug reports (and
> > Emacs recently acquired the "M-x submit-emacs-patch" command for
> > that reason), in which case the bug list _is_ the proper place to
> > discuss that. When the feature is significant and/or affects
> > Emacs or our users in prominent ways, prudence would mandate that
> > we move such general discussions to emacs-devel, but that's a
> > judgment call, not an automatic knee-jerk reaction
>
> Jdgment calls are like this. There is no precise rule that gives a
> perect result every time. That is too much to ask for.
>
> What we can hope for is to recognize when a local change idea
> has wandered into an idea for a change that would affect a lot
> more situations.
Agreed.