From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id kOfDLLBG3GjiORoAWB0awg (envelope-from ) for ; Tue, 30 Sep 2025 17:08:00 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=xtaGoMpV; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id A4C131E0B6; Tue, 30 Sep 2025 17:08:00 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED, RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id E4EB61E04C for ; Tue, 30 Sep 2025 17:07:59 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 66EE23857823 for ; Tue, 30 Sep 2025 21:07:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 66EE23857823 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1759266479; bh=dZsa1xLblu+yoqFhCaM3E2P6fyHojUahS0as5v9Tl8w=; h=Date:Subject:To:Cc:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=xtaGoMpVJYg2InBlk1EjSHHdJLGljcmDCabIFG2kgnLMAaiZmcyxdqjPQNsesyJQs 6XRVruCmQDC4ef5YHdF8Ydy+TGydee/mLag0NmnraomgW6tH4tTONWjzNXDvzlfih+ e37db2HkjIVQq3scaqTLrzCeptkYhH6YwMhYwj7g= Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) by sourceware.org (Postfix) with ESMTPS id 283243857B91 for ; Tue, 30 Sep 2025 21:07:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 283243857B91 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 283243857B91 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1759266425; cv=none; b=XJlASLcagyqRv4DbyEPkl7LZd6p9/ebhjcuSpzigmVj9FBz11kxecNuv9yCiIWL8Y5zOGvRJK5qjO76E/zlRROWFT18SWRgKls70ZuRGP2YUPkHTSvbqDG86d1pXWIUkf41idxdLcoycSAkj3QLQh6f6AZhIznn/vHsU8KoGoXc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1759266425; c=relaxed/simple; bh=RI2Z3VG/3BDp3KVBH83DeQmk/Q6qhEPcl+eQAbvx7eQ=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=An6/E4/RXtfcO4GWYxmvn0b4/j2HHm4HS40lO+8efHK9xC3p2fypq0/QBi3SvT2knQa2irhsVlqUbHU7UkPQtr1EAuozpF26ikuOHp2glzrU5CFLGPadIJ5fsMjrosX0Pz4v42dk9zWSSg5krUonHMtSB5iBsQNXz0xhB1tg7ZI= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 283243857B91 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-71d603acc23so63124157b3.1 for ; Tue, 30 Sep 2025 14:07:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759266424; x=1759871224; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=dZsa1xLblu+yoqFhCaM3E2P6fyHojUahS0as5v9Tl8w=; b=K2Lw6A1uLYf+MbkEBTvyy/HI8MxmXkDYDZe68/Ldtkn19to5yU/74G1efSQskb58GX wvZYMAvYQfxmz7NVdCbbXQL3Q6VaSGFaEgwTaWoYvob5MP2RViY+x1sCACo/eTw5vvti f1j91XFNhrNDNOD482nI+q7Q+aHpvEA1s57i1l5FvLTG0n4WIU4evZPoYdsU3wC1tzxa LbHBUMXV3ZOzKJ0ASvSCEHm2zSQTEc0IVwgpNbsPyaYm/O0maHZgYYX3uvajJNeQSiGs AYYAWEPAVZK2FtMZzlrdLxZwSvsOtTIWK2C/CZqaEOBBys2NDktfxEKjNhjmysWae1sj i/Rg== X-Forwarded-Encrypted: i=1; AJvYcCVrmUjLcwaGNnDkEi28cYvi8Tt7t6+rjjTYgPIeURbwLIfdS4QEzPaaZr4JVoWuUumQ5Pg=@sourceware.org X-Gm-Message-State: AOJu0YyKqKpoxkVlZC0SReFOl6fpYmisqtAHeS23+MEJvACrBi8Uld8X exyk3fFPYz9dCqdwcbFO6fZoIAGjdBfwiN0j9kmiTVk/x9LU7VZgs3jzccKf920zw2o= X-Gm-Gg: ASbGncs8BEljyuzl4NizGusSzA7LsbY4Ob96WmWSbQ0kO85J4+3q58bBVsLKc272ZHO xEVEmTP5SJWH5z3zt8uAF+mrViV1ArHTD4zvl1y/a4wROeZmyqUh2aJACn5aWmwZesnX1jmQF6u fwECvzCv+z+/GsMvflYRKUBUPZB39ZkQAWt25g8M8hixmM1GKfzofPJSE+AacP9wgvicQjVhqD5 IvXSMkfQT0oEzAjjIvmuimQwvv6tqa5tcj0ybJMqvLNT44xxJwbzcWko3XrvxPRA6pOYb2BzezT VVwHwnUWFkuKvXRrEztjUEPIIrEjTarZzDbYGtDmC16j/sUkWIElqXV+b+eZ3hd/4uY4BOz68n3 7TWTxUm49nyoDOhORbMoJtQOGT9oEHVLStuE4puUnmxbGE9+4+uo= X-Google-Smtp-Source: AGHT+IED3hDGnOAgelEmlb7fn+ps3C++aTl3yWZU5t3F7R+jn/IukmLCjn+/o3CglZr8WK6abhiJKw== X-Received: by 2002:a05:690c:6909:b0:76b:dd1:15f with SMTP id 00721157ae682-77f6f2e6dfbmr18339857b3.23.1759266423715; Tue, 30 Sep 2025 14:07:03 -0700 (PDT) Received: from [172.31.0.38] ([136.38.201.137]) by smtp.gmail.com with ESMTPSA id 00721157ae682-765c62a0261sm39842857b3.39.2025.09.30.14.07.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 Sep 2025 14:07:03 -0700 (PDT) Message-ID: <0ef5e545-ec01-4fdc-99ca-28dd30577e6f@gmail.com> Date: Tue, 30 Sep 2025 15:07:02 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: bugzilla keyword for beginner issues to work on To: Andrew Pinski , gcc@gcc.gnu.org, gdb@sourceware.org, binutils@sourceware.org, libc-alpha@sourceware.org Cc: guinevere@redhat.com References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jeff Law via Gdb Reply-To: Jeff Law Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On 9/29/25 2:07 PM, Andrew Pinski wrote: > 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. > So I was thinking of a good name and came up with beginner-improvement . > > I know this is all bikeshedding but in this case since the 2 projects > right now use different naming we have a good chance to come up with a > good name in the first place. > beginner-improvement has a few advantages, first it is about being a > beginner to the project. How long someone can be a beginner is up to > them; it does not need to be their first issue solving. And the idea > of an issue being easy is also left behind; some of them might not > actually be "easy" but a beginner can still solve it. > Plus in many cases it is not exactly a bug but rather than an > improvement that needs to be done so this new name removes that side > of things. > > > So in summary, beginner-improvement is my proposal for the new keyword. I'm not going to bikeshed on the name :-) But I would suggest we generally indicate why we're adding the tag to any given bug. For example I might see a bug reported against the SH which I think may be painful to fix on the SH due to characteristics of its architecture, but the bug may still show up on say RISC-V with a clear path to fixing on that ISA. One might argue I should create another bug (and sometimes I have done that). But I wouldn't be surprised if we found that over time ideas to fix on one ISA may be relevant to approaches taken on others and the like. So I'm in general agreement on finding a consistent way to tag these things and would really like those of us who scour BZ to record thoughts if we think some of these are junior engineer applicable (and to be clear, I'm certainly guilty of adding a personal tag without indicating why I added that personal tag for educational BZs). jeff