-
Notifications
You must be signed in to change notification settings - Fork 10
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
Request for changing the name of WASIX #4
Comments
Hey Till, we have been using the WASIX name for a long time, way before any other project. As a matter of fact, we purchased wasix.org in April 2020 (please see the receipt attached). Code-wise, the first commit of us using the term WASIX was as soon as March 24, 2021 (again, way before any other project existed). https://github.com/wasmerio/wasix/commit/d03508483df61379fb4f1c56ab012b7bb78745ab The wasmerio/wasix repository was open source for a long period of time, but we closed the source about a year ago. In any case, you shall be able to validate what I said once we open-source that repo again. All this is to say that our usage of WASIX predates any other project by a big margin (at least for a few years), as proven by the receipts on this thread, so we will continue using this name. Thanks in any case for bringing this to our attention! |
In your screenshot your repo is set to private - and that project still seems to be private now: wasix-org github organization was created 2023-5-22: The SingleStore-labs/wasix repo shows it was created at 2022-1-13, is public, and is being continually updated: I don't see anything on way way back machine under either domain until now. I don't see any complaints over to singlestore on their use of wasix for the last 16 months. I am only asking to understand, is there something public I am missing here? I just want to understand where folks are coming from and their point of view. |
I've been working on WASIX for over two years https://crates.io/crates/wasix/versions john-sharratt/wasix-libc@93973da Quite proud of what we've done together and it's going to be great for the community. |
I don't think we're talking about the value, just the name. I see stuff back to May of 2022. Thank you for sharing! |
Here are some public facts:
I also even have proof that people belonging to your organizations/alliances were already aware that we were using that name as early as July 2021 (happy to attach any receipts if you want 😉). We have provided all this data out of courtesy, and even then there is still a push to dismiss those facts. So I’m frankly quite surprised. As proven by multiple comments in this thread, Wasmer has been using the WASIX name (both publicly and privately) for more than two years, way before any other project existed, and we will continue using this name. |
Hey all, first off: congratulations on putting this system interface and tooling around it together! I know how much work goes into something like this, even if you can reuse so much existing code.
Unfortunately there is a sizable problem with the name you chose, which I have no doubt is a simple oversight: since early in 2022,
WASIX
has been in use for an open source project by SingleStore Labs, originally developed for their port of cpython to WASI. At one point it was also used by the official cpython distribution.Given that this project is very much in the same space as your system interface, this name collision would be bound to cause a great deal of confusion once you announce more widely.
I'm glad I stumbled upon this before a big announcement could be made, since I know @syrusakbary's very strong stance against using names already taken by other projects in a related space (see e.g. here, here, and here), and hence that he'd certainly agree that continued use of this name would be the wrong thing to do.
(Note: I would have filed this on the wasix-libc repo, but it has issues disabled.)
The text was updated successfully, but these errors were encountered: