Add Subproject Leads responsibilities

Co-Authored-by: Shane Utt <[email protected]>
Signed-off-by: Surya Seetharaman <[email protected]>
Signed-off-by: Shane Utt <[email protected]>

Author: tssurya

sig-network/README.md

@@ -136,6 +136,31 @@ The following [subprojects][subproject-definition] are owned by sig-network:
 [subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
 [working-group-definition]: https://github.com/kubernetes/community/blob/master/governance.md#working-groups
 <!-- BEGIN CUSTOM CONTENT -->
+
+### Subproject Leads
+
+SIG network provides some additional responsibilities for subproject leads beyond what is covered in the [standard subproject definition][subprojects].
+Most of these additional responsibilities relate to communication about their projects within SIG Network, and to the greater community:
+
+- **Transparent Project Planning, Maintenance and Communication:**
+  - Subproject Leads must provide transparent view into their historical and future project plans (eg; using GitHub project boards, KEPs, or custom enhancement proposals (see [GEPs]/[NPEPs])).
+  - Subproject leads must create, maintain and be present in a public [Kubernetes Slack] channel with the easy-to-find naming `#sig-network-<subproject>` for their sub-project.
+  - Subproject leads should create and maintain a regular public [Zoom] sync on the [SIG Network Calendar].
+  - Subproject leads must keep the project in good health through regular issue triaging, PR reviews, CI health monitoring and checking testgrids (delegating this to other members in the community is good!)
+  - Projects that own CRDs in the `k8s.io` group must go through the [API review process](https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md) and Subproject leads are expected to make sure this well defined processes across Kubernetes is followed.
+
+- **Regular Project Updates**
+  - Subproject leads must report on project's status, significant releases/events, interesting developments to the wider SIG-Network community via the [SIG Network Mailing List] on a quarterly basis (or as needed).
+  - Subproject leads should report on project status in the general SIG Network community meetings (in addition to mailing list updates).
+
+[subprojects]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
+[GEPs]: https://github.com/kubernetes-sigs/gateway-api/blob/main/geps/overview.md
+[NPEPs]: https://github.com/kubernetes-sigs/network-policy-api/blob/main/npeps
+[Kubernetes Slack]: https://kubernetes.slack.com
+[Zoom]: https://zoom.us
+[SIG Network Calendar]: https://github.com/kubernetes/community/tree/master/sig-network#meetings
+[SIG Network Mailing List]: https://groups.google.com/g/kubernetes-sig-network
+
 ## Areas of Responsibility
 
 SIG Network is responsible for the following Kubernetes subsystems: