3 ms·
It looks like the Open Usage Commons organization handles trademarking, so roughly speaking (I'm not a lawyer) they set and enforce rules under which other enti
by jka 6y ago
It looks like the Open Usage Commons organization handles trademarking, so roughly speaking (I'm not a lawyer) they set and enforce rules under which other entities may use their hosted project names and brand identities.
When GCP's container engine launched[1] in 2014 it was initially referred to by the anagram 'GKE' yet corresponded to the name 'Google Container Engine'.
After achieving CNCF certification in Nov 2017[2], GCP began using the term 'Kubernetes' within the product name, rebranding it as 'Google Kubernetes Engine'.
At least as far back as Oct 2017, members of the CNCF did not have to pay any fees[3] to participate in the conformance program.
Is it possible that executives within Google were unhappy about the marketshare gains of GKE and attribute this partially to the time it took their product to achieve certification?
If so, could that have led them to push other open source initiatives within the company to retain their trademarks under tighter control, even if that required creating an organization with less experience handling international trademark registration?
As per the post, IBM's stated standpoint is: "IBM continues to believe that the best way to manage key open source projects such as Istio is with true open governance, under the auspices of a reputable organization with a level playing field for all contributors, transparency for users, and vendor-neutral management of the license and trademarks."
[1] - https://www.infoq.com/news/2014/11/google-cloud-container-engine/ https://www.infoq.com/news/2014/11/google-cloud-container-en...
[2] - https://cloud.google.com/blog/products/gcp/introducing-certified-kubernetes-and-google-kubernetes-engine https://cloud.google.com/blog/products/gcp/introducing-certi...
[3] - https://github.com/cncf/k8s-conformance/commit/34683a331647377585f30df47a1bce27b731cac9#diff-1131adf39164dafb81de955efadf6029R39 https://github.com/cncf/k8s-conformance/commit/34683a3316473...
- 9nGQluzmnq3M 6y agoFWIW, the GKE acronym (also?) came about because GCE is GCP's core VM offering, Google Compute Engine.
- crb 6y ago> After achieving CNCF certification in Nov 2017[2], GCP began using the term 'Kubernetes' within the product name, rebranding it as 'Google Kubernetes Engine'. After _creating_ the certification program: it was driven by GKE PM (and upcoming book author[1]) William Denniss. https://kubernetes.io/blog/2017/10/software-conformance-certification/ https://kubernetes.io/blog/2017/10/software-conformance-cert... (At the time of GKE's launch, 'containers' were more well known than 'Kubernetes'. Google also owned the trademark, so it could have been called Kubernets Engine from the beginning.) [1] https://www.manning.com/books/getting-started-with-kubernetes https://www.manning.com/books/getting-started-with-kubernete...
- jka 6y agoThanks for the explanation; that all makes sense and certainly makes the naming of GKE seem like less of a driving factor. PS: For anyone curious about the adoption of the word 'Kubernetes', Google Trends provides a good summary: https://trends.google.com/trends/explore?date=all&q=kubernetes https://trends.google.com/trends/explore?date=all&q=kubernet... (2014 was definitely very early days)