Roadmap to 1.0 ? | Inquiry About Active Maintenance and Roadmap

[rjrobinson]

hello jsonapi-resources contributors,

First, I want to say that I think the jsonapi-resources project is great, and I truly appreciate all the work that has gone into it so far. I’m reaching out with a couple of questions and suggestions regarding the project’s current status and future direction:

1. Is there any plan for active maintenance of the project?
   It looks like development has slowed recently, and I’m curious if there are any upcoming updates or fixes planned.

2. Is there a roadmap to reach the 1.0 release?
   It would be helpful to know what the vision is for getting to a stable 1.0 version.

I’d love to offer help where I can, but I feel that some formal organization—such as a structured roadmap and project management—would go a long way toward coordinating efforts and attracting more contributors. I've wanted to dedicate some time to an OSS project for a while, and this is one that I really enjoy.

Would there be any interest in setting up a formal roadmap and managing the project more actively? I believe this could benefit both current contributors and those, like myself, who are eager to assist.

Looking forward to hearing your thoughts!

[lgebhardt]

Last spring I had to slow my work on jsonapi-resources for reasons I won't go into here. I do hope to pickup that work back up, though I expect it may not be until the new year that I can give it some serious development time again.

I think setting up a roadmap is an excellent idea. First thing I should do is to document the goals for the current changes I have in progress. I will find some time to do that next week. Then maybe we can develop a roadmap to get that work finished.

@rjrobinson thanks for bringing this up and lighting the🔥 again

[rjrobinson]

Would love to be a part of it ! :)

[stevieing]

Hi

My name is Steve and I work at the Sanger institute in Cambridge, UK. https://www.sanger.ac.uk/

We have been using JSON API resources for many years in a couple of critical applications. Thank-you for what you have created, we are grateful and it has worked well for us.

The problem we are now having is that we needed to fork it to get it work again and we have also monkey patched it in places. We have also noticed that it is not compatible with Rails 8 due to a 422 error returning no status.

I realise that it is not actively maintained and we understand but for business reasons we need to do something about it so we plan to create a fork to fix it and get it up to date.

It would be difficult for us to try and maintain it as an open source project but we want to make sure that anything we do is released back to the open source community but I am not sure at this stage how best to do that.

It will be done in a fully open sourced publicly available repository under our organisation.

Any suggestions gratefully received? bearing in mind that we need to start this work now as it could take us a few months with all of our other priorities to ensure that our critical applications can be updated and continue to work.