Skip to content

Is this project abandoned? No PR's merged or versions released in nearly a year! #452

@JeffLuckett

Description

@JeffLuckett

I've had my eye on this project since it was announced back in '18. I work on a large JSON API that uses ActiveModelSerializers, and we've been "stuck" on the 0.8 version of the gem ever since that project killed the 0.9 version. We know we've got work to do to get current, and I have long considered swapping it out for fast_jsonapi, since it's so much faster and we've got work to do anyway.

I've just recently begun a side project, and had hoped to use this library for my serialization. It's a good fit for that project, and would give me the familiarity with the Gem to decide whether I want to bring it into my employer's API as the AMS replacement. However, I've noticed the lack of activity here ... no PR's merged since last March, many open (and even more closed) PR's with no attention from the maintainers, and that gives me pause.

Now I've also noticed that some community members have created a fork (https://github.com/fast-jsonapi/fast_jsonapi) and are actively working on it since October given the sudden radio silence here. However, since they can't publish releases to RubyGems, you are required to install via Github. I don't mind that for my side project, but would be reluctant to do such for my employer's project.

Is it the intention of Netflix and the maintainers to allow this project to die on the vine? Might you possibly instead hand over the reins of the "official" repo to these new maintainers so that new releases can be posted to RubyGems, and developers can have the confidence to include this promising library in their projects?

Please reach out to the folks at https://github.com/fast-jsonapi/fast_jsonapi and figure out the best path forward. If Netflix doesn't currently have the resources to maintain this gem, perhaps you could give the maintainers of the fork Collaborator status here and allow them to merge their fork back in and continue to develop the "official" library?

If it's not possible to give them commit rights in this Repo, how about just shutting this project down, and redirecting people to the fork, allow them to "unfork" and become the canonical repo. This is a great project for those of us who are trying to develop performant JSON API's, please don't let it die.

Edit: I realize this has been raised here #433, but with no official response, I thought it a good idea for a new issue to be opened at the "top of the list" to hopefully garner a response.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions