Skip to content

Will trademark concerns be addressed? #93157

Closed as not planned
Closed as not planned
@irelativism

Description

Now that most of the foundation work seams to be completed, and that the project is a bit more independent from Mozilla, will the trademark concerns, be addressed.

Shouldnt trademark policy (and related references to Mozilla Media-guide) be rebased? Because while Rust copyright license allows distribution of derivative works, trademark policy might restrict this very own concession. Propousal:

  • Removing obnoxious clauses stating "need for explicit permission, except non commercial-use" on policy itself in what is related with media-guide. This would resolve derived restrictions from such a demanding policy. Given, in theory, even if somebody wants to makes minor changes, they would need to rebrand the entire compiler and build tools, so in practice nobody does (and just infringe above policy for practicallity).
  • Addressing the previous, in order to allow people to fork and by consequence contributing back, without the fear of infriging this overreaching policy. In other words this would also allow to study and redistibution of derivative works (not that people dont already, by infringement anyway) but so people have the ability to improve the source code and contribute/release improvements for the Rst codebase (which obviously still contain all references to Rst and abranged by its current trademark policy), without the need for users to rebrand their modified versions, allowing patching without "explicit approval” and withdrawing any fear of policy violation or infrigment. Therefore the community has doubts if Rst compiler and Cargo can be considered FOSS or not because it's ND by rebranding impracticability (except for non-commercial usage) so that is why is strictly urgent to remove such malevolent limitations.
  • Finalize all the details around the foundation and language independence and by consequence create a brand new policy, while still being able to efectively protect, and prevent copycats, or even malicius forks, that intend to republish sources with injected malware or any sort of related atacks to our project, but still respecting contributor freedom has explained above. A good sugestion would be for the team to look into similar policy, to what is propoused here. Implementation that adopt this kind of positions are for example what Perl and/or Python foundations have in place. Many believe such projects managed to reached a good balance between both objectives, on this very dificult balance.

partialSOLUTION: all branding should be defined in one file or folder making it easy for somebody who wants to distribute modified copies to rebrand. Firefox has the same trademark policy as Rust (Mozilla Media-guide), but they at least make it relatively easy to rebrand the browser: https://searchfox.org/mozilla-central/source/browser/branding/unofficial

Thanks nonetheless for the feedback, all your previous contributions for this project. And goodluck with finalizing all the foundation work. :)
P.S.Sorry for any misspellings here, but english is not my native language. Will hopefull hear back from you in the future, Cheers. (based on • irelativism comment Dec 7, 2020 •)

Some older issues might also prove helpfull:

Also this issue was discussed, in the past a few times, but originaly rejected in #53287#issuecomment-414472372 by mozilla team, now with independance the project might have a diferent view on it. Especially given recently show of position, that seams to provide a bit more openess and willingness to find a solution for this topic -> relevant answer:
"
The foundation will be reviewing the trademark policy, but it will ultimately be up to the board to decide the terms that are selected.
"

Activity

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

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: This is a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions