RESERVED.md

I've reserved some crate names on crates.io for future use.

I'm willing to turn over any crate names to interested parties under some criteria:

1. The name actually suits the project. If the crate name is banana and your project is about apples, its off-topic use. Name it apples instead!
2. Your crate is a significant contribution to the ecosystem and not just e.g. some test project or something you never intend to finish.
3. You intend to maintain the crate.
4. There is a RIIR-only policy to help pure-Rust implementations getting great names. This means: no crate names for API bindings of any non-rust codebases, rust-idiomatic or otherwise. There are three exceptions to this rule: OS/driver API bindings, projects that are getting rewritten part by part and where some parts are already rewritten (like ring), and if you are the original creator of the non-Rust codebase and you want to provide the bindings yourself, you'll get the name as well.
5. You actually have it almost done so that its usable by other people. With "usable" I mean that the crate is functional and can be integrated into software fulfilling the task its meant for.

Please get in touch with me via this gist if you wish access or have any questions. Thank you!

@attackgoat invite sent!

@est31 Hi, I'd be interested in taking wave for a no-std no-alloc gesture recognition library intended for usage with low-resolution TOF-sensors. The code is here: https://github.com/flxzt/wave and it would be ready for an initial 0.1 release.

@flxzt invite sent.

@est31 @jkelleyrtp I see at some point you planned to use the "Dirac" crate on Dioxus, is that still the case? I have a dirac notation macro that would fit the naming very well https://github.com/felipetavares/dirac