-
Notifications
You must be signed in to change notification settings - Fork 185
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
Migrate to Prometheus Community? #24
Comments
Hi @SuperQ thanks for your interest. I'm not sure sure how much that organization is open to accept repos that has not been well maintained by someone, so I think we need an active maintainer for this project anyway. |
Yes, as one of the Prometheus maintainers, I would be willing to sponsor getting maintenance started. One of the things I was looking at was your prometheus-exporter-harness code. I think that something like that would be really useful for https://github.com/prometheus/common. |
oh that's nice :) Let me prepare to transfer the ownership.
Oh it's interesting to hear heat. I thought most exporter authors are just relying on standard prom modules because its just enough. so when it's ready I'll just ping you and move the ownership, does it works? |
I filed an issue in the community tracker for this. There are two ways to do the move.
Either way, you're welcome to continue to be a maintainer/contributor of the project after the move. |
@SuperQ ok that works. Let me add you as an admin. |
FYI, It turns out it's not possible to make others "admin" on "personal" repos. I will create a group on prometheus-community so it can be moved.
|
@SuperQ I see, thanks for the clarification!
I assume it's not ready yet? I've just tried to transfer the ownership but failed by lack of permission on prometheus-community. |
I sent an invite to join the |
@SuperQ Ugh, sorry it seems that I overlooked the previous invitation. |
Is there any interest in maintaining this exporter? Maybe we could move it to the Prometheus Community repos?
https://github.com/prometheus-community
The text was updated successfully, but these errors were encountered: