Skip to content
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

x/website: brand and trademark guideline document #58412

Closed
tooltitude-support opened this issue Feb 8, 2023 · 6 comments
Closed

x/website: brand and trademark guideline document #58412

tooltitude-support opened this issue Feb 8, 2023 · 6 comments
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done. website

Comments

@tooltitude-support
Copy link

tooltitude-support commented Feb 8, 2023

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.

@seankhliao seankhliao changed the title Brand and trademark guideline document brand: brand and trademark guideline document Feb 8, 2023
@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Feb 8, 2023
@ianlancetaylor ianlancetaylor changed the title brand: brand and trademark guideline document x/website: brand and trademark guideline document Feb 8, 2023
@gopherbot gopherbot added this to the Unreleased milestone Feb 8, 2023
@jamalc jamalc modified the milestones: Unreleased, website/unplanned Feb 16, 2023
@rsc
Copy link
Contributor

rsc commented Jun 5, 2023

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.

@tooltitude-support
Copy link
Author

@rsc Thanks a lot!

@gopherbot
Copy link

Change https://go.dev/cl/506756 mentions this issue: _content: add brand guidelines page: https://go.dev/brand

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jun 28, 2023
@rsc
Copy link
Contributor

rsc commented Jun 28, 2023

Just submitted a new page https://go.dev/brand that I hope will answer your questions. In particular "Tooltitude for Go" is fine.

@tooltitude-support
Copy link
Author

@rsc These are fantastic guidelines! Thank you very much.

@gopherbot
Copy link

Change https://go.dev/cl/558195 mentions this issue: _content/blog/go-brand: link to go.dev/brand

gopherbot pushed a commit to golang/website that referenced this issue Jan 24, 2024
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 <rsc@golang.org>
Reviewed-by: Sameer Ajmani <sameer@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done. website
Projects
None yet
Development

No branches or pull requests

6 participants