-
Notifications
You must be signed in to change notification settings - Fork 83
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
What is today's guidance for naming packages? #355
Comments
Might be worth checking wa.dev for the User accounts can have any number of namespaces to publish packages. |
Okay, so now that I've checked that out, I'm very confused. I was expecting that a site like wa.dev would have a single namespace and would allocate package names first-come-first-served within that namespace, similar to how Since the namespace is just |
@dfoxfranke and I are moving this discussion off this thread since it is particular to |
Where should I discuss everything about Should I open topic on https://github.com/bytecodealliance/registry/discussions? I accidentally created a namespace that I don't need, but I don't know how to delete or rename it. |
@oovm |
If I'm creating a WIT package today, how should I go about choosing a name for it such that it won't conflict with somebody else's name in the future? Is there a warg instance running somewhere that has a namespace allocated to it and whose database won't be purged in the future?
Currently, I'm following the lead of the
wasi
crate and using a package name ofrust:<pkg>
where<pkg>
is the name of a crate I control on crates.io.The text was updated successfully, but these errors were encountered: