[RFC] MAINTAINERS: require a BZ account field

[Richard Sandiford]

Sam James via Gcc <gcc@gcc.gnu.org> writes:
> Hi!
>
> This comes up in #gcc on IRC every so often, so finally
> writing an RFC.
>
> What?
> ---
>
> I propose that MAINTAINERS be modified to be of the form,
> adding an extra field for their GCC/sourceware account:
>   <Name>        <Email>                <Email on gcc.gnu.org BZ / sourceware account>
>   Joe Bloggs    joebloggs@example.com  jbloggs@gcc.gnu.org
>
> Further, that the field must not be blank (-> must have a BZ account;
> there were/are some without at all)!
>
> Why?
> ---
>
> 1) This is tied to whether or not people should use their committer email
> on Bugzilla or a personal email. A lot of people don't seem to use their
> committer email (-> no permissions) and end up not closing bugs, so
> pinskia (and often myself these days) end up doing it for them.
>
> 2) It's standard practice to wish to CC the committer of a bisect result
> - or to CC someone who you know wrote patches on a subject area. Doing
> this on Bugzilla is challenging when there's no map between committer
> <-> BZ account.
>
> Specifically, there are folks who have git committer+author as
> joebloggs@example.com (or maybe even cooldude@example.com) where the
> local part of the address has *no relation* to their GCC/sw account,
> so finding who to CC is difficult without e.g. trawling through gcc-cvs
> mails or asking overseers for help.
>
> Summary
> ---
>
> TL;DR: The proposal is:
>
> 1) MAINTAINERS should list a field containing either the gcc.gnu.org
> email in full, or their gcc username (bikeshedding semi-welcome);
>
> 2) It should become a requirement that to be in MAINTAINERS, one must
> possess a Bugzilla account (ideally using their gcc.gnu.org email).

How about the attached as a compromise?  (gzipped as a poor protection
against scraping.)

It adds the gcc.gnu.org/bugzilla account name, without the @gcc.gnu.org,
as a middle column to the Write After Approval section.  I think this
makes it clear that the email specified in the last column should be
used for communication.

It's awkward to add a new column to the area maintainer section, so this
version also reverses the policy of removing entries from Write After
Approval if they appear in a more specific section.

I've also committed heresy and replaced the tabs with spaces.

The account names are taken from the gcc-cvs archives (thanks to
Andrew for the hint to look there).  I've tried to make the process
relatively conservative, in the hope of avoiding false positives or
collisions.  A handful of entries were derived manually.  There were
four that I couldn't find easily (search for " - ").

James Norris had an entry without an email address.  I've left that
line alone.

If this is OK, I'll need to update check-MAINTAINERS.py.

Thanks,
Richard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: MAINTAINERS.gz
Type: application/gzip
Size: 17383 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20240704/da31c930/attachment-0001.gz>