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

Trademark restrictions? #53287

g4jc opened this issue Aug 12, 2018 · 4 comments · Fixed by #59748

Trademark restrictions? #53287

g4jc opened this issue Aug 12, 2018 · 4 comments · Fixed by #59748


Copy link

@g4jc g4jc commented Aug 12, 2018

Want to fix this bug? There are instructions below.

This github repository does not contain a trademark file, and I am curious if still applies, as it would seem.

Uses that require explicit approval

**Distributing a modified version of the Rust programming language or the Cargo package manager and calling it Rust or Cargo requires explicit, written permission from the Rust core team.** We will usually allow these uses as long as the modifications are (1) relatively small and (2) very clearly communicated to end-users.

Selling t-shirts, hats, and other artwork or merchandise requires explicit, written permission from the Rust core team. We will usually allow these uses as long as (1) it is clearly communicated that the merchandise is not in any way an official part of the Rust project and (2) it is clearly communicated whether profits benefit the Rust project.

Using the Rust trademarks within another trademark requires written permission from the Rust core team except as described above.

Debian and some other distributions are applying patches against the Rust language and Cargo package. I assume this qualifies as something which requires explicit approval?

If so, removing or restricting packages from Cargo would also be considered a modification. e.g. some distributions may wish to block access to Cargo downloads that are not in compliance with license standards.

Just wanted to get some clarification on this as it is not mentioned here in the repo and some folks seems to think that because there is no trademark "here" that rust-lang can be distributed with modifications without approval. I believe the only way such modifications would be allowed unrestricted, is if "rust" was not used at all in the package and it was clearly defined as a rebranded fork that is not affiliated with the official package - Otherwise the trademark policy is still enforced.


This comment has been minimized.

Copy link

@nagisa nagisa commented Aug 12, 2018

This question should be asked at the email address linked on the Legal page rather than here.


This comment has been minimized.

Copy link

@g4jc g4jc commented Aug 20, 2018

Just received a response. It seems a may be useful to direct people to the appropriate information from github.

You are correct that we intended the trademark to apply when
distributing a package or other binary called "Rust" -- and in
particular that if modifications are made, then we would expect a
trademark request outlining the sorts of changes being made (as the
policy notes though, we are inclined to accept such a request).


This issue can be closed once trademark notification is included or mentioned on
Thank you.


This comment has been minimized.

Copy link

@steveklabnik steveklabnik commented Apr 3, 2019

I've tagged this issue as E-easy and E-mentor. To close this bug, we should add a new section to that mentions that there are trademarks on the rust name and logo, and link to

If you want to fix this bug and need any help, please let me know, and I'm happy to assist!


This comment has been minimized.

Copy link

@agnxy agnxy commented Apr 6, 2019

Hi @steveklabnik
I'd like to work on this and opened #59748 to add a section about trademarks. But I'm not sure whether I made appropriate wording. Could you please help to review? Thanks a lot.

Centril added a commit to Centril/rust that referenced this issue Apr 15, 2019
Add summary and reference to Rust trademark guide

Fix rust-lang#53287
cc @steveklabnik
@bors bors closed this in #59748 Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.