-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trademark restrictions? #53287
Comments
This question should be asked at the email address linked on the Legal page rather than here. |
Just received a response. It seems a TRADEMARK.md may be useful to direct people to the appropriate information from github.
This issue can be closed once trademark notification is included or mentioned on README.md. |
I've tagged this issue as If you want to fix this bug and need any help, please let me know, and I'm happy to assist! |
Hi @steveklabnik |
Add summary and reference to Rust trademark guide Fix rust-lang#53287 cc @steveklabnik
Any news regarding this ^ |
Want to fix this bug? There are instructions below.
This github repository does not contain a trademark file, and I am curious if https://www.rust-lang.org/en-US/legal.html still applies, as it would seem.
Debian and some other distributions are applying patches against the Rust language and Cargo package. I assume this qualifies as something which requires explicit approval?
If so, removing or restricting packages from Cargo would also be considered a modification. e.g. some distributions may wish to block access to Cargo downloads that are not in compliance with license standards.
Just wanted to get some clarification on this as it is not mentioned here in the repo and some folks seems to think that because there is no trademark "here" that rust-lang can be distributed with modifications without approval. I believe the only way such modifications would be allowed unrestricted, is if "rust" was not used at all in the package and it was clearly defined as a rebranded fork that is not affiliated with the official package - Otherwise the trademark policy is still enforced.
The text was updated successfully, but these errors were encountered: