unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: Richard Stallman <rms@gnu.org>
Subject: Re: Plan for inquiries about Emacs changes
Date: Tue, 26 May 2020 08:37:35 +0200	[thread overview]
Message-ID: <4eb0d4ed-cab9-9f12-c258-242edc3a02bd@online.de> (raw)
In-Reply-To: <E1jd4u1-0003BK-D4@fencepost.gnu.org>


On 25.05.20 06:39, Richard Stallman wrote:
> [[[ 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. ]]]
>
> Here's the method I propose for inquiries (we used to call them "polls")
> about users' views about possible changes in well-known behaviors.
> Any comments or suggestions?
>
>
> * Make a file for the replies to go into.
>
> * Make a mailing address which drops all mail into the file.
>
> * Write a inquiry statement which describes the proposed change in
> sufficient detail that people can judge it, what kind of information
> we seek, and where to email the response.  Include a deadline for
> replies at least 6 weeks in the future.
>
> If possible, we should tell users how to select various behaviors, so
> that they can state their opinions based on comparing actual
> experiences.
>
> End the inquiry statement with the following text.
>
>      We do not seek "votes", but rather understanding.  If you are for
>      the change, please explain why.  Would it help you directly?  If
>      so, in what scenarios?  How often, and how strongly, would it
>      benefit you?  What would the benefit be?
>
>      Or is it that you think it will improve Emacs, or speed Emacs
>      development, by helping other users?  How so?
>
>      Please distinguish between what you know and what you predict.
>
>      Likewise, if you are against the change, please explain why.
>      Would it inconvenience you directly?  If so, in what scenarios?
>      How often, and how strongly, would it inconvenience you?  What
>      would the inconvenience be?
>
>      Or is it that you think it will harm Emacs or Emacs development by
>      inconveniencing others?  How so?
>
>      We invite you also to propose alterations in the proposed change that
>      you think would improve it -- saying in what scenario that would be an
>      improvement, and how so, etc.
>
>      Please post the URL of this page in forums where it is appropriate,
>      and resend it to Emacs users and mailing lists where you know people
>      will be glad to receive it.
>
> It is crucial to urge people repeatedly to explain their positions
> because there is a strong tendency for people not to bother.
>
> * Put the inquiry statement in a web page under gnu.org/software/emacs.
>
> * Mail the inquiry statement info-gnu-emacs, help-gnu-emacs and
> emacs-tangents, with the URL of the web page _and_ the full text
> of the inquiry statement.
>
> Also post a note referring to the web page on reddit.com/r/emacs, and
> any other suitable places.  Mail the URL to Sacha Chua
> <sacha@sachachua.com>.
>
> * Wait until at least two weeks after the deadline, then study and
> record the responses.  Note down all interesting comments, since they
> are the most important information in the responses.
>
> * Do count how many people support each position that people support,
> but it would be a mistake to make the actual decision based simply on
> counting.  A given change can affect one user very often, and affect
> another user only rarely, but they could both state a "strong
> preference".
>
> * We are not compelled to choose between "make that change" and "no
> change".  The best outcome of the inquiry is that the responses show
> us how to design a way to please almost all users, almost all the
> time, and not displease any user very much.
>

What about implementing in a way Python language did:

https://www.python.org/dev/peps

Thanks,

Andreas





      parent reply	other threads:[~2020-05-26  6:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  4:39 Plan for inquiries about Emacs changes Richard Stallman
2020-05-25 10:47 ` Bastien
2020-05-25 13:41 ` Dmitry Gutov
2020-05-26  0:44   ` Tim Cross
2020-05-27  3:06     ` Richard Stallman
2020-05-27  7:09       ` Tim Cross
2020-05-26  4:16   ` Richard Stallman
2020-05-26  6:37 ` Andreas Röhler [this message]

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=4eb0d4ed-cab9-9f12-c258-242edc3a02bd@online.de \
    --to=andreas.roehler@online.de \
    --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).