Add OARP approval process for SIG charters

Signed-off-by: Joe Beda <joe.github@bedafamily.com>

committee-steering/governance/README.md

@@ -19,6 +19,25 @@ Specific attention has been given to:
 - Process for agreeing upon technical decisions
 - Process for ensuring technical assets remain healthy
 
+## 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 the 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 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
 
 When developing or modifying a SIG governance doc, the intention is for SIGs to use the templates (*under development*)
@@ -42,3 +61,5 @@ See [frequently asked questions]
 [Recommendations and requirements]: sig-governance-requirements.md
 [Short Template]: sig-governance-template-short.md
 [frequently asked questions]: FAQ.md
+[steering@kubernetes.io]: mailto:steering@kubernetes.io
+[kubernetes-dev@googlegroups.com]: mailto:kubernetes-dev@googlegroups.com