kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Addressed comments on scope; Removed sigs.yaml

This commit is contained in:
Sean Sullivan 2018-08-24 11:52:44 -07:00
parent 8b2aac9716
commit 7ac2653867
1 changed files with 13 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
sig-cli/charter.md
View File

@ -6,22 +6,24 @@ 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 command line tools and
related tools. This group focuses on general purpose command line tools and
libraries to interface with Kubernetes API's.
### In scope
SIG CLI section in [sigs.yaml]
SIG CLI [README]
#### Code, Binaries and Services
SIG CLI code include command line tools and binaries for working with Kubernetes
API's. Examples of these binaries include: [kubectl and kustomize].
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 defining the Kubernetes API that it
interfaces with. The Kubernetes API is the responsibility of SIG API Machinery.
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
@ -32,7 +34,7 @@ and opts-in to updates and modifications to [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
knowledge.
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
@ -43,8 +45,9 @@ and opts-in to updates and modifications to [sig-governance].
Option 1: by [SIG Technical Leads](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#L100)
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L487
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[Test Playbook]: https://docs.google.com/document/d/1Z3teqtOLvjAtE-eo0G9tjyZbgNc6bMhYGZmOx76v6oM
[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