diff options
| author | Joe Beda <joe.github@bedafamily.com> | 2018-03-31 20:41:37 -0700 |
|---|---|---|
| committer | Joe Beda <joe.github@bedafamily.com> | 2018-09-27 14:14:53 -0700 |
| commit | f4d36b4265c3f579f250c10fb2f12cdd8041e1b4 (patch) | |
| tree | 3dcacea88478be69980fd6854b7579fa2e0a0cb8 | |
| parent | 9b780b3c89ad323476c090f97e429fa1010a8571 (diff) | |
Add OARP approval process for SIG charters
Signed-off-by: Joe Beda <joe.github@bedafamily.com>
| -rw-r--r-- | committee-steering/governance/README.md | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md index 59fb78d8..b61ac493 100644 --- a/committee-steering/governance/README.md +++ b/committee-steering/governance/README.md @@ -28,6 +28,25 @@ All Kubernetes SIGs must define a charter defining the scope and governance of t - For minor updates to that only impact issues or areas within the scope of the SIG the SIG Chairs should facilitate the change. +## SIG Charter approval process + +When introducing a SIG charter or modification of a charter the following process should be used. +As part of this we will define roles for the [OARP] process (Owners, Approvers, Reviewers, Participants) + +- Identify a small set of Owners from the SIG to drive the changes. + Most typically this will be the SIG chairs. +- Work with the rest of the SIG in question (Reviewers) to craft the changes. + Make sure to keep the SIG in the loop as discussions progress with the Steering Committee (next step). + Including the SIG mailing list in communications with the steering committee would work for this. +- Work with the steering committee (Approvers) to gain approval. + This can simply be submitting a PR and sending mail to [steering@kubernetes.io]. + If more substantial changes are desired it is advisable to socialize those before drafting a PR. + - The steering committee will be looking to ensure the scope of the SIG as represented in the charter is reasonable (and within the scope of Kubernetes) and that processes are fair. +- For large changes alert the rest of the Kubernetes community (Participants) as the scope of the changes becomes clear. + Sending mail to [kubernetes-dev@googlegroups.com] and/or announcing at the community meeting are a good ways to do this. + +If there are questions about this process please reach out to the steering committee at [steering@kubernetes.io]. + ## How to use the templates SIGs should use [the template][Short Template] as a starting point. This document links to the recommended [SIG Governance][sig-governance] but SIGs may optionally record deviations from these defaults in their charter. @@ -41,9 +60,12 @@ The primary goal of the charters is to define the scope of the SIG within Kubern See [frequently asked questions] +[OARP]: https://stumblingabout.com/tag/oarp/ [Recommendations and requirements]: sig-governance-requirements.md [sig-governance]: sig-governance.md [Short Template]: sig-charter-template.md [frequently asked questions]: FAQ.md [sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml [sig-architecture example]: ../../sig-architecture/charter.md +[steering@kubernetes.io]: mailto:steering@kubernetes.io +[kubernetes-dev@googlegroups.com]: mailto:kubernetes-dev@googlegroups.com |