summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-08-28 12:45:52 -0700
committerGitHub <noreply@github.com>2018-08-28 12:45:52 -0700
commitab4ada747580b50c0df64a917178fa6863d15e56 (patch)
tree465ec62aee59da41bed918a8b66f81b0ab397a95
parentc86d0abf3f7fb8e1ac77badc902a668e7f5893c9 (diff)
parent7ac26538679db25d565791f6d7cf4df9feacd0b6 (diff)
Merge pull request #2453 from seans3/sigcli-charter
First version of SIG CLI Charter
-rw-r--r--sig-cli/charter.md53
1 files changed, 53 insertions, 0 deletions
diff --git a/sig-cli/charter.md b/sig-cli/charter.md
new file mode 100644
index 00000000..8ce0dd18
--- /dev/null
+++ b/sig-cli/charter.md
@@ -0,0 +1,53 @@
+# SIG CLI 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 Command Line Interface SIG (SIG CLI) is responsible for kubectl and
+related tools. This group focuses on general purpose command line tools and
+libraries to interface with Kubernetes API's.
+
+### In scope
+
+SIG CLI [README]
+
+#### Code, Binaries and Services
+
+SIG CLI code include general purpose command line tools and binaries for working
+with Kubernetes API's. Examples of these binaries include: [kubectl and kustomize].
+
+### Out of scope
+
+SIG CLI is not responsible for command-line tools built and maintained by other
+SIGs, such as kubeadm, which is owned by SIG Cluster Lifecycle. SIG CLI is not
+responsible for defining the Kubernetes API that it interfaces with. The
+Kubernetes API is the responsibility of SIG API Machinery.
+
+## Roles and Organization Management
+
+SIG CLI adheres to the Roles and Organization Management outlined in [sig-governance]
+and opts-in to updates and modifications to [sig-governance].
+
+### Deviations from [sig-governance]
+
+- In addition to Technical Leads, SIG CLI defines Emeritus Leads. These former
+ SIG CLI leaders *SHOULD* be available to provide historical perspective and
+ domain knowledge.
+- SIG CLI defines the role of Test Health Maintainer. Contributors who have
+ successfully completed one test on-call rotation within the last six months as
+ shown in the test on-call schedule of the [Test Playbook] are included in this
+ group. Test Health Maintainers are SIG CLI Members.
+
+### Subproject Creation
+
+Option 1: by [SIG Technical Leads](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#L100)
+
+
+[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
+[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
+[README]: https://github.com/kubernetes/community/blob/master/sig-cli/README.md
+[kubectl and kustomize]: https://github.com/kubernetes/community/blob/master/sig-cli/README.md#subprojects
+[Test Playbook]: https://docs.google.com/document/d/1Z3teqtOLvjAtE-eo0G9tjyZbgNc6bMhYGZmOx76v6oM
+