Hi Bjoern! Hope you had a productive PromCon! Did you have a chance to discuss this thread? It'd be nice to figure out how we could collaborate some more, thank you!
On Thursday, September 25, 2025 at 7:18:03 AM UTC+9 Konrad “ktoso” Malawski wrote: > Thanks for the reply, Bjoern! > > Appreciate you putting this on the dev-summit agenda and for sharing the > additional background. > > Would you suggest we continue the thread here? Once you have had some time > at the dev-summit to define the guidance for how to proceed with a > transition under the Prometheus governance, including the GitHub repo > transfer. > > Thanks in advance and talk to you soon then, > Konrad > On Tuesday, September 23, 2025 at 8:20:57 AM UTC+9 Bjoern Rabenstein wrote: > >> On 17.09.25 17:30, Konrad “ktoso” Malawski wrote: >> > >> > We would like to propose swift-prometheus (currently at >> > https://github.com/swift-server/swift-prometheus) as an officially >> > supported client library for you to consider, extending the current >> list ( >> > https://prometheus.io/docs/instrumenting/clientlibs/). >> > >> > The library is being used at scale in production and as far as we know >> > should be fully spec compliant. The project is well maintained, and >> we're >> > committed to it long term as well. >> > >> > We'd love to become part of the Prometheus family, and we're more than >> > happy to fulfill any the technical and non-technical requirements to >> > formally transfer the project to the Prometheus GitHub organization and >> > integrate it into the Prometheus governance structure. >> >> Thanks for all of this. >> >> For starters, I would suggest to add it to the "unofficial" list, by >> opening a PR against >> >> https://github.com/prometheus/docs/blob/main/docs/instrumenting/clientlibs.md >> >> . >> >> (I know that this was already attempted long ago as >> https://github.com/prometheus/docs/pull/2002 . The maintainers of the >> docs repo are a lot behind. Feel free to poke them frequently on a new >> PR (or an updated version of the old PR).) >> >> WRT "official" status: This would mean to move the library into the >> prometheus GH org, which is something we still have to discuss within >> the community (if we want to avoid creating many more repos in that >> org, or if we want to go the exact opposite way and put a lot there, >> maybe including prometheus-community repos, too). A lot of the >> "unofficial" libraries are simply "the" Prometheus instrumentation >> libraries for their language. So the question would be what's the big >> difference in making them "official". (There is certainly the formal >> difference that the prometheus and prometheus-community GH orgs are >> under the Prometheus governance. But that's more a limitation for a >> library that could be maintained independently as well.) >> >> We have a big in-person dev-summit next month. I'll put this question >> on the agenda. Also the not-very-well-maintained state of the docs >> repo... Agologies again. >> >> -- >> Björn Rabenstein >> [PGP-ID] 0x851C3DA17D748D03 >> [email] [email protected] >> > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/prometheus-developers/8c407782-057c-4a91-a114-0d66c39bd381n%40googlegroups.com.
