Interesting application of a trademark policy as applied to FOSS: the software is distributed under ALv2, but contains trademarks owned by the company managing the projects (which also has commercial offerings based on the software). The trademark policy permits you to make your own builds of the software, without removing the trademarks, *only* for development purposes (to contribute to the project), but not for any other purpose. If you want to use your builds for any other purpose, even just for internal use to manage your infrastructure, you have to remove all the trademarks first.

https://www.systeminit.com/open-source

CC @pchestek

#FOSS #TrademarkPolicy

System Initiative

The recent trademark policy proposal by the Rust Foundation has sparked some criticism.

In its restrictiveness, I consider it harmful to the friendly and open attitude of the Rust community. If you feel the same, you can voice your concerns in this feedback form: https://docs.google.com/forms/d/e/1FAIpQLSdaM4pdWFsLJ8GHIUFIhepuq0lfTg_b0mJ-hvwPdHa4UTRaAg/viewform until 16th April, 5 p.m. PDT #rust #rusttrademark #rustfoundation #trademarkpolicy

Rust Trademark Policy Comment Form

TRADEMARK POLICY CONTEXT The Rust Foundation is developing an updated Trademark Policy for use of the registered trademarks Rust and Cargo. We began this legal process collaboratively in August 2022, starting with the Trademark Policy Review Survey, which received nearly 1,000 responses. Following that survey, we invited any individuals interested to join the Trademark Policy Working Group, consisting of Rust Project leaders, Foundation staff and Legal Counsel. This Working Group met on several occasions between September 2022 and January 2023 to develop an updated policy suitable for the needs of the Rust communities. We appreciate all of the input shared and collaboration involved in the development of this policy to date! A central aim of the Rust Trademark Policy is to help ensure that when you encounter a product, project, or resource listing an affiliation with the Rust programming language via the Marks, you can be better assured of its authenticity and affiliation with the Rust Foundation/the Rust Project. We want to instill confidence in this policy within the Rust community and enable you to use it as a helpful resource — it is not meant to intimidate or impose a sense of great limitation where undue. CALL-TO-ACTION The document linked below as a Google Doc displays the full draft policy, as well as an introductory plain English outline and FAQ section to preface the policy on the Trademark section of the Rust Foundation website. We welcome any feedback, comments or issues you identify within the draft policy, to ensure that we can create a final policy and FAQ that is fit for purpose. You will not be submitting feedback directly within the Google Doc file, but using the open text field below. GOALS & NEXT STEPS After the commentary period is over, we will produce a final version of the Trademark Policy. We will also develop a summarized response to the feedback received. NOTES: - While it is our intention to ensure the policy is as comprehensive as possible, it cannot provide details for every use case. With that said, please let us know if there are any common use cases you feel aren't adequately represented by this policy. Our goal is for the overarching principles of the policy to guide the majority of use-cases. - In order to proceed with the most productive and expedient process possible, the Rust Foundation is only soliciting comments on the Trademark Policy via this survey. The public comment period for the Rust Trademark Policy will close on April 16th at 5 PM PDT. Thank you for taking time out of your day to review the Rust Trademark Policy and provide feedback.

Google Docs