Requiring a BZ account as part of commit access process

[Jason Merrill]

On Mon, Dec 15, 2025 at 6:10 AM Mark Wielaard <mark@klomp.org> wrote:

> Hi Sam,
>
> On Thu, Dec 11, 2025 at 07:27:15PM +0000, Sam James via Overseers wrote:
> > Fairly often, I find that new contributors with commit access don't have
> > a Bugzilla account and hence can't be CC'd on any regressions.
> >
> > Even worse, sometimes this is even the case for actual port maintainers
> > too.
> >
> > 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.

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

Jason