summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--committee-steering/governance/wg-governance.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/committee-steering/governance/wg-governance.md b/committee-steering/governance/wg-governance.md
index d974f9be..875774dc 100644
--- a/committee-steering/governance/wg-governance.md
+++ b/committee-steering/governance/wg-governance.md
@@ -4,13 +4,15 @@
Working Groups provide a formal avenue for disparate groups to collaborate around a common problem, craft a balanced
position, and disband. Because they represent the interests of multiple groups, they are a vehicle for consensus
building. If code is developed as part of collaboration within the Working Group, that code will be housed in an
-appropriate repository as described in the [repositories document]. The merging of this code into the repository
+appropriate repository as described in the [repositories document][repodoc]. The merging of this code into the repository
will be governed by the standard policies regarding submitting code to that repository (e.g. developed within one or
more Subprojects owned by SIGs).
Because a working group is an official part of the Kubernetes project it is subject to steering committee oversight
over its formation and disbanding.
+[repodoc]: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md
+
## Goals of the process
- An easy-to-navigate process for those wishing to establish and eventually disband a new Working Group
@@ -118,4 +120,4 @@ References
- [2] https://groups.google.com/a/kubernetes.io/d/msg/steering/zEY93Swa_Ss/C0ziwjkGCQAJ
-[repository document]: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md \ No newline at end of file
+[repository document]: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md