[flagged]
I guess it is an abrupt change in trademark enforcement for Rust.
I wouldn't worry about writing on rust, the language. It certainly sucks that the language, the compiler and the foundation share the same name. But it probably sucks for the foundation as well regarding enforcement.
I don't get why people like to put the name "rust" in crate names, unless they write tools that work with the language (linters, auto-formatters), it just feels redundant.
In crate names it is redundant. As a project or domain name it isn't.
Crabby may be the word to use
From Mozilla's trademark policy: If you want to include all or part of a Mozilla trademark in a domain name, you have to receive written permission from Mozilla. People naturally associate domain names with organizations whose names sound similar. Almost any use of a Mozilla trademark in a domain name is likely to confuse consumers, thus running afoul of the overarching requirement that any use of a Mozilla trademark be non-confusing. If you would like to build a Mozilla, Firefox Internet browser or Thunderbird e-mail client promotional site for your region, we encourage you to join an existing official localization project.
From Node Foundation's trademark policy: You need permission to register or use a domain name that contains a Node.js mark in it. Please don’t register a domain that looks or sounds similar to a Node.js or includes a misspelled Node.js mark as that can confuse community users
From Debian's trademark policy: You cannot use Debian trademarks in a domain name, with or without commercial intent.
IANAL and this is not legal advise, but I wouldn't sweat about it. This same thing applies to any other trademark too, be it Debian, Firefox, Nintendo or Coca-Cola.
I've got a couple small things I don't like, but once again, it seems to be right in line with other open source trademark policies. I just had never looked closely at them before
I strongly, STRONGLY, agree with their political stance. However, I find their forcing their politics down people's throats extremely concerning. Keep in mind that you also have to seek approval to use the word Rust (I am not affiliated with the Rust Foundation), which means that they could disallow it merely because they don't like you or what you stand for (which the prior rule shows a tendency to do). Call me crazy, but I fail to see how that's in any way progressive (yes, given even the tolerance paradox) - especially given that the other people and beliefs will be running the Rust Foundation at some point in the future.
This isn't a matter of "keep your politics out of tech," it's a matter of bringing in politics being actually harmful to the community.
Ending gun violence in America is the responsibility of voters and lawmakers, not the Rust Foundation.
So a "Ferris and Firearms" meetup is simply not allowed to occur. That sounds extremely inclusive.
This also implies that organizers would have to go through the effort AND cost (because you are only allowed to collect fees for food and drinks) of doing entry control or a meetup.
>The main focus of the group is discussion of and education about Rust software;
It's a programming language, not a lifestyle brand. Not everything needs to be dragged down into US-centric culture wars. It's good that they don't want to dilute the brand and are keeping it focused on the software. If you want to go to the range with a group there are tons of meetups for that. I don't know why you would want to make one based around a programming language.
- follow local health guidelines
- may attract people wearing fireguns
These breaches of our big CoC are not appreciated and we will spend all of our sparse funding now to drag you to court.
But since the name it's the only thing that is getting in the way with this new (draft) policy, you wouldn't really have to fork the language and the tooling etc. All you have to do is to just use this new made up name in place of rust (and similarly for cargo) and you've achieved independence with a fraction of the cost.
E.g.
Rust -> Crust Cargo -> Embargo
"Hey, here's a quick Crust tutorial: check out this git repo and run: embargo build"
Fork the web page, you cannot just replace Rust with ALTERNATIVE, because ALTERNATIVE is not used at npm, you don't have a Discord community, and you don't have books and videos, and no foundation. All those changes would need to be kept up-to-date.
You could also have a new file type, .altrs, while you still want to be able to use Rust's files. Same goes for tooling, supporting websites such as crates.io: you might want your own, but you also want all the tools to work with the Rust crates. With the new file type, you need people to know how to change their config to treat .altrs files as regular .rs files.
.. though I don't know how much of it would be really necessary if all you want is to not violate their new policy, so it's more of a thought experiment at this point.
Cargo->Corvo
And from there on we have a ton of bird-related puns for naming.
> we invite you to review (..) and share any feedback (...). Your responses will help us ensure the Rust Trademark Policy is useful for all!
I'm bringing attention and visibility to the proposal and hopefully help the foundation receive valuable feedback from more people.
This just diverts attention away from the original project that was posted here.
Are you going to post the same thing under every project written in Rust during the next weeks?
The proposal was very disappointing to me, and it has been on top of my mind when I browsed HN this morning, so when I saw a cool project that -- if some of the sections of the proposal go through -- would violate Rust's Trademark Policy, I thought it'd be acceptable to bring that up (and still think that).
I believe raising awareness to issues with the proposal is productive, and hopefully at least some people here on HN decided to leave feedback in the Rust Foundation's form, so that as little of the non-sensical paragraphs stay in the final document as possible.
It is based on the results of a previous survey: https://old.reddit.com/r/rust/comments/wkv8gv/rust_foundatio.... Looking at where we are now it's safe to assume that not all community feedback was given the same level of care, the (vocal) community is against this, as am I.