From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
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 17:42:10 -0700 (PDT) [thread overview]
Message-ID: <f5103221-cf9f-4ca9-a2ba-7637269baa11@default> (raw)
In-Reply-To: <CADwFkm=cB+KKH4-5F7-9t9ctgo5yXtbxSsTSYzM27Cmwqo-vOg@mail.gmail.com>
> 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?
Thanks for reconsidering, and for working on this.
Wrt #1 & #2: Neither is perfect:
#1: People breeze past the splash screen.
(But see below.)
#2: A user needs to have somehow found node
(emacs) `Contributing'. Not obvious for a
newbie (but see below).
Wrt your patch (#2): +1 in favor of it.
You might want to say "attracting interest from
volunteer Emacs developers", instead of "from
one of many" (why one?).
Or maybe - why mention two separate hurdles:
getting your suggestion "accepted" and getting
someone to work on it? Consider just removing
that whole sentence, keeping only the first one,
which invites suggestions that are clear and
that provide a "why".
Wrt #1: People might not notice a mention on
the splash screen, and even if they do they
might not have a clue how to show it again,
apart from restarting Emacs.
But they might well look into the `Help' menu.
The `Help' menu is the most likely place a new
user will look for info about how to contribute
or contact Emacs developers. Even if they know
nothing about Info or how to get to the splash
screen, they will find the `Help' menu.
On the `Help' menu we have `How to Report a
Bug' and `Send Bug Report...'. That's 2 menu
items to help users report bugs.
The `Help' menu also has an `About Emacs' item
that, lo and behold, displays the splash screen,
with its link to node `Contributing'. So for
both contributing and reporting bugs the `Help'
menu is pretty good.
Consider one or both of these possibilities,
in addition to adding your suggested text to
node `Contributing':
* Change `Help' > `Send Bug Report' to `Help'
> `Report Bug or Suggestion'
* Add a `Report Bug or Suggestion' link to
the splash screen
The menu item `Send Bug Report' invokes
`send-emacs-bug-report'. But that's the
same command you use to send an enhancement
request. It would help if the menu item
expressed that. (It would even help if the
command name did so.)
---
BTW, I don't know why the _first_ of the
list of links on the splash page is `Authors'.
I'd suggest moving it later or (better, I
think) just removing it. It would be good to
have `Contributing' as the first link of the
list.
next prev parent reply other threads:[~2019-09-29 0:42 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
2019-09-28 13:49 ` Stefan Kangas
2019-09-29 0:42 ` Drew Adams [this message]
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
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=f5103221-cf9f-4ca9-a2ba-7637269baa11@default \
--to=drew.adams@oracle.com \
--cc=20697@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).