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 16:05:19 -0700 [thread overview]
Message-ID: <CAFHYt57a8FBmHeHpV2sgMoqForgfackwqWfN3+og3F8rP6jwpQ@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:
>
> AFAIK, we are not able to change the current Debbugs tags
Alternatively, we could also change the bug "owner". Quoting from the
documentation, "The owner of a bug claims responsibility for fixing
it." [1]
In the context of Guix, teams would have to make sure they are not
offended when unrelated parties set or modify the bug owner. An
assignment to someone else can come across as patronizing—especially
in a ping-pong type situation—but I think that Guix contributors as a
whole have a collective morale that is strong enough to discount any
perceived slights.
With a monorepo, it's all kind of left-pocket/right-pocket, anyway.
Kind regards
Felix
[1] https://elpa.gnu.org/packages/doc/debbugs-ug.html#Mail-Command-Index
prev parent reply other threads:[~2023-04-28 23:06 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.
2023-05-01 15:38 ` Maxim Cournoyer
2023-04-28 23:05 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
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=CAFHYt57a8FBmHeHpV2sgMoqForgfackwqWfN3+og3F8rP6jwpQ@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).