-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Additional chart maintainers #21
Comments
Aah.. gotcha @scottrigby I have a kafka-exporter chart as well. I will donate to the community group and continue to maintain here. Really awesome what you are doing here. |
@gkarthiks sounds great! |
As explained prometheus-community/community#28 (comment), I am open to help maintain some charts if help is needed |
I could Co maintain the prometheus chart. Did a bunch of pull requests there already. |
@monotek Message me please on Kubernetes Community Slack workspace - Miro Hadzhiev. |
@scottrigby @brancz @vsliouniaev @bismarck @gianrubio |
@Xtigyro IMO that would be helpful since @gianrubio has stepped back largely, and if I understood correctly @vsliouniaev and @bismarck work together, so sharing the load would probably be nice. However, the current maintainers of each chart should decide on new maintainers for that chart (as long as they're responsive – i.e., the chart hasn't been abandoned. In this case they have been active recently, so we should wait for them to reply) 🙂 |
If somebody else is needed for blackbox-exporter chart i've could jump in too. |
When introducing CODEOWNERS we will have an issue with charts which only have one maintainers. If that maintainer make a change then he is not able to approve it. Repository admins would need to use their "superpower" to override the required review and can merge it. That might be ok for the start, but I would suggest that we try to add at least a second maintainer there. Affected charts are:
Solved:
Would be great if we could find volunteers here or even better if the chart maintainers could try to motivate people who already contributed to the chart to become maintainer. |
Happy to help out on the |
I would like to help with:
For charts/prometheus-postgres-exporter, I need you guys help to become one of OWNERs. For charts/prometheus-redis-exporter, I will PR to see what @acondrat say. |
Adding myself as an additional maintainer for /cc @timm088 @scottrigby |
I am updating the table above so that we keep track of which charts only have one maintainer. As most of us doing this in there spare time and there are vacations and other times where one can not be as active it can't harm to hove more than two maintainers. |
anyone likes to co maintain the prometheus-mysql-exporter chart? or at least would approve my pr :D |
@scottrigby , I worked on druid exporter and donated the helm chart to the community as well. PR is already in the review process and I would like to maintain some other charts as well. |
I'd also like to volunteer to maintain the |
@iamabhishek-dubey The list above shows which charts need more maintainers. If you are interested in one of those juts reach out to their maintainers and create a PR to add youself. |
📣 update: I edited the description with clear steps to follow. We'll keep the summary and current status of this issue up to date there. Thanks everyone! |
Adding myself as an additional maintainer for charts/prometheus-rabbitmq-exporter |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Part-of: #21 Signed-off-by: Torsten Walter <mail@torstenwalter.de>
@iamabhishek-dubey did you already create a PR for that? |
Yes here is the link #282 |
Part-of: #21 Signed-off-by: Torsten Walter <mail@torstenwalter.de>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
…community#275) Part-of: prometheus-community#21 Signed-off-by: Torsten Walter <mail@torstenwalter.de> Signed-off-by: Oleksandr Pylypenko <lex.pilipenko@gmail.com>
This issue is being automatically closed due to inactivity. |
initialisation du chart shiny
EDIT: Wrong issue. Wanted 1656. |
[kube-state-metrics] sync upstream update
Problem
Good summary from @torstenwalter #21 (comment):
Solution
Also from #21 (comment):
We have arrived at a process:
Additional maintainer processes should be discussed in a separate issue, and documented in the PROCESSES file
Current status
Affected charts since issue was opened:
Original issue
The text was updated successfully, but these errors were encountered: