deduping and creating gov docs

1 files changed, 26 insertions, 12 deletions

diff --git a/governance.md b/governance.md
index 8dfc32cc..243d7a01 100644
--- a/governance.md
+++ b/governance.md
@@ -6,18 +6,22 @@ The Kubernetes community adheres to the following principles:
 * Open: Kubernetes is open source. See repository guidelines and CLA, below.
 * Welcoming and respectful: See Code of Conduct, below.
 * Transparent and accessible: Work and collaboration should be done in public. See SIG governance, below.
-* Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, [scope](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/), and [design principles](contributors/design-proposals/architecture/principles.md).
+* Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, [scope], and [design principles].
 
 # Code of Conduct
 
-The Kubernetes community abides by the [Kubernetes code of conduct](/code-of-conduct.md). Here is an excerpt:
+The Kubernetes community abides by the [Kubernetes code of conduct]. Here is an excerpt:
 
 _As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities._
 
 As a member of the Kubernetes project, you represent the project and your fellow contributors.
 We value our community tremendously and we'd like to keep cultivating a friendly and collaborative
 environment for our contributors and users. We want everyone in the community to have
-[positive experiences](https://www.cncf.io/blog/2016/12/14/diversity-scholarship-series-one-software-engineers-unexpected-cloudnativecon-kubecon-experience).
+[positive experiences].
+
+# Values
+
+[We have them!]
 
 # Community membership
 
@@ -83,6 +87,10 @@ community.
 See [sig governance] for more details about current SIG operating
 mechanics, such as mailing lists, meeting times, etc.
 
+More information:  
+[SIG Governance Requirements]  
+[SIG Lifecycle] - for a tactical checklist on creation and retirement  
+
 ### Subprojects
 
 Specific work efforts within SIGs are divided into **subprojects**.
@@ -97,10 +105,9 @@ field technical escalations, etc.
 Example subprojects for a few SIGs:
 * SIG Network: pod networking (CNI, etc.), Service (incl. kube-proxy),
 Ingress, DNS, and Network policy
-* SIG Apps: workload APIs, Helm, Kompose, ...
 * SIG Cluster Lifecycle: kubeadm, kops, kubespray, minikube, ...
 
-Subprojects for each SIG are documented in [sigs.yaml](sigs.yaml).
+Subprojects for each SIG are documented in [sigs.yaml].
 
 ## Working Groups
 
@@ -115,7 +122,7 @@ forming a Working Group.
 See [working group governance] for more details about forming and disbanding
 Working Groups.
 
-Working groups are documented in [sigs.yaml](sigs.yaml).
+Working groups are documented in [sigs.yaml].
 
 
 ## Committees
@@ -134,7 +141,7 @@ charter.
 Some topics have long term relevance to large groups of Kubernetes users, but
 do not have clear deliverables or ownership of parts of the Kubernetes
 code base. As such they are neither good fits for SIGs or Working Groups.
-An example of such a topic might be continuous delivery to Kubernetes. 
+An example of such a topic might be continuous delivery to Kubernetes.
 
 Though their central goal is not a a deliverable piece of work, as contributing
 members of the community user groups are expected to work with SIGs
@@ -142,7 +149,7 @@ to either identify friction or usability issues that need to be addressed,
 or to provide or improve documentation in their area of expertise. However
 these activities are covered under general code contributions to the relevant
 SIGs (e.g. SIG Docs) rather than as part of the user group. These contributions
-are expected to be more incremental and ad-hoc versus the more targeted 
+are expected to be more incremental and ad-hoc versus the more targeted
 output of a user group.
 
 User groups function as a centralized resource to facilitate communication
@@ -152,8 +159,8 @@ form working groups under the auspices of some SIG for such work. Likewise
 they shouldn't take ownership of anything in the Kubernetes process, as
 that is a role for SIGs.
 
-To facilitate discoverability and engagement, 
-user groups are documented in [sigs.yaml](sigs.yaml)
+To facilitate discoverability and engagement,
+user groups are documented in [sigs.yaml]
 
 ## Cross-project Communication and Coordination
 
@@ -192,12 +199,19 @@ Note that "Kubernetes incubator" process has been deprecated in favor of the new
 
 All contributors must sign the CNCF CLA, as described [here](CLA.md).
 
+[positive experiences]: https://www.cncf.io/blog/2016/12/14/diversity-scholarship-series-one-software-engineers-unexpected-cloudnativecon-kubecon-experience
+[sigs.yaml]: /sigs.yaml
+[SIG Lifecycle]: /sig-wg-lifecycle
+[We have them!]: /values.md
+[Kubernetes code of conduct]: /code-of-conduct.md
+[design principles]: /contributors/design-proposals/architecture/principles.md
+[scope]: https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/
 [community membership]: /community-membership.md
-[sig governance]: /sig-governance.md
+[sig governance]: /committee-steering/sig-governance.md
 [owners]: /community-membership.md#subproject-owner
 [sig charter process]: /committee-steering/governance/README.md
 [short template]: /committee-steering/governance/sig-governance-template-short.md
 [kubernetes repository guidelines]: /github-management/kubernetes-repositories.md
 [working group governance]: /committee-steering/governance/wg-governance.md
-
+[SIG Governance Requirements]: /committee-steering/governance/sig-governance-requirements.md
 [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/governance.md?pixel)]()