@norbu "The Rust Foundation has no desire to engage in petty policing or frivolous lawsuits." Nothing will happen if you register a domain containing "rust" and don't do anything with it. Section 5.3.2 is a general domain name exclusion term that you would find in many trademark policies, including that of Linux, Apache, Java, etc.
@norbu
I am not sure which version you read, but the current version has 4.2.1, which explicitly grants license for using the Rust name for porting and packaging without asking.
It is also false that every blog post about Rust has to include a trademark disclaimer. Most blog posts, even if they use Rust in the title, are considered "nominative use" and is automatically exempted from trademark dispute by trademark laws, overriding this policy.
As I mentioned, Linux has a similar policy, so Arch Linux actually needs to obtain a sublicense, and show the following on its website:
> The Arch Linux name and logo are recognized trademarks. Some rights reserved.
> The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide basis.
@kemuri Well, it seems the board realized that it wasn't that good an idea ... https://blog.rust-lang.org/inside-rust/2023/04/12/trademark-policy-draft-feedback.html
@kemuri there is no guarantee that the Rust Foundation will not do that. Not now maybe, but dinner or later I guess it will happen. And the requirement to put "not endorsed.." on every blog post etc on Rust??? Furthermore, I fear that the policy will prohibit or make it difficult for distributions (Arch, Debian, ..) to repackage and distribute rust packages.
I don't think that this policy serves the community omg any way.