Skip to content

Instantly share code, notes, and snippets.

@est31
Last active Apr 14, 2022
Embed
What would you like to do?

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 if you wish access or have any questions. Thank you!

@attackgoat
Copy link

attackgoat commented Apr 13, 2022

@est31 I've got a crate that might be interested in the pak name you have reserved. The "pak" format is a custom file type generally used in games and another library I wrote includes a largely feature-complete implementation for baking and reading these files.

I'm happy with the quality of the code, although it is not completely 1.0 yet and doesn't have superb documentation. It does have lots of examples and useful documentation comments:
https://github.com/attackgoat/screen-13/tree/master/src/pak

I think this crate meets your criteria in these ways:

  1. The pak name suits my project which reads/writes .pak files, which are commonly proprietary.
  2. The "pak"-portion of the existing crate is approximately 90% feature complete and brings numerous capabilities together for users: compression, expressive asset trees common in commercial games, mesh optimization, PBR, scenes, animations, bitmaps, fonts.
  3. I have maintained the existing crate, including this functionality, for over two years with a steady and documented plan - I intend to grow this repository further using a new name.
  4. The pak code is fully RIIR and even uses .toml to store human-readable asset files. The larger project it currently sits within is another Rust-centric project.
  5. The project has reached a point of stability where I hope to see iterative improvements in API, standards conformance, documentation, etc, rather than much base functionality.

@est31
Copy link
Author

est31 commented Apr 14, 2022

@attackgoat invite sent!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment