-
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
[all] added MAINTAINERS.md #5083
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: David Calvert <[email protected]>
A automation would this would be pretty. Guessing the real name could be fetched via GH API. |
Co-authored-by: Jan-Otto Kröpke <[email protected]> Signed-off-by: David Calvert <[email protected]>
True, but we don't add maintainers very often, and not all names are present in GitHub. |
Could you bump the python version in the CI in a separate PR? At least, I head merge permissions to fix that. |
Merged ✔️ |
On A semi related note, how does one ask for being a maintainer? I would like to offer a hand if I could based on previous contribs |
@DrFaust92 Awesome! You should open an issue and PR(s) like #3431. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like a script to keep this file and CODEOWNERS
in sync. One of them should be a source of truth.
Not sure if it's worth it since we don't add maintainers very often, and several chart maintainers don't include their names in their GitHub profiles. We could consider the following options:
Nothing ideal, but we could pick one to have something at least. cc @SuperQ |
tbh. since CODEOWNERS are just generated from Chart.yaml, the Chart.yaml are the source of truth here. + admins. We can start simple. Omit the full name and just add the GitHub handle should be sufficient. |
This should do most of the work:
We could change the way we use |
I like the script. About the full name: in times of GDPR and data economy, the full name of each maintainer shouldn't be mandatory. From maintainer info perspective, the GitHub handle + mail is fully sufficient. |
We don't require it as a policy, but we make it an option for contact formatting of our MAINTAINERS files. People can choose whatever name field they want.
|
Ok, to summarize the proposal from SuperQ:
# Chart.yaml
apiVersion: 2
# ...
maintainers:
- name: The maintainers name # (required for each maintainer) - free text
email: The maintainers email # will be not changed
url: A URL for the maintainer # link to GitHub profile.
While it looks a bit over-engineered first, it giving individual maintainers the possibility the add they correct name. Thats a benefit for this eco system. |
What this PR does / why we need it
Here's a proposal for
MAINTAINERS.md
as asked in #5026.Just kept GitHub handles or forename when I didn't manage to find the full name (maybe it's on purpose):
We can adapt if needed.
cc @RichiH
Which issue this PR fixes
Special notes for your reviewer
Checklist
[prometheus-couchdb-exporter]
)