Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create api-machinery charter.md #2927

Merged
merged 6 commits into from
Dec 5, 2018
Merged

Create api-machinery charter.md #2927

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
6103df1
Create charter.md
maulin9 Nov 12, 2018
f3f86d1
Update charter.md
maulin9 Nov 12, 2018
6da9a6b
Update charter.md
maulin9 Nov 13, 2018
b7ab624
Update charter.md
maulin9 Nov 14, 2018
64f7327
Update charter.md
maulin9 Nov 21, 2018
cc7f60b
Updated charter.md
maulin9 Nov 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 63 additions & 0 deletions sig-api-machinery/charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be helpful to link to a doc that describes the process


### 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