-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
the foundation owns rust trademarks #85504
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
cc #85291 |
The Rust Foundation has not taken over project governance, but we should probably link the README to that page rather than just saying it's a core team. Or since that section is just about trademarks, maybe it shouldn't mention governance at all. |
I've pushed a commit, now the trademark section don't mention governance. |
@bors r+ rollup Thanks! |
📌 Commit 9c65f9f has been approved by |
Rollup of 8 pull requests Successful merges: - rust-lang#85504 (the foundation owns rust trademarks) - rust-lang#85520 (Fix typo and improve documentation for E0632) - rust-lang#86680 (Improve error for missing -Z with debugging option) - rust-lang#86728 (Check node kind to avoid ICE in `check_expr_return()`) - rust-lang#86740 (copy rust-lld as ld in dist) - rust-lang#86746 (Fix rustdoc query type filter) - rust-lang#86750 (Test cross-crate usage of `feature(const_trait_impl)`) - rust-lang#86755 (alloc: `RawVec<T, A>::shrink` can be in `no_global_oom_handling`.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Any update on this? rust-lang/foundation-faq-2020#35 |
Given even thought this PR adresses wording on the matter it still links to excessively protective Mozzila mediaguide. Rust foundation should think about creating a Perl/Python like trademark policy, which still allows protections agaisnt copycats without being obnoxious on what contributors can and cannot do ;) |
No description provided.