From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Greater bug specifics for automatic team assignment
Date: Fri, 28 Apr 2023 10:29:11 -0700 [thread overview]
Message-ID: <CAFHYt56H-SqwVdh3BTtS_HosJxLG4fAN1Bxyt5+Lx8drFiNv=w@mail.gmail.com> (raw)
In-Reply-To: <878rec9i63.fsf@gmail.com>
Hi Simon,
On Fri, Apr 28, 2023 at 10:02 AM Simon Tournier
<zimon.toutoune@gmail.com> wrote:
>
> What do you have in mind?
In my recollection of using Debbugs in Debian, which uses a slightly
different version with more features (for example, a SOAP interface)
than the instance provided by GNU.org, there is a feature called "user
tags." They allow anyone to set arbitrary labels. [1]
Personally, I used regular tags frequently when co-maintaining Lintian
in Debian. They were super helpful when dealing with hundreds of bugs.
I therefore thought user tags could be helpful in Guix, especially for
teams. I may not be alone. [2]
We even have a section about them in the Guix manual, although I
haven't seen them being used much. [3]
Kind regards
Felix
[1] See "usertag", https://elpa.gnu.org/packages/doc/debbugs-ug.html
[2] https://lists.gnu.org/archive/html/help-debbugs/2020-08/msg00000.html
[3] https://guix.gnu.org/manual/devel/en/html_node/Debbugs-Usertags.html
next prev parent reply other threads:[~2023-04-28 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 20:57 Greater bug specifics for automatic team assignment Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-28 14:48 ` Simon Tournier
2023-04-28 17:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-05-01 15:38 ` Maxim Cournoyer
2023-04-28 23:05 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFHYt56H-SqwVdh3BTtS_HosJxLG4fAN1Bxyt5+Lx8drFiNv=w@mail.gmail.com' \
--to=guix-devel@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=zimon.toutoune@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/guix.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).