@stereobooster I'd be interested in co-maintaining. You can email me at info at ovio.org

Looks dead sadly :'(

With @ericboucher, we are exploring ways of supporting devs and maintainers in situations like these: a package you rely on stops being maintained but many people still seem to have an interest in using it, and possibly contributing, like here.

The approach we are considering would be to fork the repo, merge all relevant PRs from the main one, and essentially provide a "managed fork" while this repo is "dead". We would happily grant access to our fork to contributors so as to allow easy functional improvements, while we do the housekeeping, bugfixing, security, etc... And if/when the maintainers of this repo come back, we can merge everything back here.

The goal is to provide continuity, a sort of "plan B" that's easy to switch to without having to vendorize code or rely on your own fork-with-my-bugfix. This would be a paid service for organisations that need to have some assurance that their dependencies will not become ghosts. But the result would obviously be available under the same conditions as the original repo to anyone.

We are maintainers of opensource packages ourselves, so we understand the challenges involved. Our goal is not to bypass maintainers, but rather be a support for when life gets in the way of supporting their creations.

Happy to hear your thoughts! @sarink @FrancoisSoler

Here's hoping someone can take over this lovely project.