From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8093D15813A for ; Sat, 11 Jan 2025 06:54:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 20999E089E; Sat, 11 Jan 2025 06:54:05 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 76F75E0899 for ; Sat, 11 Jan 2025 06:54:04 +0000 (UTC) From: Agostino Sarubbo To: gentoo-dev@lists.gentoo.org Cc: Rich Freeman Subject: Re: [gentoo-dev] A new bugzilla keyword for bug investigation Date: Sat, 11 Jan 2025 07:53:59 +0100 Message-ID: <1889643.atdPhlSkOF@fcf> In-Reply-To: References: <2645278.Lt9SDvczpP@fcf> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart46944782.fMDQidcC6G" Content-Transfer-Encoding: 7Bit X-Archives-Salt: 713cabda-0daa-4ded-b476-be17f2666a09 X-Archives-Hash: f29def0c35f9eb7d6ea7be16f68255e7 This is a multi-part message in MIME format. --nextPart46944782.fMDQidcC6G Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On venerd=C3=AC 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? >=20 > 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" whi= le there are some=20 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 t= o maintainer.=20 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 --nextPart46944782.fMDQidcC6G Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

On venerd=C3=AC 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 coul= d

>= ; 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 er= ror" while there are some bugs where there is an ebuild failure and yo= u don't know why and from where it comes.


In case of a bug submitted by a non-privileged user, wrangler will assig= n 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 peop= le set "need-help" keyword/whiteboard.


Agostino

--nextPart46944782.fMDQidcC6G--