Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen via Gdb <gdb@sourceware.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
	Dhruv Chawla <dhruvc@nvidia.com>
Cc: Sam James <sam@gentoo.org>,
	Andrew Pinski <andrew.pinski@oss.qualcomm.com>,
	gcc@gcc.gnu.org, gdb@sourceware.org, binutils@sourceware.org,
	libc-alpha@sourceware.org
Subject: Re: bugzilla keyword for beginner issues to work on
Date: Tue, 30 Sep 2025 08:22:08 -0300	[thread overview]
Message-ID: <bc6aa5db-1964-4d2c-be86-d9892385da55@redhat.com> (raw)
In-Reply-To: <CAH6eHdTeGcY=mwUBh_TYeJLAhEY1ix7mCcgGVK+G5b5MA8-1Bw@mail.gmail.com>

On 9/30/25 6:04 AM, Jonathan Wakely wrote:
> On Tue, 30 Sept 2025 at 09:39, Dhruv Chawla via Gcc <gcc@gcc.gnu.org> wrote:
>> On 30/09/25 13:19, Sam James via Gcc wrote:
>>> External email: Use caution opening links or attachments
>>>
>>>
>>> Andrew Pinski <andrew.pinski@oss.qualcomm.com> writes:
>>>
>>>> Hi all,
>>>>     As talked about during the GNU tools cauldron, the gdb and gcc
>>>> keywords usage here are different but folks mentioned it would be a
>>>> good idea to have the same between the 2 bugzilla instances. Right now
>>>> gcc is easyhack while gdb uses good-first-bug. Both have issues with
>>>> the naming of each.
>>> 'good-first-*' is what people tend to search for in other
>>> projects. Having it aligned (and optimising for new contributors) makes
>>> sense, I think.
>>>
>>>> [...]
>>> sam
>> +1 to this. I feel like "beginner-improvement" and "easyhack" are harder to
>> parse than "good-first-bug" or "good-first-issue" (which LLVM uses FWIW), and
>> it is not immediately obvious to me what either of them mean.
> Yeah, I really don't care that somebody might decide to work on a
> "good first issue" as their second or third issue. It would still a
> good first one for somebody else, it just happens to be that person's
> second or third.
>
> "beginner-improvement" is too long, and I had the same question as
> Florian about who or what is being improved.
>
I am not a fan of easy-hack, and I find good-first-bug mentally longer 
because it is one more word (even if fewer characters). However, I don't 
really mind how wordy it is because bugzilla can autofill the options 
based on the partial typing, so I don't care about wordiness


I like beginner-improvement and I'm fine with good-first-bug. If 
would-be contributors are already searching for one, we should 
definitely standardize on the one that is already searched (or at least 
match the beginning). I'll try to see if I can look up what kernel, QEMU 
and other systems engineering projects use.

-- 
Cheers,
Guinevere Larsen
It/she


  reply	other threads:[~2025-09-30 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 20:07 Andrew Pinski via Gdb
2025-09-30  6:25 ` Luis via Gdb
2025-09-30  8:08   ` Richard Biener via Gdb
2025-09-30 11:46   ` Andrew Pinski via Gdb
2025-09-30 12:08     ` Matt Rice via Gdb
2025-09-30  7:10 ` Florian Weimer via Gdb
2025-09-30  7:49 ` Sam James via Gdb
     [not found]   ` <eb1d3e79-4627-4f66-858b-e1923f9071fe@nvidia.com>
2025-09-30  9:04     ` Jonathan Wakely via Gdb
2025-09-30 11:22       ` Guinevere Larsen via Gdb [this message]
2025-09-30 11:54       ` Andrew Pinski via Gdb
2025-09-30 21:07 ` Jeff Law via Gdb

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=bc6aa5db-1964-4d2c-be86-d9892385da55@redhat.com \
    --to=gdb@sourceware.org \
    --cc=andrew.pinski@oss.qualcomm.com \
    --cc=binutils@sourceware.org \
    --cc=dhruvc@nvidia.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guinevere@redhat.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sam@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