xeipuuv/gojsonschema

Volunteering to maintain

mattwelke opened this issue · 12 comments

mattwelke commented

Hi, we've been using this library in production for about 7 months now, with no plans to stop using it. In fact, we're using it more and more. I see a lot of open PRs and issues, and I've also seen a few people step up to volunteer to maintain it. I'd like to volunteer myself. I'm going to ping the others I've seen volunteer too to see if they're still interested. I suggest we use this issue to centralize discussion about maintainership.

@xeipuuv Are you open to adding people as maintainers?

mattwelke commented

People I've noticed volunteer to maintain in the past:

  • @anandsunderraman
  • @lpessoa
  • @johandorland (didn't see a message from you explicitly stating this, but I've noticed you discuss having "to do lists" and I've seen you fork this library and have commits here)
piotrszyma commented

My organisation also started using that on prod with success, so if you'll need any more help I'm also happy to discuss / contribute ;)

pierrecamilleri commented

Same here, we would like to use it in prod and we would be willing to (modestly) contribute.

Surfoo commented

I don't think you can't count on this repository to maintain it, and a fork should be created..

mattfarina commented

This project is a dependency of a bunch of other open source projects so it would be good for it to be maintained.

I've reached out (via email) to the maintainer and have not yet gotten a response.

If there is to be a folk, I would hope a single folk can be created that the larger projects are willing to use.

piotrszyma commented

Hmm if the maintainer no longer wants to contribute then either one of us can create a fork or we can create a separate organisation? WDYT?

anandsunderraman commented

Or should we reach out to github support to see if they can hand over the rights to maintain this repo to the set of folks willing to maintain it.

mattwelke commented

I'm going to take my hat out of the ring. Things got busy, and it's clear there are plenty of others who also want to maintain.

As far as I know, in the open source community, a fork is most appropriate when the original maintainer isn't available. It might seem a bit hostile to ask GitHub to hand over a repo someone else created.

TRiggAtGM commented

I think it would be best to set up an organization and to create a fork there. I think it seems evident that the owner of this repository has no intention of resuming support for it themself as they have not been active on GitHub in over two years (probably got busy, as this is the constant risk of the open source world). I'm a neophyte to this space so I don't feel comfortable taking on those initial steps to start, but I do think it's just going to take someone saying "Okay, it's time someone did the thing"

  • 👍2
decentralgabe commented

also in favor of seeing this maintained. is there a fork yet?

Surfoo commented

Hello there 👋

ok, nobody created a fork of this projet, so I just forked it within a new organization: https://github.com/gojsonschema/gojsonschema.
Let me know here if you want contribute to this fork, and I'll add you as member/whatever. The rest will happen there now.

  • 👍2
mattwelke commented

I agree with the decision to fork to a new org of the same name. I think we've given the creator plenty of time to chime in. It is important that the library is taken into a good direction, community-maintained, for the future. Given that we haven't heard back from @xeipuuv for a while, I hope they're doing okay.

To clarify, at this time, I'm not requesting to be added as maintainer to the new fork.