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: Fri, 13 Sep 2019 13:13:57 -0700 (PDT) [thread overview]
Message-ID: <5e1c6ad4-5c01-4989-bbcf-7e398ba9ede6@default> (raw)
In-Reply-To: <CADwFkmk6-0Yme+HmrtCvyNKB-oeVbgQpkxv0y6PuJLktMVLJvg@mail.gmail.com>
> There are many ways to contribute to Emacs:
> • find and report bugs; *Note Bugs::.
>
> So I think this is already a good landing page for both bugs and
> contributions.
Yes.
> > [Mentioning also enhancement requests was my input
> > for this bug thread.]
>
> Do you have any ideas for how to better emphasize enhancement
> requests? Should it be a separate bullet point on the "Contribute"
> page perhaps?
My suggestion is to put it explicitly in the text/link
that then leads you to the doc section that covers all
of this.
Although "contribute improvements" covers suggesting
enhancements, I think the former suggests more
substantial contribution than just asking for or
suggesting a possible enhancement - something wished.
I think it's important for users to see, up front,
an invitation to make even minor or undeveloped, even
possibly infeasible or not-well-thought-through
suggestions.
If that invitation is found only after following some
"contribute" link to doc that covers everything,
including full-blown patches, then its effect on
inviting superficial suggestions can be lost.
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"
> > But in that case, the more lightweight feedback, #1,
> > should be separated and up front, so users wanting
> > to report a bug or suggest an enhancement need not
> > find themselves immediately in the depths of how to
> > contribute in a deeper way.
>
> I think that it's fine that users can click the link on the top of the
> page to reach (info "(emacs) Bugs"). It's separate enough, and early
> enough, that users can easily click on it and ignore the rest of the
> page, in my opinion.
See above. Separate enough and early enough, perhaps.
But it doesn't explicitly invite suggestions, even
blue-sky suggestions. That invitation is what I think
is missing up front.
> > We want (IMO) to encourage lots of users to provide
> > relatively easy feedback, beyond also wanting some
> > users to get more deeply involved. We don't want
> > people to get the impression that lightweight
> > suggestions are not possible or encouraged, and that
> > a heavy commitment is the only encouraged participation.
>
> I absolutely agree.
Thanks for working on this. The patch looks good to
me, though I'd prefer to also see what I mention above.
next prev parent reply other threads:[~2019-09-13 20:13 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 [this message]
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
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=5e1c6ad4-5c01-4989-bbcf-7e398ba9ede6@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 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.