summaryrefslogtreecommitdiff
path: root/governance.md
diff options
context:
space:
mode:
authorBrian Grant <briangrant@google.com>2018-03-08 10:16:06 -0800
committerBrian Grant <briangrant@google.com>2018-03-08 10:16:06 -0800
commit21fd318e6ac008ab32f85e39e66e197e40b2bd99 (patch)
tree2f3bb6a3fdb167c3f682143be5ade0c430cf61e5 /governance.md
parente98ca57eb2a9f53506c79af70a8d5c9ca93f0c91 (diff)
Reformat subproject examples.
Diffstat (limited to 'governance.md')
-rw-r--r--governance.md12
1 files changed, 7 insertions, 5 deletions
diff --git a/governance.md b/governance.md
index 1fdf0b7d..30dd9203 100644
--- a/governance.md
+++ b/governance.md
@@ -93,11 +93,13 @@ subproject’s technical leaders: responsible for vision and direction
and overall design, choose/approve change proposal (KEP) approvers,
field technical escalations, etc.
-For example, SIG Network potentially is comprised of multiple
-subprojects: pod networking (CNI, etc.), Service and kube-proxy,
-Ingress and Ingress controllers, DNS, and Network policy. SIG Apps has
-the workload APIs, Helm, and Kompose. SIG Cluster Lifecycle has
-kubeadm, kops, kubespray, minikube, 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).
## Working Groups