Rust Foundation Shares Draft of New, Simpler Trademark Policy (rust-lang.org) 13
"The Rust trademark policy has been updated and a new draft is available to view," announced the Rust Foundation this week.
The last proposed trademark policy (in April of 2023) was criticized by open source advocate Bruce Perens in The Register as "far awry of fair use which is legally permitted." The Rust Foundation says this new version has "incorporated a number of suggestions from the Rust community," in a blog post that summarizes the feedback and enumerates specific ways it's been addressed: 1. We primarily plan to lean on community reports for enforcement and have no intention of spending our limited resources policing the work of small creators.
2. We have removed the non-legal language summary and instead have clarified wording throughout as best we can while keeping the policy valid.
3. The Rust trademark does not cover use of the word "Rust" in general and instead pertains to its use in relevant technical settings.
4. We have updated the logo usage policy. Color modifications are allowed.
5. The non-endorsement rule is about managing perception of official affiliation with the Foundation and Rust Project, and is thus subjective.
6. We removed restrictions on the use of "Rust" and "Cargo" in package names. The crates prefixes "rust-" and "cargo-" are no longer reserved to the Rust Project.
7. We will usually allow the community to use the marks on limited merchandise (more details in the updated draft)....
[T]he central purpose of these updates is to empower all Rustaceans to engage with the Rust language ecosystem more confidently. As a final step in this process, we invite you to review the updated policy and share any blocking concerns you might have... Thank you to everyone who weighed in with helpful suggestions on the initial trademark policy draft we shared. The level of engagement and passion within the Rust community is inspiring to all of us at the Rust Foundation.
The tech news site Heise Online writes "It is noticeable that the language is much clearer and dispenses with a lot of legal jargon," in a piece which argues the new draft "should calm the waves and create clarity." The new draft is not only formulated more simply, but is also significantly shorter. Some restrictions have been softened in the new rules or have disappeared completely...
Meanwhile, the Foundation has also adapted its logo so that it is clear which logo stands for the programming language and which for the Foundation. The use of the name Rust is explicitly permitted to identify projects that are either written in the programming language or are compatible with it...
Before the new trademark rules come into force, the Rust Foundation is collecting feedback on the current draft. The web form is open until November 20, 2024.
The last proposed trademark policy (in April of 2023) was criticized by open source advocate Bruce Perens in The Register as "far awry of fair use which is legally permitted." The Rust Foundation says this new version has "incorporated a number of suggestions from the Rust community," in a blog post that summarizes the feedback and enumerates specific ways it's been addressed: 1. We primarily plan to lean on community reports for enforcement and have no intention of spending our limited resources policing the work of small creators.
2. We have removed the non-legal language summary and instead have clarified wording throughout as best we can while keeping the policy valid.
3. The Rust trademark does not cover use of the word "Rust" in general and instead pertains to its use in relevant technical settings.
4. We have updated the logo usage policy. Color modifications are allowed.
5. The non-endorsement rule is about managing perception of official affiliation with the Foundation and Rust Project, and is thus subjective.
6. We removed restrictions on the use of "Rust" and "Cargo" in package names. The crates prefixes "rust-" and "cargo-" are no longer reserved to the Rust Project.
7. We will usually allow the community to use the marks on limited merchandise (more details in the updated draft)....
[T]he central purpose of these updates is to empower all Rustaceans to engage with the Rust language ecosystem more confidently. As a final step in this process, we invite you to review the updated policy and share any blocking concerns you might have... Thank you to everyone who weighed in with helpful suggestions on the initial trademark policy draft we shared. The level of engagement and passion within the Rust community is inspiring to all of us at the Rust Foundation.
The tech news site Heise Online writes "It is noticeable that the language is much clearer and dispenses with a lot of legal jargon," in a piece which argues the new draft "should calm the waves and create clarity." The new draft is not only formulated more simply, but is also significantly shorter. Some restrictions have been softened in the new rules or have disappeared completely...
Meanwhile, the Foundation has also adapted its logo so that it is clear which logo stands for the programming language and which for the Foundation. The use of the name Rust is explicitly permitted to identify projects that are either written in the programming language or are compatible with it...
Before the new trademark rules come into force, the Rust Foundation is collecting feedback on the current draft. The web form is open until November 20, 2024.
Reasonable (vs. Celebrity) (Score:2, Interesting)
Its quite refreshing reading about an organization looking to relax enforcement and ensure fair use.
If Taylor Swift Inc. was in charge of this, a planet would be forced to come up with a new word to describe what happens to metal when it deteriorates. In 47 languages.
Thank you (Score:5, Funny)
3. The Rust trademark does not cover use of the word "Rust" in general and instead pertains to its use in relevant technical settings.
My pickup truck thanks you.
I'd settle for a secondary syntax (Score:4, Interesting)
The learning curve for the Rust syntax is needlessly high. I honestly believe that it was made this way in order to avoid C++ simply adding the features that Rust touts as being irreplaceable and leaving Rust to die off. The only people that care about the Rust trademark policy are the people using Rust. What about trying to make it easier for people to actually use Rust?
Re: (Score:2)
The learning curve for the Rust syntax is needlessly high. I honestly believe that it was made this way in order to avoid C++ simply adding the features that Rust touts as being irreplaceable
I'm not saying you're wrong, but how would it do that, especially if the syntax is bad? What would stop someone adding the same functionality to C++, with better syntax, and hookers?
Re: (Score:2)
I'm not saying you're wrong, but how would it do that, especially if the syntax is bad?
By making a new spec with a new syntax and a different parser. Use a flag to select your preferred Rust syntax.
What would stop someone adding the same functionality to C++, with better syntax, and hookers?
What makes you think people aren't working on it already?
Re: (Score:2)
What makes you think people aren't working on it already?
Your comment made it sound that way.
Re: (Score:2)
What makes you think people aren't working on it already?
Your comment made it sound that way.
You need to consider that situations change with time.
Rust was invented about a decade ago. My comment was about when it was first invented. The idea is that Rust could have been killed in it's infancy if it's killer features features were merged into the C++ spec. The insane syntax has kept a lot of people away which allowed it time to grow. It's grown enough that there is plenty of overlap and now people are working toward adding Rust features to C++.
Re: (Score:2)
Circle C++ is an implementation of nearly all the Rust features in a nice, compatible C++ syntax. Well nice if you're used to C++. I suspect most of these things will end up informing the next C++ spec in some way. Given that I don't develop software much these days, I'm waiting for that, rather than learn Rust.
Great improvement (Score:1)
Is Rust actually still around? (Score:2)
Best regards, The C++ Programming Language
Re: (Score:2)
Haha. Nice one.
Although I have to admit that experiments like the Circle C++ compiler show that there are distinct advantages for putting safety constructs front and center in C++. I'm looking forward to how this will turn out as the next spec for C++ considers many of these things. If all Rust does is push existing languages to adopt and enforce safer principles, that's a good thing and we should thank them for it.
Re: (Score:2)
I’ve been programming mostly in C++ full time since the late 1990s, in scientific computing, HPC, simulation and offline production rendering Throughout this time the language has evolved — rapidly in the last decade — while predictions of its demise or complete replacement by Java, C#, Python, JavaScript, Go, Rust and whatever else have been the only constant.
Rust was high profile a few years ago but seems to have fallen mostly off the radar. I agree Rust was a good
Foundations? Trademarks? (Score:2)