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

What is today's guidance for naming packages? #355

Open
dfoxfranke opened this issue May 7, 2024 · 5 comments
Open

What is today's guidance for naming packages? #355

dfoxfranke opened this issue May 7, 2024 · 5 comments

Comments

@dfoxfranke
Copy link

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 of rust:<pkg> where <pkg> is the name of a crate I control on crates.io.

@calvinrp
Copy link

calvinrp commented May 7, 2024

Might be worth checking wa.dev for the Warg namespaces in use and reserving what you would like to use.

User accounts can have any number of namespaces to publish packages.

@dfoxfranke
Copy link
Author

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 crates.io operates. Instead, I created an account there and it handed me a dfoxfranke namespace based on my GitHub login.

Since the namespace is just dfoxfranke and not dfoxfranke.wa.dev or something, does this imply that wa.dev's allocations are intended to be canonical across the whole WASM ecosystem? Does it imply that if you rely on any packages registered with wa.dev, you should rely only on packages registered there? How does this allocation scheme interact with that fact that, e.g., there's a github user named wasi who doesn't have anything to do with WASI?

@calvinrp
Copy link

calvinrp commented May 7, 2024

@dfoxfranke and I are moving this discussion off this thread since it is particular to wa.dev service

@oovm
Copy link

oovm commented May 10, 2024

Where should I discuss everything about wa.dev?

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.

@calvinrp
Copy link

calvinrp commented May 10, 2024

Where should I discuss everything about wa.dev?

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
Best on the Discord link at the bottom of wa.dev. Deleting or renaming is not quite available in UI. Happy to address manually. Feel free to message me directly.

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

3 participants