diff options
| -rw-r--r-- | sig-architecture/README.md | 6 | ||||
| -rw-r--r-- | sig-architecture/charter.md | 40 | ||||
| -rw-r--r-- | sigs.yaml | 2 |
3 files changed, 46 insertions, 2 deletions
diff --git a/sig-architecture/README.md b/sig-architecture/README.md index ba944a67..c933fb03 100644 --- a/sig-architecture/README.md +++ b/sig-architecture/README.md @@ -8,7 +8,7 @@ To understand how this file is generated, see generator/README.md. --> # Architecture SIG -The SIG would be intended to guide the design principles of Kubernetes, as well as provide a consistent body of expertise necessary to ensure architectural consistency over time. +The Architecture SIG maintains and evolves the design principles of Kubernetes, and provides a consistent body of expertise necessary to ensure architectural consistency over time. ## Meetings * [Mondays at 17:00 UTC](https://zoom.us/j/2018742972) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:00&tz=UTC). @@ -25,4 +25,8 @@ Meeting notes and Agenda can be found [here](https://docs.google.com/document/d/ <!-- BEGIN CUSTOM CONTENT --> +## Additional materials + +* [Charter](charter.md) + <!-- END CUSTOM CONTENT --> diff --git a/sig-architecture/charter.md b/sig-architecture/charter.md new file mode 100644 index 00000000..04fd2ecf --- /dev/null +++ b/sig-architecture/charter.md @@ -0,0 +1,40 @@ +# SIG Architecture Charter + +This charter is a WIP. + +The Architecture SIG maintains and evolves the design principles of +Kubernetes, and provides a consistent body of expertise necessary to +ensure architectural consistency over time. + +The scope covers issues that span all the system's components, how +they fit together, how they interact, etc. + +Specific areas of focus include: + +* Defining the scope of the Kubernetes project + * [What is (and is not) Kubernetes](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/) +* Maintaining, evolving, and enforcing the deprecation policy + * [Deprecation policy](https://kubernetes.io/docs/reference/deprecation-policy/) +* Documenting and evolving the system architecture + * [Kubernetes Design and Architecture](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture.md) +* Defining and driving necessary extensibility points +* Establishing and documenting design principles + * [Design principles](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/principles.md) +* Establishing and documenting conventions for system and user-facing APIs + * [API conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md) +* Developing necessary technical review processes, such as the proposal and API review processes +* Driving improvement of overall code organization, including github orgs and repositories +* Educating approvers/owners of other SIGs (e.g., by holding office hours) + +Out of scope: +* Issues specific to a particular component or functional area, which would be the purview + of some other SIG, except where they deviate from project-wide principles and conventions. +* [Release support policy](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/versioning.md) + is owned by SIG Release + +TODO: +* Formalize decision processes +* Document initial reviewers and approvers +* Clarify criteria for areas out of scope for the SIG +* Document who owns client library, build, and release artifacts +* Document who owns conformance definition, profiles, etc. @@ -49,7 +49,7 @@ sigs: - name: Architecture dir: sig-architecture mission_statement: > - The SIG would be intended to guide the design principles of Kubernetes, as well as provide a consistent + The Architecture SIG maintains and evolves the design principles of Kubernetes, and provides a consistent body of expertise necessary to ensure architectural consistency over time. leads: - name: Brian Grant |