Maintenance support (offer)

Nobody has claimed this yet.

Hi @indygreg . I read [your blog](https://gregoryszorc.com/blog/2024/03/17/my-shifting-open-source-priorities/). Congrats on all of the life changes. Sounds exciting.

I'd like to offer to take over maintenance for python-zstandard and possibly also PyOxidizer projects.

Like you, I've had some life changes, but my changes have given me more time to support open source projects.

My involvement would be modest - I don't have aspirations to make _any_ major changes to the projects. Instead, I'd be focused on occasionally reviewing PRs and issues, guiding users to explore solutions, and cutting releases as needed to keep the projects from growing stale. I'd leverage the same methodology I use to maintain the hundreds of other projects I maintain in the Python ecosystem. I might step in to make important maintenance changes, but more than likely I'd direct the community to contribute most changes. I'd be careful to maintain the stability and quality that users have come to expect, directing contributors to provide well-engineered solutions with test coverage and to be responsive to unexpected regressions. And I of course would be happy to keep you on as a co-maintainer and be prepared to hand the project back should you wish to re-engage with any of them.

Let me know if that sounds at all interesting and if you have any specific stipulations you'd like to include.

Otherwise, feel free to give me ownership access of the PyPI projects and (optional but preferable) transfer the GitHub repos to the [coherent-oss](/coherent-oss) org, which I've formed to share maintenance on projects.

No source files, tests, or code entry points are named. Read the issue thread and the linked maintenance-priorities post first; the issue is resolved only if the maintainership arrangement and any ownership or repository transfer are explicitly agreed.

Written by the indexing model from the issue text.