Skip to content

Trademark restrictions? #53287

Closed
Closed

Description

@g4jc

Want to fix this bug? There are instructions below.


This github repository does not contain a trademark file, and I am curious if https://www.rust-lang.org/en-US/legal.html 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.

Activity

  1. nagisa commented on Aug 12, 2018

    @nagisa
    Member

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

  2. g4jc commented on Aug 20, 2018

    @g4jc
    Author

    Just received a response. It seems a TRADEMARK.md 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).

    regards,
    Niko

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

  3. added
    A-docsArea: Documentation for any part of the project, including the compiler, standard library, and tools
    on Aug 21, 2018
  4. added
    P-lowLow priority
    and removed
    P-lowLow priority
    on Dec 27, 2018
  5. added
    E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
    E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
    on Apr 3, 2019
  6. steveklabnik commented on Apr 3, 2019

    @steveklabnik
    Contributor

    I've tagged this issue as E-easy and E-mentor. To close this bug, we should add a new section to https://github.com/rust-lang/rust/blob/master/README.md that mentions that there are trademarks on the rust name and logo, and link to https://www.rust-lang.org/policies/media-guide.

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

  7. agnxy commented on Apr 6, 2019

    @agnxy
    Contributor

    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.

  8. added a commit that references this issue on Apr 15, 2019
    b13291f
  9. irelativism commented on Jan 21, 2022

    @irelativism

    Any news regarding this ^
    Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.P-mediumMedium priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions