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.

Sign up for GitHub

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

Jump to bottom

Spell out references to GKE and GCE #10354

Closed
RichieEscarez opened this issue Jun 25, 2015 · 2 comments
Closed

Spell out references to GKE and GCE #10354

RichieEscarez opened this issue Jun 25, 2015 · 2 comments
Assignees
@RichieEscarez
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Milestone
v1.0

Comments

@RichieEscarez
Copy link
Contributor

Replacing all instances of GKE or GCE in the documentation with full product names: Google Container Engine or Google Compute Engine. Note: this is also a GKE/GCE guideline.

This is also based on customer feedback: "got confused with the difference between gce and gke"
@RichieEscarez RichieEscarez added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 25, 2015
@RichieEscarez RichieEscarez self-assigned this Jun 25, 2015
@RichieEscarez RichieEscarez added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 25, 2015
@RichieEscarez RichieEscarez added this to the v1.0 milestone Jun 25, 2015
@mbforbes
Copy link
Contributor

Out of curiosity, what's the data behind this? A single customer?

Once you know what GCE and GKE are, visually diffing "Compute" and "Container" is harder than "C" and "K," in my opinion.

@mbforbes mbforbes added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Jun 25, 2015
@RichieEscarez
Copy link
Contributor Author

Yeah, one customer that im aware of. Then adding on top of that the branding guidelines "official rules (signed off by marketing)".

I agree and think the real challenge is when gke and gce show up in a single document.

Ultimately, this is a consistency item and i think if and where we do use gke or gce in any particular document, it should be capitalized and the first reference should be defined "Google Container Engine (GKE)" and then can use GKE thereafter.

@RichieEscarez RichieEscarez mentioned this issue Jun 25, 2015
Merged
RichieEscarez added a commit to RichieEscarez/kubernetes that referenced this issue Jun 26, 2015
@RichieEscarez
Replaced (or defined first instance of) GKE/GCE with Google Container…
899145d 
… Engine/Google Compute Engine

Fixes kubernetes#10354
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RichieEscarez RichieEscarez

Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
2 participants
@mbforbes @RichieEscarez