GNU bug report logs - #41373
GNU ELPA: Add "reporting bugs" to individual package pages

Previous Next

Full log

Message #35 received at 41373 <at> debbugs.gnu.org (full text, mbox):

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: Bastien <bzg <at> gnu.org>
Cc: dgutov <at> yandex.ru, 41373 <at> debbugs.gnu.org, Richard Stallman <rms <at> gnu.org>,
 Stefan Kangas <stefankangas <at> gmail.com>
Subject: Re: bug#41373: GNU ELPA: Add "reporting bugs" to individual package
 pages
Date: Mon, 25 May 2020 08:39:10 -0700

Bastien <bzg <at> gnu.org> writes:

> Hi Eric,
>
> Eric Abrahamsen <eric <at> ericabrahamsen.net> writes:
>
>> Richard Stallman <rms <at> gnu.org> writes:
>>
>>> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
>>> [[[ whether defending the US Constitution against all enemies,     ]]]
>>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>>
>>> We could have report-emacs-bug ask for which package the bug is in.
>>> The Bug Subject argument could be one of the acceptable package names,
>>> including 'emacs' and whichever ELPA packages have been loaded.  The
>>> user could specify one of those.
>>>
>>> If the definition of a package says where to send bug reports for it,
>>> report-emacs-bug could send each bug to the right place.
>>>
>>> If Bug Subject argument isn't on that list, report-emacs-bug could ask,
>>> "Would you like to specify one of the ELPA packages that have been
>>> loaded?"  But you would not have to do that.  If Bug Subject is unknown,
>>> the message would go to bug-gnu-emacs, as now.
>>
>> Several years ago I cooked up something basic like that. I've attached
>> the patch from that thread, which might serve as the basis for something
>> usable.
>
> I tested your patch and it looks really useful to me.
>
> Two things that come to my mind:
>
> - Package completion could not find "org" as a package: still, a bare
>   emacs -q list Org as a built-in package.  Maybe we can add those to
>   the completion list?

I think in the original discussion the patch went back and forth between
completing on `package-alist' and completing on `features'. The former
didn't offer enough, the latter offered too much.

> - If completion fails, then the bug reporting process is stopped,
>   which may be confusing for users -- when there is no completion,
>   I suggest to fall back on the current report-emacs-bug behavior.

Yes, that's a bug! It shouldn't require a package.

> - I wonder what happens if the "maintainer" email is a mailing list
>   address: this might lead to confusion, with people cross-posting to
>   both bug-gnu-emacs <at> gnu.org and emacs-orgmode <at> gnu.org for example,
>   which would perhaps lead to some more confusion because bugs on
>   bug-gnu-emacs <at> gnu.org are posted to emacs-orgmode <at> gnu.org when they
>   are tagged "org-mode" (if I understand correctly).

If we complete on `features', that's definitely an issue. I think my
solution in that version of the patch simply dropped the issue if the
Maintainer header was emacs-devel, or there was no Maintainer.

> A simple solution for the last issue would be to forbid mailing list
> addresses in the "maintainer" email field.  In the case of org-mode,
> for example, the address could be that of someone in charge of doing
> bug triage, assigning tags to bug-gnu-emacs <at> gnu.org when needed.
>
> In any case, thanks for spending time on this!

My pleasure -- as Dmitry notes, this might not solve the problem that
this thread is about, but I think it's definitely worthwhile on its own.

Eric

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.