-
Notifications
You must be signed in to change notification settings - Fork 18k
x/website: brand and trademark guideline document #58412
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
Comments
I will look into what guidance we can provide. I'll have to check with Google's lawyers, so it may take longer than our usual technical discussions. |
@rsc Thanks a lot! |
Change https://go.dev/cl/506756 mentions this issue: |
Just submitted a new page https://go.dev/brand that I hope will answer your questions. In particular "Tooltitude for Go" is fine. |
@rsc These are fantastic guidelines! Thank you very much. |
Change https://go.dev/cl/558195 mentions this issue: |
More formal brand guidelines are now available. For golang/go#58412. Change-Id: If3383c186115f146577ad80fddb7e1c5744af157 Reviewed-on: https://go-review.googlesource.com/c/website/+/558195 Auto-Submit: Russ Cox <[email protected]> Reviewed-by: Sameer Ajmani <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
It would be nice if you provide a brand/trademark guideline. I.e. describe how to use the words Go and GoLang which are registered trademarks. There's a great document describing how to use the visual branding: https://go.dev/blog/go-brand
For example, Apple has this document: https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html which describes their approach in details.
P.S. For me the question is it ok to use the phrase for "Tooltitude for Go/GoLang" in the name of our extension: https://marketplace.visualstudio.com/items?itemName=tooltitudeteam.tooltitude My understanding that it's covered by trademark fair use (under nominative use). However, it would be great if it's documented, and everyone using go/golang name could be a good citizen/use the same approach.
The text was updated successfully, but these errors were encountered: