docs: update outdated MAINTAINERS.md#7880
docs: update outdated MAINTAINERS.md#7880phip1611 wants to merge 1 commit intocloud-hypervisor:mainfrom
Conversation
TL;DR: The MAINTAINERS.md file is heavily outdated. I've updated MAINTAINERS.md from the (co-)maintainers I regularly see working on CHV and from the information available at https://github.com/orgs/cloud-hypervisor/teams. I also removed two maintainers (@sameo and @michael2012z) as they are not in https://github.com/orgs/cloud-hypervisor/teams respectively inactive for many years (latter case). Further, I think it is helpful to list domain experts for a few selected areas. Signed-off-by: Philipp Schuster <philipp.schuster@cyberus-technology.de> On-behalf-of: SAP philipp.schuster@sap.com
| - **RISC-V** | ||
| - @RuoqingHe | ||
|
|
||
| ### Features & Subsystems |
There was a problem hiding this comment.
It was a little hard to me to
- find the right level of abstraction
- find meaningful sub components worth mentioning
I'm very open for reviewer feedback from the other maintainers!
| - **Main Maintainers** | ||
| - Bo Chen - @likebreath | ||
| - Robert Bradford - @rbradford | ||
| - **Co-Maintainers** |
There was a problem hiding this comment.
By co-maintainers, I refer to everyone that can close PRs, move issues, etc.
likebreath
left a comment
There was a problem hiding this comment.
@phip1611 Thanks for bringing this up. These are important topics to discuss.
I like the idea of identifying domain experts. To make this actionable and integrated into our workflow, I'd suggest we formalize these as entries in a proper CODEOWNERS file that maps experts to the actual code modules and file paths they own. This way, GitHub will automatically request reviews from the right people, and the expertise mapping stays close to the code it describes.
To have proper maintainer list changes, we need to address the gaps in our governance model first. Today, our governance documentation (community/README.md) defines how contributors become maintainers, but is missing on how maintainers transition to emeritus/inactive status. Also, the overall design of developer likely needs to be revisited.
As for next step, I started an issue for discussing governance model and let's follow-up on this topic there: cloud-hypervisor/community#8. Once that's in place, we can revisit the maintainer list changes proposed here.
Can you please open a separate PR to define domain experts as CODEOWNERS entries mapped to specific code paths? We can iterate it with the community together.
|
I'm going to draft this as I think we're not really moving forward with this at the moment? |
TL;DR: The MAINTAINERS.md file is heavily outdated.
I've updated MAINTAINERS.md from the (co-)maintainers I regularly see working on CHV and from the information available at https://github.com/orgs/cloud-hypervisor/teams.
I also removed two maintainers (@sameo and @michael2012z) as they are not in https://github.com/orgs/cloud-hypervisor/teams respectively inactive for many years (latter case).
Further, I think it is helpful to list domain experts for a few selected areas. I'm very open and welcome everyone to join the discussion how this can be handled in a fair and inclusive way, helpful for everyone.
Other tasks