2 ms·
Hey folks! So, yes, the intention of this policy is basically to prevent people from confusion around forking the language itself. It would be very bad if, for
by steveklabnik 7y ago
Hey folks!
So, yes, the intention of this policy is basically to prevent people from confusion around forking the language itself. It would be very bad if, for example, a distro would strip out the borrow checker and still called the language “Rust.”
Distributions do make some patches to Rust, and still call it Rust. The team is fine with this. Nobody has explicitly asked to do so either. The only trademark inquiries we get are around things like “can I sell this tshirt”, honestly.
Now, there is one thing of interest here. Mozilla does own these trademarks. I often comment here about how Mozilla does not run Rust governance, and that’s true, but this is the one single way in which they do have some leverage. However, I can’t imagine a world in which they do something against the will of the team. When discussing the idea for a foundation, a place for these trademarks is often one of the largest pros of doing such a thing.
I will note that a lot of people have brought up Iceweasel; this issue resolved itself long ago and distros like Debian ship Firefox now.
- tedunangst 7y agoIs it very bad that https://github.com/thepowersgang/mrustc https://github.com/thepowersgang/mrustc calls itself a Rust compiler?
- steveklabnik 7y agoNo, because it is very clear that it's not an actual Rust compiler yet, and so is extremely unlikely to generate said confusion.
- Argorak 7y agoFrom the Rust Media guide, under "Uses that do not require explicit approval": * Stating accurately that software is written in the Rust programming language, that it is compatible with the Rust programming language, or that it contains the Rust programming language, is allowed. In those cases, you may use the Rust trademarks to indicate this, without prior approval. This is true both for non-commercial and commercial uses. I would call a compiler that compiles Rust, but does not name itself "rustc" falling under that explicit approval. (Full disclosure: I'm part of the Rust community and core team and often handle trademark decisions)