[SUPPORT NOTICE] #568
Description
Hi all,
It has been a while since we were active on the repo, and people started reaching out even outside github looking for answers re support status of the project.
Since our company joined the contributor pool, we cleaned up backlog a bit and improved a few things. However, this being a json ser library, there is not much variety in what you can do. In addition, re-writing the library core to allow smoother maintenance and extra features that are not available in the current version has not received enough support both inside and outside the contributor circle. Finally, properly maintaining the repo with this many users requires a lot of careful consideration for each PR - or risk breaking stuff and making many people unhappy, but we lacked numbers to make qualified decisions re releases. Taking all this into account, and the fact that core functionality will work for years as-is, we gradually stepped away from active maintenance and stopped responding to issues/PRs. Finally, we don't have full access needed to maintain the repo CI pipelines, and the OG author has understandably moved on to other projects, even though he still finds time to responded when needed, I think this project is no longer in a centre of his attention.
What does this mean for the repo support-wise? Mainly that right now we can't explain to people who employ us and ourselves, why active maintenance is needed here. Thus, we are not spending time on it. This leads to:
- Issues piling up
- PR's not reviewed
- Library code not tested and updated for latest Python versions (3.13, 3.14)
- CI not maintained
If you are willing to actively maintain and contribute on a level this repo needs, please reach out to the OG author and request collaborator access.