-
Notifications
You must be signed in to change notification settings - Fork 3
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
Adopt the Github Exporter to the Prometheus Community #44
Comments
This will need a Prometheus Team sponsor. |
Thanks, good to know - is there an "official" way of going about that? |
I can help transition this if required, though i only have access for another week before i move on from the current project owner. If we want/need to do something then i'd suggest we look to do it sooner rather than later. If needed though i could bring others up to speed. ^ In ref to the current owner |
@Rucknar apologies, I've only just seen this. If it's not too late for you to step in that would be fantastic - work has required far more of my time than expected of late! |
Apologies @proffalken I don't have the time in my last week to actually make changes and manage through, More i have the time to transfer ownership if suitable. I've talked through my colleague though @ivorc who will be able to do this if it's required after i've gone. |
@proffalken I'm happy to support this. @SuperQ — you mentioned the need for a Prometheus Team sponsor. Can you guide us on how to arrange that? |
As detailed in githubexporter/github-exporter#85, the Github Exporter is no longer actively maintained and the previous maintainers are happy for it to be adopted by this community.
Whilst I don't know GO, I am willing to undertake the work required to get the repo to a point where it is building within the Prom Community's CI/CD platform and see where we can take it from there.
The text was updated successfully, but these errors were encountered: