---
# System prepended metadata

title: '2021-01-26 CNF WG Governance, Roles, Responsibilities'

---

# 2021-01-26 CNF WG Governance, Roles, Responsibilities

References:
- [2021-01-25 "Call for CNF WG Self Nominated Chairs" email draft for mailing list](https://hackmd.io/gKmjeV3zQA-zqmR0yf1HDQ?edit)
- [TOC SIG Formation](https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#sig-formation-leadership-and-membership-composition)
- [TOC SIG Roles](https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#sig-member-roles)
- [SIG Security Governance Roles](https://github.com/cncf/sig-security/blob/master/governance/roles.md#role-of-chairs)


# Planning roles


## 2021-02-04

How many Chairs (eg. admins)
- :heavy_check_mark: 3 with equal representation
> [name=Bill] get it done. fits TOC.
> [name=Taylor] +1 especially with tech leads as another option
- 4 with a minimum of 1 from each of the 3 communities
- 5 with minimum of 1 from each of the 3 communities
- ref:
    - 3 listed for [toc sig formation](https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#sig-formation-leadership-and-membership-composition)
    


How many tech leads?
- limit
    - 3, 5?
- :heavy_check_mark: no limit
> [name=Bill] matches toc. 
> [name=Taylor] we can limit later as needed. open up tech lead since chairs are limited
- ref:
    -  no specific number. multiple listed [toc sig formation](https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#sig-formation-leadership-and-membership-composition)


Pull requests:
- :heavy_check_mark: individual
    - roles and responsibilities
    - election process
    - nominations (could be pat of election process or stand alone)
- both in 1 PR

How will people be nominated?
- :heavy_check_mark: self nomination
- nominate others
- both

Required before Monday, Feb 8th?
- :heavy_check_mark: roles and responsibilities




## 2021-01-26 initial draft of CNF WG Governance, Roles, Responsibilities


What to cover
- roles and responsibilities
- elections



# DRAFTS


Draft based on https://github.com/cncf/sig-security/blob/master/governance/roles.md#role-of-chairs https://github.com/cncf/sig-security/blob/master/governance/roles.md#role-of-chairs

## CNF WG Member Roles


### Chairs

Role of the CNF WG Chairs

The CNF WG will be co-chaired by 3 people: at least one co-chair from the Kubernetes (K8s) Community, one from the Service Provider (SP) Community and one from the CNF Developer (Dev) Community to have equal representation.
- *Primary role of Chairs is to run operations and the governance of the group.*
- The Chairs are responsible for ensuring that group meetings are planned and facilitated effectively, while also engaging group members in leadership roles. Effective facilitation includes (but is not limited to) the following activities:
    - setting the agenda for meetings
    - extending discussion via asynchronous communication to be inclusive of members who cannot attend a specific meeting time
    - scheduling discussion of proposals that have been submitted
    - asking for new proposals to be made to address an identified need
    - partnering with Technical Leads to establish a roadmap and manage ongoing projects

### Tech Lead


CNF WG has multiple tech leads who are recognized as (1) experts in the Networking, Telco, Kubernetes, and/or Cloud Native domains, (2) leaders of projects in these domains, and (3) demonstrating the ability to provide the balanced technical leadership required to produce the required unbiased outputs of the CNF WG. The reason for having separate chair and tech lead roles is to allow responsibility for primarily administrative functions to be separated from deep technical functions and associated time commitments and skill sets. Where appropriate, an individual may perform both roles as shown in CNF WG member roles.

Tech leads are primarily focused on the technical execution of the working group's activities including:
- Leads projects in the working group’s area. For example, building out a use case or developing a best practice.
- Has the time and ability to perform deep technical dives on projects.


### Everyone else (eg. other members)

Membership is self-declared.

There are no membership requirements to be a part of the CNF WG. This is an open public working group welcoming anyone who would like to help.

All members
- May either have no explicit roles or responsibilities, or formally assigned roles (see above).
- May not create the impression that they have any authority or formal responsibilities in the CNF WG other than assigned roles.

<--
See [CONTRIBUTING](CONTRIBUTING.md) documentation for more information how to get involved.
-->



---

ARCHIVE / OTHER


## Option based on https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#sig-formation-leadership-and-membership-composition 

CNF WG Roles
---
### Chairs

The CNF WG will be co-chaired by 3 people: one co-chair from the Kubernetes (K8s) Community, one from the Service Provider (SP) Community and one from the CNF Developer (Dev) Community to have equal representation.
- Three chairs where the active chair rotates each week/fortnight/month.
- Primarily performs administrative functions including collecting and compiling topics for the (bi)weekly agenda, chairing the meeting, ensuring that quality meeting minutes are published, and follow-up actions tracked and resolved.
- A chair role may be held and performed by a tech lead, in cases where one person has the time and ability to perform both roles.

### Tech Lead
- Leads projects in the working group’s area.
- Has the time and ability to perform deep technical dives on projects. Projects may include formal CNCF projects or other projects in the area covered by the SIG.

---