Rust Language Trademark Policy

Sections:

◦ Not Appearing Official, Affiliated, or Endorsed

◦ The Basics: Referring to Rust/Cargo

◦ Legitimate Source of Official Source Code of the Rust Project and Associated Binaries

◦ Uses That Do Not Require Explicit Approval

◦ Uses That Require Explicit Approval

    About

    The Rust and Cargo names and brands make it possible to say what is officially part of the Rust Project, and what isn’t. So we’re careful about where we allow them to appear. At the same time, we want to allow for as much creative use of these brands as we can. This policy explains how we strike a balance. If you want to use the Rust names or brands, especially in a commercial way, please read this page or feel free to reach out and ask us about it.

     If you have any doubts about whether your intended use of a Rust Trademark requires permission, please contact us.

     This document was derived in part from the Python Software Foundation Trademark Usage Policy.

    Art License

    The Rust and Cargo logos (bitmap and vector) are owned by the Rust Foundation and distributed under the terms of the Creative Commons Attribution license (CC-BY). This is the most permissive Creative Commons license, and allows reuse and modifications for any purpose. The restrictions are that distributors must “give appropriate credit, provide a link to the license, and indicate if changes were made.” Note that use of these logos, and the Rust and Cargo names, is also governed by trademark; our trademark policy is described below.

    The Rust Trademarks

    The Rust programming language is an open source project governed by a Leadership Council, and stewarded by the Rust Foundation, which owns and protects the Rust and Cargo trademarks and logos (the “Rust Trademarks”). This document provides information about use of the Rust Trademarks specific to a programming language and software related to it, as well as examples of common ways people might want to use these trademarks, with explanations as to whether those uses are OK or not or require permission.

     

    The Rust Trademarks include two word marks and two logos:

    Rust language logo
    Rust programming language logo
    Rust Cargo logo
    Cargo logo

    Trademarks are names and designs that tell the world the source of a good or service. Protecting trademarks for an open source project is particularly important. Anyone can change the source code and produce a product from that code, so it’s important that only the original product, or variations that have been approved by the Rust Project, use the trademarks.

    By limiting use of the Rust Trademarks, the Rust Foundation and the Rust Project can help users and developers know they’re getting the product produced by the Rust Project and not someone else’s modified version. The trademark assures users and developers of the quality and safety of the product they’re using.

    Using the Trademarks

    Not Appearing Official, Affiliated, or Endorsed

    The most basic rule is that the Rust trademarks cannot be used in ways that appear (to a casual observer) official, affiliated, or endorsed by the Rust Project or Rust Foundation, unless you have written permission from the Rust Foundation. This is the fundamental way we protect users and developers from confusion. This is a requirement for all uses, even those that are listed as not requiring explicit approval. For example, the use of terms such as ‘official’, ‘original’ or ‘only’, (e.g. ‘The only Rust conference in the USA’ or ‘The original Rust Async Book’),  is likely to give the appearance that the use of the trademark is officially endorsed by the Rust Project or Rust Foundation, and therefore would not be acceptable.  

    Since this rule is about managing perception, it is subjective and somewhat difficult to nail down concretely. If you have any doubts, we would be more than happy to help.

    The Basics: Referring to Rust/Cargo

    As with any trademark, the Rust and Cargo word marks can be used with minimal restriction to refer to the Rust programming language and the Cargo package manager.

    They may not be used:

    • To refer to any other programming language;
    • To refer to a modified version of the Rust programming language, except as permitted below for minor changes;
    • In a way that is misleading or may imply association of unrelated modules, tools, documentation, or other resources with the Rust programming language;
    • In ways that confuses the community as to whether the Rust programming language is open source and free to use.

    Legitimate Sources of Official Source Code of the Rust Project and Associated Binaries

    Official source code and binaries produced by the Rust Project will always come from one of these sources; however, not everything on these domains is official or covered by this policy.

    Uses That Do Not Require Explicit Approval

    There are a variety of uses that do not require explicit approval. However, in all of the cases outlined below, you must ensure that use of the Rust trademarks does not appear official, affiliated or endorsed, as explained above. 

    • Stating accurately that software is written in the Rust programming language, that it is compatible with the Rust programming language, or that it contains code written in the Rust programming language, is allowed. In those cases, you may use the word “Rust” to indicate this, without prior approval. This is true both for non-commercial and commercial uses.
    • Using the name Rust in the name of crates or code repositories in e.g. GitHub, is allowed when referring to use with or compatibility with the Rust programming language.
    • Naming software in the form of “cargo-foobar”, where this is a subcommand for cargo intended to be executed as “cargo foobar.” is allowed, provided it is not implied or indicated to be an official cargo extension.
    • Publicly distributing a modified version of the Rust programming language, compiler, or the Cargo package manager is allowed, provided that the modifications are limited to:
    • Code adjustments for the purpose of porting to a different platform, architecture, or system, or integrating the software with the packaging system of that platform.
    • Hosting a fork of the code for the purpose of making changes, additions, or deletions that will be submitted as proposed improvements to the Rust Project code is allowed, as long as you do not market or promote your fork. 
    • Publicly distributing, in source code form, modifications made by an official platform distributor of Rust as listed explicitly or implicitly in https://doc.rust-lang.org/rustc/platform-support.html is allowed, provided such changes are licensed under the same license as the Rust Project code and the Rust Foundation has not stated publicly that it has asked the platform distributor to revert the modifications because they are inconsistent with the purpose and direction of the Rust Project.
    • Using the Rust trademarks on t-shirts, hats, and other artwork or merchandise, even in modified form, is allowed for your personal use or for use by a small group of community members, as long as they are not sold.
    • Using the Rust trademarks for social and small non-profit events like meetups, tutorials, and the like is allowed for events that are free to attend. Your materials for the event must not imply that the event is officially endorsed or run by the Rust Project or Rust Foundation unless you have written permission.  For commercial events (including sponsored ones), please check in with us.
    • Using unmodified Rust trademarks in books, blogs or publications like “Rust Journal” or “Rust Cookbook” is allowed.
    • Using the word “Rust” on websites, brochures, documentation, academic papers, books, and product packaging to refer to the Rust programming language or the Rust Project is allowed.

    Modifications must be clearly disclosed alongside the distribution if they do not have prior approval.

    Uses That Require Explicit Approval

    Distributing a modified version of the Rust programming language, compiler, or the Cargo package manager with modifications other than those permitted above and calling it Rust or Cargo requires explicit, written permission from the Rust Foundation. 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 with the logo mark requires explicit, written permission from the Rust Foundation. 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 or not profits benefit the Rust Project or Rust Foundation.
    • Using the Rust trademarks within another trademark requires written permission from the Rust Foundation and may include additional conditions of use and a fee for use.
    • The words “RustCamp,” “RustCon”, or “RustConf” cannot be used without explicit permission.

    If you don’t see your situation covered by these guidelines, please get in touch and we’ll be happy to help!

    Helping Out

    As a member of the Rust community, please let us know if you are concerned about any potentially questionable uses of the Rust logo and “Rust” word mark. You can report potential misuse to the Foundation. We will evaluate each case and take appropriate action.

    If you have a specific question or concern about promoting Rust or using its trademarks, please contact the Rust Foundation.

    Please do not approach users of the trademarks with a complaint. That should be left to the Rust Foundation and its representatives. Thanks!