summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-09-21 08:02:00 -0700
committerGitHub <noreply@github.com>2018-09-21 08:02:00 -0700
commit9b9420e4f035a18074cc9e2e4b1ebf1587daf2a8 (patch)
tree3bd955562efcd4d3d90617e1a5529fb50eefb466
parent60c132ba1e6da493bca9153a81c9d26135e7f410 (diff)
parent4037c92ab3254d3a8e8731b9d9ef5fee4a54d6b4 (diff)
Merge pull request #2555 from spzala/sigibmcloudcharter
Add sig-ibmcloud Charter
-rw-r--r--sig-ibmcloud/charter.md38
1 files changed, 38 insertions, 0 deletions
diff --git a/sig-ibmcloud/charter.md b/sig-ibmcloud/charter.md
new file mode 100644
index 00000000..eb81a2ff
--- /dev/null
+++ b/sig-ibmcloud/charter.md
@@ -0,0 +1,38 @@
+# SIG IBMCloud Charter
+
+This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
+the Roles and Organization Management outlined in [sig-governance].
+
+## Scope
+
+The IBMCloud SIG enables activities and discussion around building, deploying, maintaining, supporting,
+and using Kubernetes on IBM Public and Private Clouds.
+
+### In scope
+- Determining and documenting best practices for configuring Kubernetes on IBM Cloud Kubernetes Service (IKS).
+- Determining and documenting best practices for configuring Kubernetes on IBM Cloud Private (ICP).
+- Discussing IKS and ICP tracking of Kubernetes features and releases.
+- Utilizing Kubernetes and related CNCF projects (e.g. Helm, Istio) by IKS and ICP.
+- Discussing bugs and feature requests recorded as Kubernetes upstream issues on GitHub. These issues should be tagged with `sig/ibmcloud`.
+
+#### Code, Binaries and Services
+
+The work to have a cloud provider specific public code repository is in progress. This section will be updated once the work is complete. Kubernetes upstream code that
+is directly related to IKS or ICP issues or features can be discussed.
+
+### Out of scope
+
+* Internal or commercial aspects of IKS and ICP.
+
+## Roles and Organization Management
+
+This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
+and opts-in to updates and modifications to [sig-governance], with exception that the SIG only
+has the Chair role at present. Chairs must also fulfill all of the responsibilities of the Tech Lead role as outlined in [sig-governance].
+
+### Subproject Creation
+Associated subprojects are created following the `by SIG Technical Leads` option procedure described in [sig-governance].
+
+[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
+[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
+[SIG README]: https://github.com/kubernetes/community/blob/master/sig-ibmcloud/README.md