-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Janitorial] Please add MAINTAINERS.md #5026
Comments
@prometheus-community/helm-charts-maintainers |
I guess the CODEOWNERS file needs to be replicated and adjusted as requested. |
My thought exactly. I also checked https://github.com/prometheus/prometheus/blob/main/.github/CODEOWNERS and it doesn't have half of the maintainers that are on the https://github.com/prometheus/prometheus/blob/main/MAINTAINERS.md file. These files are bound to be out of sync. Maybe we should automate this to make sure it doesn't happen? |
There's a lot of people in CODEOWNERS; I don't have enough context if that means "full" maintainer or not. If it's equivalent, we can also symlink and be done with it. Autmation and syncing is a good idea, indeed |
@RichiH Unlike other community repositories, this is a multi-project repository. It contains multiple distinct projects (i.e., Helm charts) with different responsibilities. However, there is one exception: there are well-defined admins who are responsible for the entire repository. My question to you: What is expected? Maintainers for each component or maintainers for the whole repository? |
Created #5083 |
Is your feature request related to a problem ?
I'm going through all of prometheus-community/ and adding an issue to create a MAINTAINERS.md where it's missing.
Ideally model it on https://github.com/prometheus/prometheus/blob/main/MAINTAINERS.md with a split between general mantainers and subsystem maintainers if applicable.
Thanks,
Richard
Describe the solution you'd like.
.
Describe alternatives you've considered.
.
Additional context.
No response
The text was updated successfully, but these errors were encountered: