Future of this repo

[siimon]

Hello everyone!

As some of you may have noticed, this project has not been on my radar for quite some time. I created it when Prometheus was relatively new, and I was heavily involved in both open source and the JavaScript community. Additionally, I was younger and didn’t have a family. All of that has changed over time. I no longer work with JavaScript (or TypeScript, for that matter), and I find that I have little free time to program.

That said, I'm open to finding a new home for this repository, where changes can be merged and maintenance can be continued. The question is where to transfer it. What do you think is the best option? @SimenB, are you interested in taking it over, or would it be better to move it to the Prometheus organization?

Thanks!

[jdmarshall]

@siimon thanks for creating this project and running it as long as you have. I don’t see any objections to @SimenB taking over, if they’re up for it.

I have a rather long list of reasons to prefer Prometheus over OpenTelemetry, which is why I’ve been filing so many PRs. It would be a shame if this module didn’t continue on.

Would the Prometheus organization be open to merging this in? And how would they feel about default labels? How would you feel about that?

[jdmarshall]

I'd love to land some of the PRs I have outstanding. Anything I can do to help out here?

[SimenB]

Sorry, missed this issue! I'm happy to take it over (either on my personal account or setting up a GH org), but if the prometheus project is interested in having the project live in their org, that'd be ideal I think (I'd still be happy to help maintain it). Should we ping some folks from there?

[SimenB]

@mcollina suggested a separate org, which also works 👍

[mcollina]

I think a separate org would be better for management.

[zbjornson]

If the Prometheus org is willing to take it, that seems like a better option than an independent organization. We've had numerous cases where we were unsure of what the correct design decisions were. Having help from anyone within Prometheus would have been really useful. It'd also make this an official package instead of a community one.

[SimenB]

Whatever moves us forward seems best. So what about this

1. Move it to my personal account so I have full admin access (mostly so that @siimon doesn't actively have to do anything for step 2 🙂)
   1. I'll add/keep @siimon, @zbjornson and @jdmarshall as admin
2. We reach out to some folks at the prometheus projects asking if they'd be ok with moving the repo into their org
   1. If they say yes, we'll do that
   2. If they say no, we create a new org ourselves

thoughts?

[mcollina]

We could also check if we want to move this to Node.js itself.

[SimenB]

Sure, I'd be ok with that 👍

[mcollina]

I think asking the prometheus folks for having this in their org should be the primary choice.

Happy to. join the team (I already have work to give significant overhead reduction).

[SuperQ]

Hey, Prometheus Team member here.

I would be happy to see this library added to the official Prometheus org. We have done similar adoptions in the past.

The first thing I would need to do is bring this up with the rest of the Prometheus dev team.

[mcollina]

Here is my work: #727.

[jdmarshall]

I'm keen to get my merged PRs into users' hands.

Does @SimenB have npmjs.org privileges to publish releases?

I'm just about down to the bottom of the backlog for the two other projects I maintain. I filed a dragon slaying PR yesterday and that's about the last big ticket item I have on my radar and I'm looking for other things to work on. I'd accept a maintainership if that was the route you want to go.

Alternatively we haven't heard anything back from @SuperQ