Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Name of the crate #21

Closed
neon64 opened this issue Aug 3, 2017 · 7 comments
Closed

Name of the crate #21

neon64 opened this issue Aug 3, 2017 · 7 comments

Comments

@neon64
Copy link

neon64 commented Aug 3, 2017

First off, this isn't exactly an issue per se.

I was looking through my crates on crates.io and discovered I had a crate from 2 years ago named spirv - which I created just to support a hobby project before there were any other SPIR-V libraries in Rust. I haven't maintained it in ages and the code/features/testing/etc are quite obviously inferior to the fantastic work being done in this crate. So basically my question is, since I'm going to mark that as 'abandoned' and suggest that nobody should use it, would another crate (eg: this one) like to take that spirv name?

I realise this is perhaps a dumb question, since changing names on crates.io would force all the users of rspirv to change their code, however I guess I'm just letting you know in case somebody feels that spirv is a 'nicer' or more canonical name to use.

Edit: I guess I'm also looking for rust-lang/rust#41616

@antiagainst
Copy link
Collaborator

antiagainst commented Aug 3, 2017

Hi @neon64, much appreciated your generosity and kindness to transfer the spirv crate name! spirv sounds like a nicer name for the header sub-crate in this repo. However, as you said, it is rather intrusive for the users to change crate names under the current cargo/crate management settings. So I'm just not sure it worth the hassle.

@neon64
Copy link
Author

neon64 commented Aug 4, 2017

Okay no worries.. Well maybe for now I'll just put a clear link to this project suggesting people go use it instead.

@antiagainst
Copy link
Collaborator

Thanks @neon64! :)

@antiagainst
Copy link
Collaborator

Hey @neon64, are you still willing to shift the ownership of the spirv crate to us now? Previously there isn't a need, but now it looks the need does arise: spirv_headers is using the SPIR-V version as the crate version; it has seen a few breakages thus far due to the differences from semver. It might be better to start with a clean slate to push to spirv crate where we can adopt semver from now on. WDYT?

@neon64
Copy link
Author

neon64 commented May 5, 2021

@antiagainst I'd be fine to transfer ownership. Which username(s) should I invite?

@Jasper-Bekkers
Copy link
Collaborator

@Jasper-Bekkers, @kvark and @antiagainst at least I think :-)

@antiagainst
Copy link
Collaborator

Yes. Thanks @neon64!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants