Requiring a BZ account as part of commit access process

[Mark Wielaard]

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 <mark@klomp.org> 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.

> Incidentally, I seem to have an unneeded account for
> jason@prospero.cambridge.redhat.com, can we remove that?

Merged into jason@gcc.gnu.org (it only had two bugs associated with it).

Cheers,

Mark