search

servicebinding / spec

Specification for binding services to k8s workloads
https://servicebinding.io
Apache License 2.0
92 stars 35 forks source link

Kubernetes word usage and project association #108

Closed baijum closed 3 years ago

baijum commented 4 years ago

Since this spec is not part of the official Kubernetes project, a disclaimer text to mention the same would be good. By seeing the GitHub organization name and the title of the spec, it could be a bit misleading. Probably the GitHub organization can be changed as well (remove the k8s).

Disclaimer: I am not a legal expert ;-)

arthurdm commented 4 years ago

how would folks feel about proposing a new k8s SIG for service binding? https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md#creation

@nebhale @navidsh @scothis @baijum

Everyone I talk to says that the service catalog SIG is very inactive, so maybe it's a good time to propose a lively addition to the SIG family.

baijum commented 4 years ago

how would folks feel about proposing a new k8s SIG for service binding? https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md#creation

A new dedicated "SIG Service Binding" looks like a great idea!

There are lots of things to read and understand :) I am not a Kubernetes contributor. If we can find a mentor to help us through the whole process, that would be really helpful.

sbose78 commented 4 years ago

+1 on removing the "k8s-" substring, it is reserved for kubernetes projects. A SIG should be an independent conversation, even if the spec becomes a part of a sig, I doubt if we could keep "k8s-".

arthurdm commented 4 years ago

ya - the good thing is that k8s is only in the org name, which can be easily changed. The spec itself, its CRD, etc, don't use that string.

baijum commented 4 years ago

I have created a separate issue to track SIG proposal #116

nebhale commented 3 years ago

Complete