On Mon, Dec 15, 2025 at 4:24 PM Mark Wielaard <[email protected]> wrote:
> Hi Jason, > > On Mon, Dec 15, 2025 at 02:10:31PM +0800, Jason Merrill wrote: > > On Mon, Dec 15, 2025 at 6:10 AM Mark Wielaard <[email protected]> wrote: > > > On Thu, Dec 11, 2025 at 07:27:15PM +0000, Sam James via Overseers > wrote: > > > > Can we please require that a Bugzilla account is created during the > > > > process for commit access approval by overseers (BZ lets admins > create > > > > accounts, this should be easy) > > > > > > Yes, we could do that. Either automated, by hand or by sending email > > > on account creation to gcc-bugzilla-account-request. > > > > > > > or we add it as a manual step like updating MAINTAINERS? > > > > > > There will always be a manual step like that because the bugzilla > > > account needs to be activated by resetting the password. > > > > > > Question is if we should also do this for all existing accounts that > > > don't have a corresponding bugzilla account. Some people just use the > > > email address in the MAINTAINERS file. > > > > I'd expect that all email addresses in MAINTAINERS should have a bugzilla > > account. And all @gcc.gnu.org accounts as well. > > Do you really mean both a personal and a gcc.gnu.org account? I > suspect (but haven't checked yet) that most people use either one or > the other. > Hmm, personally I only actually use my @gcc.gnu.org account but also have a @redhat.com account and people can CC either one. Perhaps if I only had the @gcc.gnu.org account it would cut down on the frequency of getting email to both addresses for the same bug. But might be confusing to people trying to CC the address I use in commits. > Incidentally, I seem to have an unneeded account for > > [email protected], can we remove that? > > Merged into [email protected] (it only had two bugs associated with it). > > Cheers, > > Mark > >
