On 26/06/2026 13:03, Richard Earnshaw via Sourceware Forge wrote: > Hi gcc-patches mailing list, > Richard Earnshaw via Sourceware Forge > <[email protected]> has requested that the > following forgejo pull request > be published on the mailing list. > > Created on: 2026-05-29 15:13:48+00:00 > Latest update: 2026-06-26 12:03:19+00:00 > Changes: 6 changed files, 6855 additions, 11 deletions > Head revision: rearnsha/gcc-TEST ref MAINT-yaml commit > 65fb98fc5dca5221231fc85b6c7cfdfe14686f03 > Base revision: gcc/gcc-TEST ref trunk commit > 4c05f6e10358f379a6da28151b832509f0a3f485 r17-1915-g4c05f6e10358f3 > Merge base: 4c05f6e10358f379a6da28151b832509f0a3f485 > Full diff url: https://forge.sourceware.org/gcc/gcc-TEST/pulls/163.diff > Discussion: https://forge.sourceware.org/gcc/gcc-TEST/pulls/163 > Requested Reviewers: > > RFD: convert MAINTAINERS data to YAML. > > For the forge to be able to notify maintainers efficiently when a > merge request is submitted, I need to be able to automate assigning > reviewers as well as just labels. The information needed for this is > largely in the MAINTAINERS file, but not in a format that is readily > machine readable: it can be scraped, but it's a bit of an ad-hoc > process and not something I'd want to maintain in the long term. > > To mitigate that, and to make it possible to augment this information > with additional details, I've been experimenting with converting the > raw data into YAML and then having a script build the official > MAINTAINERS file form that. The results can be seen in the following > patch. The results so far are /almost/ identical with only a limited > set of differences, some of which can probably be resolved later on. > > - the free-form entries saying All XXX maintainers have been expanded > into explicit lists; I really don't think it helps much to have yet > another level of indirection to deal with here and in particular it > complicates regenerating the MAINTAINERS file as the template rules > would need to be handled specifically. > > - I've found some small sort-order differences; these could be easily > rectified, but I think the sort order I'm using here > (case-independent sort) is preferable to a case-dependent one: Lac > should be sorted before LaD. It would be better, I think to tweak > check-MAINTAINERS.py to prefer this new order, but that file becomes > redundant if this code goes in. > > - I might have over-merged the entries for Feng Wang. That's easily > fixable in the MAINTAINERS.yml data, but is an example of the kind > of issue that I've faced with creating the machine-readable data > from the raw files. > > Finally, the name for Naveen Gowda has changed in the DCO list. The > email address used appears elsewhere in the MAINTAINERS file with a > slightly different name. This could be fixed with a small extension > to the YAML data (the DCO entry could take an optional name), if it > really matters. > > One additional field that I've added is a marker for what I consider > to be inactive accounts. The forge is likely to be more aggressive in > emailing developers and I don't want it to be forever mailing people > who have long ceased to contribute to the project. For now I've > scraped the GCC commit logs and posts to [email protected] and > [email protected]; anybody who has not contributed to one of those > sources in the last two years has been marked as inactive. The > generator script has an option (-a) to build a version of the > MAINTAINERS file with inactive users removed: we have a lot of retired > devs! > > Changes since V1: > - Added a schema and additional checks to validate the yaml data > - Added a simple script to create a Write-After entry > - Split the edits to the base conversion of the original > MAINTAINERS data into separate commits. This is just to > make things easier in the case I need to re-run the conversion > and will be collapsed before the final commit > ---
And here's a link to the updates to WWWDOCs. Claudio's bot isn't set up for that yet, so it's not posted here. https://forge.sourceware.org/gcc/gcc-wwwdocs-TEST/pulls/1 R.
