summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2018-12-05 13:31:59 -0800
committerGitHub <noreply@github.com>2018-12-05 13:31:59 -0800
commit77c7fa36f7950b8be0cc9c6a4bab53375f71e646 (patch)
treebfb4e93229298793c1ff9e9f72027e74d73c9659
parent7b0f0d9f1c74b94bb9017f4fc33a125739311c85 (diff)
parentcc7f60be1374ca20057c0d19543a524463fe9903 (diff)
Merge pull request #2927 from maulin9/patch-1
Create api-machinery charter.md
-rw-r--r--sig-api-machinery/charter.md63
1 files changed, 63 insertions, 0 deletions
diff --git a/sig-api-machinery/charter.md b/sig-api-machinery/charter.md
new file mode 100644
index 00000000..28baf5f0
--- /dev/null
+++ b/sig-api-machinery/charter.md
@@ -0,0 +1,63 @@
+# SIG API Machinery 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
+
+SIG API Machinery is responsible for the development and enhancement of Kubernetes cluster control plane. The scope covers API server, persistence layer (etcd), controller manager, cloud controller manager, CustomResourceDefinition and webhooks.
+
+### In scope
+
+#### Code, Binaries and Services
+
+All aspects of
+* API server
+* API registration and discovery
+* Generic API CRUD semantics
+* Admission control
+* Encoding/decoding
+* Conversion
+* Defaulting
+* Persistence layer (etcd)
+* OpenAPI
+* The informer libraries
+* CustomResourceDefinition
+* Webhooks
+* Garbage collection
+* Namespace lifecycle
+* Client libraries
+
+#### Cross-cutting and Externally Facing Processes
+
+Client library releases
+
+### Out of scope
+
+The contents of individual APIs are owned by SIG Architecture
+
+## Roles and Organization Management
+
+This sig follows adheres to the Roles and Organization Management outlined in [sig-governance]
+and opts-in to updates and modifications to [sig-governance].
+
+### Additional responsibilities of Chairs
+
+Technical leads seeded by legacy SIG chairs from existing subproject owners
+
+### Additional responsibilities of Tech Leads
+
+N/A
+
+### Deviations from [sig-governance]
+
+N/A
+
+### Subproject Creation
+
+SIG delegates subproject approval to Technical Leads. See [Subproject creation - Option 1.]
+
+[Subproject creation - Option 1.]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subproject-creation
+[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
+[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-api-machinery/README.md#subprojects
+[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md