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: Fri, 13 Sep 2019 21:39:40 +0200	[thread overview]
Message-ID: <CADwFkmk6-0Yme+HmrtCvyNKB-oeVbgQpkxv0y6PuJLktMVLJvg@mail.gmail.com> (raw)
In-Reply-To: <5d8f820c-4029-45cf-8fd7-b1fc44f8e6e3@default>

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

> > > So this basically adds another line and links directly to the Bugs
> > info
> > > page.  Hm.  Would it be possible to instead just change the line
> > >
> > > Contributing    How to contribute improvements to Emacs
> > >
> > > to something like the following?  That link already links to the bug
> > > reporting page...
> > >
> > > Contributing    How to report bugs and contribute improvements
> >
> > I had missed that, but you're absolutely correct and I agree that its
> > a better solution.
>
> I saw that "How to contribute..." but I thought/think
> its destination is to the doc section about contributing.
>
> If so, that's not quite the same thing.
>
> It would be OK to have a single link that points to
> something that covered both (1) `report-emacs-bug',
> mentioning that that's also for enhancement requests,
> and (2) how to contribute in a deeper way: GIT, patches
> etc.

(info "(emacs) Contributing") already says on the top of the page:

   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.

> [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?

> 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.

> 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.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-09-13 19:39 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 [this message]
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
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=CADwFkmk6-0Yme+HmrtCvyNKB-oeVbgQpkxv0y6PuJLktMVLJvg@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.