public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-dev] A new bugzilla keyword for bug investigation
Date: Sat, 11 Jan 2025 07:53:59 +0100	[thread overview]
Message-ID: <1889643.atdPhlSkOF@fcf> (raw)
In-Reply-To: <CAGfcS_nJ2vOmY=SKfBfwWVZyVUFYeCypn9GkaEzftPjfZdfazg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

On venerdì 10 gennaio 2025 17:12:28 CET Rich Freeman wrote:
> Makes a lot of sense, though I'm not sure if it could cause confusion
> for bug wrangling/etc.  I don't think non-prived bugzilla users could
> add the keyword though, so probably no impact there?
> 
> The bug wranglers might actually like it for marking stuff that can't
> be assigned easily?  In any case, I'm just thinking out loud about
> whether there is anything in the bug wrangling process that needs
> consideration.

Hello Rich,

in my opinion this is not for wranglers but for submitters.

Basically when you file a bug you are saying: "hey there is this error" while there are some 
bugs where there is an ebuild failure and you don't know why and from where it comes.

In case of a bug submitted by a non-privileged user, wrangler will assign to maintainer. 
Then maintainer can decide to set a keyword and asking for help.

In some circumstances it will be similar and/or remembers when guru people set "need-
help" keyword/whiteboard.

Agostino

[-- Attachment #2: Type: text/html, Size: 2345 bytes --]

  parent reply	other threads:[~2025-01-11  6:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  8:17 [gentoo-dev] A new bugzilla keyword for bug investigation Agostino Sarubbo
2025-01-10 16:03 ` Jaco Kroon
2025-01-10 16:12 ` Rich Freeman
2025-01-10 16:34   ` Immolo
2025-01-11  6:53   ` Agostino Sarubbo [this message]
2025-01-18 18:02 ` Sam James
2025-01-19 17:19   ` [gentoo-dev] " Duncan
2025-01-18 19:55 ` [gentoo-dev] " Jonas Stein

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=1889643.atdPhlSkOF@fcf \
    --to=ago@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rich0@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox