all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 20697@debbugs.gnu.org
Subject: bug#20697: 25.0.50; Mention `M-x report-emacs-bug' on splash screen
Date: Sat, 28 Sep 2019 15:44:58 +0200	[thread overview]
Message-ID: <CADwFkm=cB+KKH4-5F7-9t9ctgo5yXtbxSsTSYzM27Cmwqo-vOg@mail.gmail.com> (raw)
In-Reply-To: <4496bd9e-58ee-45b5-967d-3402ce4999bd@default>

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

Drew Adams <drew.adams@oracle.com> writes:

> > > So I'd "waste" a few extra chars to spell out that
> > > invitation explicitly.  Something like this:
> > >
> > >  "How to report bugs and suggest or contribute possible improvements"
> >
> > I find that line a bit too packed with information to be easily
> > parsed.  I think that the concern Lars has pointed out is valid here:
> > the about screen is already very dense.
>
> Then get rid of some other parts of the link text or
> other parts of the too-dense screen.  Don't get rid
> of the part about suggesting improvements.
>
> This bug report is especially about explicitly
> inviting enhancement suggestions/wishes.  That needs
> to be on top, up-front, in link text - not relegated
> to some text at the link target.
[...]
> > I came up with the attached tentative patch that adds a paragraph to
> > "Contributing" manual page, attached here for discussion.
> >
> > But thinking about this a bit more, I can't decide if it's a good idea
> > to encourage this or not.  There is a risk that we get too many low
> > quality suggestions that we will waste a lot of time handling.
>
> I couldn't disagree more with such fear/hesitation.

I largely agree with what you're saying; thanks for spelling it out.

I see two options to move forward here:

1. Add a new item (or reformulate an old one) on the splash screen.
2. Add something to the "Contributing" page about feature suggestions.

I'm not too enthusiastic about option 1, but I've re-attached my patch
which tries to do 2.  (They are not mutually exclusive.)

Any other opinions, please?

Best regards,
Stefan Kangas

[-- Attachment #2: 0001-Document-feature-requests-in-the-Emacs-manual.patch --]
[-- Type: text/x-patch, Size: 1328 bytes --]

From 1a445133c47c2fa596fa5bdebe150991fde9ee6f Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefankangas@gmail.com>
Date: Sat, 14 Sep 2019 13:27:10 +0200
Subject: [PATCH] Document feature requests in the Emacs manual

* doc/emacs/trouble.texi (Contributing): Document feature
requests.  (Bug20697)
---
 doc/emacs/trouble.texi | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index 13d3e8475c..f0f9af20b8 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -1299,6 +1299,19 @@ Contributing
 @end ifhtml
 You can ask for suggested projects or suggest your own ideas.
 
+If you have a feature request or a suggestion for how to improve
+Emacs, the best place to send it is to
+@ifnothtml
+@email{bug-gnu-emacs.org}
+@end ifnothtml
+@ifhtml
+@url{https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs, bug-gnu-emacs}
+@end ifhtml
+.  Please explain in clear language exactly what change you would like
+to see, and why and how you think it would improve Emacs.  If your
+suggestion is accepted, this will increase its chances of attracting
+interest from one of many volunteer Emacs developers.
+
 If you have already written an improvement, please tell us about it.  If
 you have not yet started work, it is useful to contact
 @ifnothtml
-- 
2.20.1


  reply	other threads:[~2019-09-28 13:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-30 14:42 bug#20697: 25.0.50; Mention `M-x report-emacs-bug' on splash screen Drew Adams
2016-04-30 19:33 ` Lars Ingebrigtsen
2019-08-21  0:41 ` Stefan Kangas
2019-08-21  1:59   ` Drew Adams
2019-08-21 20:02   ` Lars Ingebrigtsen
2019-08-21 21:02     ` Stefan Kangas
2019-08-21 21:27       ` Drew Adams
2019-09-13 19:39         ` Stefan Kangas
2019-09-13 20:13           ` Drew Adams
2019-09-14 12:01             ` Stefan Kangas
2019-09-14 15:54               ` Drew Adams
2019-09-28 13:44                 ` Stefan Kangas [this message]
2019-09-28 13:49                   ` Stefan Kangas
2019-09-29  0:42                   ` Drew Adams
2020-01-16  2:06                   ` Stefan Kangas
2020-01-16 14:49                     ` Eli Zaretskii
2020-01-16 14:55                       ` Stefan Kangas
2020-01-16 15:16                         ` Eli Zaretskii
2020-01-16 20:36                           ` Stefan Kangas
2019-08-21 21:38       ` Lars Ingebrigtsen
2019-09-13 19:29         ` Stefan Kangas
2019-09-14  6:41           ` Eli Zaretskii
2019-09-14 12:06             ` Stefan Kangas
2019-09-14 12:11           ` Lars Ingebrigtsen
2019-09-28 13:39             ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=cB+KKH4-5F7-9t9ctgo5yXtbxSsTSYzM27Cmwqo-vOg@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=20697@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.