Inherit maintenance of this crate?

[MarijnS95]

Hey @arcnmx! It looks like this crate hasn't seen any merges or publishes in the past 3 years (barring some sidetracking in v0.2.x branches that never made it to master nor crates.io). We've started building on top of it and adding a few features to it, but would like to expand that a little bit further into safe Rust.

For that to make sense globally, I'd love for those efforts to apply to the current repository and published crates.io crates rather than living in a niche hidden fork somewhere.

Are you still up for maintaining this crate and accepting pull requests, or would you be open to transition ownership of the repository and crate so that we can continue in your legacy? At this point we are mostly interested in DRS.

Usually when I inherit a crate, I'll tend to focus on the following:

• Add CI to ensure the crate builds and is lint-free at all times;
• Extend (code/crate) documentation and READMEs;
• Resolve existing issues or shortcomings;
• Update/regenerate bindings with the latest versions;
• Use newer Rust features for improved safety on top of these C APIs;
• Last but not least, contribute new features and API that we are using.

See for example nvngx-rs. This crate is still maintained by its original author but I've started helping out with the above listed points.

Thanks for this crate, and thanks for considering!