|  | 
|  | 1 | +--- | 
|  | 2 | +layout: post | 
|  | 3 | +title: "Next Steps on the Rust Trademark Policy" | 
|  | 4 | +author: the Leadership Council | 
|  | 5 | +--- | 
|  | 6 | + | 
|  | 7 | +As many of you know, the Rust language trademark policy has been the subject of | 
|  | 8 | +an extended revision process dating back to 2022. In 2023, the Rust Foundation | 
|  | 9 | +released an updated draft of the policy for input following an initial survey | 
|  | 10 | +about community trademark priorities from the previous year along with review | 
|  | 11 | +by other key stakeholders, such as the Project Directors. Many members of our | 
|  | 12 | +community were concerned about this initial draft and shared their thoughts | 
|  | 13 | +through the feedback form. Since then, the Rust Foundation has continued to | 
|  | 14 | +engage with the Project Directors, the [Leadership Council](https://www.rust-lang.org/governance/teams/leadership-council), and the wider Rust | 
|  | 15 | +project (primarily via all@) for guidance on how to best incorporate as much | 
|  | 16 | +feedback as possible. | 
|  | 17 | + | 
|  | 18 | +After extensive discussion, we are happy to circulate an updated draft with the | 
|  | 19 | +wider community today for final feedback. An effective trademark policy for an | 
|  | 20 | +open source community should reflect our collective priorities while remaining | 
|  | 21 | +legally sound. While the revised trademark policy cannot perfectly address | 
|  | 22 | +every individual perspective on this important topic, its goal is to establish | 
|  | 23 | +a framework to help guide appropriate use of the Rust trademark and reflect as | 
|  | 24 | +many common values and interests as possible. In short, this policy is designed | 
|  | 25 | +to steer our community toward a shared objective: to maintain and protect the | 
|  | 26 | +integrity of the Rust programming language. | 
|  | 27 | + | 
|  | 28 | +The Leadership Council is confident that this updated version of the policy has | 
|  | 29 | +addressed the prevailing concerns about the initial draft and honors the | 
|  | 30 | +variety of voices that have contributed to its development. Thank you to those | 
|  | 31 | +who took the time to submit well-considered feedback for the initial draft last | 
|  | 32 | +year or who otherwise participated in this long-running process to update our | 
|  | 33 | +policy to continue to satisfy our goals. | 
|  | 34 | + | 
|  | 35 | +Please review the updated Rust trademark policy [here][policy], and share | 
|  | 36 | +any critical concerns you might have [via this form][form] by November 20, 2024. | 
|  | 37 | +The Foundation has also published a [blog post][blog post] which goes into more | 
|  | 38 | +detail on the changes made so far. The Leadership Council and Project Directors | 
|  | 39 | +look forward to reviewing concerns raised and approving any final revisions | 
|  | 40 | +prior to an official update of the policy later this year. | 
|  | 41 | + | 
|  | 42 | +[policy]: https://drive.google.com/file/d/1hjTx11Fb-4W7RQLmp3R8BLDACc7zxIpG/view?usp=sharing | 
|  | 43 | +[form]: https://docs.google.com/forms/d/e/1FAIpQLSeU1Ocopa0v9UZn_ZSTkKQM7gqZIrt63lCFz-xtogcFHMtkAg/viewform?usp=sf_link | 
|  | 44 | +[blog post]: https://rustfoundation.org/news/rust-trademark-policy-updates/ | 
0 commit comments