unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Glenn Morris <rgm@gnu.org>
Cc: Bastien <bzg@gnu.org>, Stefan Kangas <stefankangas@gmail.com>,
	41373@debbugs.gnu.org, Richard Stallman <rms@gnu.org>,
	dgutov@yandex.ru
Subject: bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages
Date: Mon, 01 Jun 2020 13:31:29 -0700	[thread overview]
Message-ID: <87blm2a5pa.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <kny2p6r2b4.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 01 Jun 2020 15:52:47 -0400")


On 06/01/20 15:52 PM, Glenn Morris wrote:
> Eric Abrahamsen wrote:
>
>> 5. Adds a "Package:" pseudo-header
>
> That is not the right thing to do.
> A debbugs.gnu.org package is not the same thing as an elpa.gnu.org package. [1]
> The valid debbugs.gnu.org packages are listed at
> https://debbugs.gnu.org/Packages.html
> Trying to use one not listed there will result in the mail going to the
> help-debbugs list.
>
> Separately, you should add an "X-Debbugs-CC" pseudo-header, because it
> seems some mail clients don't allow arbitrary (real) X- mail headers.

Thanks for this. You'd mentioned a pseudo-header in your previous
message, and all I could see defined was "Package" and "Version", so I
assumed you meant Package; my mistake.

> I hope this is at most restricted to elpa.gnu.org packages.
> There are already thousands of open Emacs bug reports.
> If reports for melpa packages start getting funnelled into the same
> system, it will make it harder than it already is to find relevant reports.

Good point. You could also argue that, by putting their packages on
Melpa, these authors have already implicitly hinted that they'd rather
not interact with the Emacs organization/infrastructure.

> (Also IMO this doesn't actually fix the issue from this bug report.
> Each elpa.gnu.org package should still be defining where it wants its
> bug reports to go to. This may be the maintainer address, github issue,
> or whatever.)

While I was succumbing to mission-creep this afternoon, I thought of the
same thing: an "Issues-to" package header. This would also give package
authors an explicit mechanism to opt out of debbugs.

> [1] With some effort, someone could in principle automatically create an
> elpa-X package on debbugs for every package X on elpa.gnu.org.

Dunno about this. I started with this idea from the point of view of an
(ELPA) package maintainer. At this point, I'm happy to just implement
whatever everyone agrees makes the most sense.

Eric





  reply	other threads:[~2020-06-01 20:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  2:14 bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages Stefan Kangas
2020-05-18 18:04 ` Glenn Morris
2020-05-18 18:07 ` Eli Zaretskii
2020-05-19  0:20   ` Stefan Kangas
2020-05-18 18:12 ` Dmitry Gutov
2020-05-19  0:15   ` Stefan Kangas
2020-05-20  3:54     ` Richard Stallman
2020-05-20  5:30       ` Eric Abrahamsen
2020-05-25  9:04         ` Bastien
2020-05-25 15:39           ` Eric Abrahamsen
2020-05-25 17:09             ` Glenn Morris
2020-05-25 17:49               ` Eric Abrahamsen
2020-06-01  6:32             ` Bastien
2020-06-01 18:29               ` Eric Abrahamsen
2020-06-01 18:41                 ` Eli Zaretskii
2020-06-01 19:25                   ` Eric Abrahamsen
2020-06-01 19:38                     ` Eli Zaretskii
2020-06-01 20:06                       ` Eric Abrahamsen
2020-06-01 19:52                 ` Glenn Morris
2020-06-01 20:31                   ` Eric Abrahamsen [this message]
2020-05-25 11:51       ` Dmitry Gutov

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=87blm2a5pa.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=41373@debbugs.gnu.org \
    --cc=bzg@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=rgm@gnu.org \
    --cc=rms@gnu.org \
    --cc=stefankangas@gmail.com \
    /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).