# 2021-01-25 "Call for CNF WG Self Nominated Chairs" email draft for mailing list

DRAFT:
---

Send to [e-mail]

Subject: Call for CNF WG Co-chair and Tech Lead Nominations

Body DRAFT:
This email will kick-off the nomination period for co-chairs and tech leads. The nomination period will end on Monday, March 8th, 2021.

The CNF WG will be co-chaired by 3 people. We are looking for 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.

The CNF WG tech leads will focus on piloting the discussion on a specific area(s) of the project. There can be as many or as few tech leads as are elected.

To nominate youself for the role of CNF WG co-chair, please send a message to [e-mail] with a brief nomination pitch which includes your name, contact information, the seat you are interested in (ie. K8s, SP or Dev), a supporting statement identifying your experience in a related domain and why you are interested in the position.

To nominate yourself as a tech lead, please send a message to [e-mail] with a brief nomination pitch which includes your name, contact information, which part of the project you would like to be tech lead for, and a supporting statement identifying your experience in a related domain and why you are interested in the position.

TBD:
---
- What are the roles and responsibilities of a chair?
- Who votes?
- How do we vote?

## Elections
Chairs and tech leads will be elected for one year terms and may run for reelection.

The CNF WG employs "organization voting" to ensure no single organization can dominate the project.

Individuals not associated with or employed by a company or organization are allowed one organization vote. Each company or organization (regardless of the number of maintainers associated with or employed by that company/organization) receives one organization vote.

In other words, if two contributors are employed by Company X, two by Company Y, two by Company Z, and one maintainer is an un-affiliated individual, a total of four "organization votes" are possible; one for X, one for Y, one for Z, and one for the un-affiliated individual.

Each organization listed in the interested parties section has one vote. Any contributor from an organization may cast the vote for that organization.

The chair nominee from each community with the most votes will be elected. Tech leads must win at least 60% of the votes cast to be elected.

---

### References found in other CNCF/LF group mailing lists:

### SIG App Delivery Operator WG Chairs
https://lists.cncf.io/g/cncf-sig-app-delivery/message/222

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

**SIG Member Roles**

**Chair**
- 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 to the satisfaction of the TOC and SIG members.

**SIG Formation, Leadership and Membership Composition**
SIGs are formed by the TOC. Initial SIGs are listed in proposed SIGs, and will be adapted over time as required. If members of the community believe that additional SIGs are desired, they should propose these to the TOC, with clear justification, and ideally volunteers to lead the SIG. The TOC wishes to have the smallest viable number of SIGs, and for all of them to be highly effective (as opposed to a "SIG sprawl" with large numbers of relatively ineffective SIGS).
SIG has three co-chairs, who are TOC Contributors, recognized as experts in that area, and for their ability to co-lead the SIG to produce the required unbiased outputs.

### https://github.com/cncf/sig-security/blob/master/governance/roles.md#role-of-chairs
Role of chairs
While CNCF TOC allows for Chairs to serve in purely administrative roles, SIG-Security was formed with deeply technical Chairs based on early need to navigate a complex security landscape. If the SIG has less than two Technical Leads, any Chair may act as Technical Lead.

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

### Governance Update and Call for Co-chair Nominations

>
Fatih Degirmenci2/03/20 #8
Hi,
>
> As discussed during the previous SIG meeting, SIG Governance topic has been brought up to TOC's attention during TOC meeting on 2020-01-28. [0][1]

> Until the topic is clarified by TOC, we can introduce a lightweight governance, starting with adoption of co-chair setup similar to other CDF SIGs as agreed during the previous SIG Meeting.
>
> What this means is that SIG Interoperability will be co-chaired by 3 people so we are looking for 2 additional co-chairs, one from user community and one from project community to have equal representation.
>
> With this mail, I would like to kick-off the nomination period for co-chairs. Please respond to this mail if you would like to nominate yourself or someone else. Please note that if you nominate someone else, the nomination needs to be accepted by nominee. The nomination period will end on 2020-02-10.
>
> Please also note that Christie Wilson and Wavell Watson have been nominated by others during the SIG meeting and we need their acceptances.
> [1]
>
> [0] https://docs.google.com/document/d/13hCBpmuAj3e0gADo1TCjsEwmz57_fw74OhQmeY1extk/edit#heading=h.3ub7vmz2qqtp
> [1] https://docs.google.com/document/d/1uBHar55fTInWF9Li4t0lyG3tTC8BRLU0FfBfsgk_Jrs/edit?ts=5c9580be#heading=h.i9mltyild8ii
>
> /Fatih

See online:
- https://lists.cd.foundation/g/sig-interoperability/topic/governance_update_and_call/70948967?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,40,70948967

### https://www.cncf.io/blog/2019/12/13/faq-for-december-2019-toc-nominations/

FAQ for December 2019 TOC Nominations

> How many seats?
>
> There are 5 seats to nominate: 3 from the Governing Board (GB), 1 from the end user community, 1 from the maintainers of Graduating + Incubating projects. The GB-elected seats are currently held by Joe Beda, Liz Rice, and Alexis Richardson. The other two seats have newly been added. These are the Selecting Groups and will be voting on the nominees after qualification.
>
> How long do we have?
>
> You have 9 days to be able to nominate candidates from December 12 through December 20th.
>
> We’ve extended the nomination deadline to January 4, 2020 at 12pm Pacific.
>
> How do I get nominated?
>
> If you are a maintainer of a graduated or incubating project, you can self-nominate, as explained below. Otherwise, you can ask a governing board member or end-user representative to nominate you.
>
> The charter (section 6(e)(i)) says: “Each individual in a Selecting Group may nominate up to two (2) people, at most one (1) of whom may be from the same group of Related Companies. Each nominee must agree to participate prior to being added to the nomination list.”
>
> How do maintainers get nominated?
>
> Maintainers self-nominate by sending an email to [e-mail]. They need to be endorsed (prior to the December 20th deadline) by two other maintainers from other projects and other companies (so, each nomination will, including the two endorsements, cover 3 projects and 3 companies). Details are in the new Maintainer Election Policy.
>
> Why is the maintainers process different?
>
> The Governing Board approved this new process to encourage broader representation.
>
> What should go in a nomination?
>
> Section 6(e)(i)(a) of the charter says: “A nomination requires a maximum one (1) page nomination pitch which should include the nominee’s name, contact information and supporting statement identifying the nominee’s experience in CNCF domains.”
>
> Do the GB and End User nominations need endorsements?
>
> Not this election, but if this new endorsements policy works for the maintainer seat, it may be expanded.
>
> What is the evaluation and qualification process?
>
> The Charter (section 6(e)(i)(c)) says: “A minimum of 14 calendar days shall be reserved for an Evaluation Period whereby TOC nominees may be contacted by members of the Governing Board and TOC.” Section 6(e)(ii) says: “After the Evaluation Period, the Governing Board and the TOC members shall vote on each nominee individually to validate that the nominee meets the qualification criteria. A valid vote shall require at least 50% participation. Nominees passing with over 50% shall be Qualified Nominees.”
>
> Is the evaluation and qualification process the same for all nominees?
>
> Yes.
>
> Who votes?
>
> The Governing Board (GB) will vote for 3 seats, the end user community for 1 seat, and the maintainers of Graduating + Incubating projects for 1 seat. These are the Selecting Groups and will be voting after the qualification process.
>
> Can you tell me more about the end-user community votes?
>
> Each end user member in CNCF has a primary representative that has voting rights.

---

### https://github.com/cncf/sig-security/blob/master/governance/chair-proposal-process.md

---

### [cncf-toc] [TOC] Nominations Open through 12pm PT, January 11, 2021

- Amye Scavarda Perrin [e-mail] via lists.cncf.io
- Mon, Dec 14, 2020, 2:02 PM
> 5 seats are open for nomination by the GB and End User Community.
> Nominations are open for the two Selecting Groups.
>
> We will be publishing the list of qualified nominees at the end of the qualification process.
>
> Timeline:
> December 14: Nominations open – 12 PM PT
> January 11: Nominations close - 12 PM PT
> Jan 11: Qualification period opens
> Jan 25: Qualification period closes
> Jan 25: Election opens, Voting occurs by a time-limited Condorcet-IRV ranking in CIVS
> Feb 1: Election closes at 12pm Pacific, results announced

---

[cncf-toc] [TOC] Nominations Open through 12pm PT, December 20th, 2019
---

- Amye Scavarda Perrin [e-mail] via lists.cncf.io
- Thu, Dec 12, 2019, 2:03 PM

> As part of the updates to the TOC approved by the Governing Board, five seats are open for nomination by the GB, End User Community and Graduating + Incubating Maintainers. Nominations are open for the three Selecting Groups.
>
> We will be publishing the list of qualified nominees at the end of the qualification process.
>
> Timeline:
> December 12: Nominations open – 12 PM PT
> Dec 20: Nominations close (last day of business before holiday) – 12 PM PT
> Jan 6: Qualification period opens
> Jan 20: Qualification period closes
> Jan 20: Election opens, Voting occurs by a time-limited Condorcet-IRV ranking in CIVS
> Feb 1: Election closes
> Feb 3: Election results posted

---

### https://groups.google.com/u/1/g/kubernetes-dev/search?q=chair

### Subject: Steering Committee Nomination: Davanum Srinivas (@dims)
> Davanum Srinivas <[e-mail]>
> Tue, Sep 1, 2020, 2:32 PM
> to Kubernetes
>
> Hi Folks,
>
> I would like to self-nominate myself for one more turn on the Kubernetes Steering Committee as my turn ends in Oct. I thought long and hard on what this means, especially the tradeoffs and finally decided to put my hat in the ring. It's been a blast working with you all and it will be a pleasure serving you again if chosen.
>
> Thanks,
> @dims (VMware)

---

### https://github.com/cncf/foundation/blob/master/maintainers-election-policy.md
> Maintainer Nomination
To nominate themselves for an open position, a graduated or incubating maintainer needs to send an email to the private list [e-mail] prior to the announced deadline with a maximum 1-page nomination pitch which includes the nominee's name, contact information, and a supporting statement identifying the nominee's experience in CNCF domains and interest in the position. The nominee needs to cc (i.e., copy) 2 other maintainers from 2 different graduated or incubating CNCF projects who each need to group reply endorsing the nomination. The 2 endorsers also need to be employed by different companies than the nominee and each other (i.e., the nominee and endorsers must each work for a different group of Related Companies as defined in the CNCF Charter section 14). It is the nominee’s responsibility to ensure that their nomination and both endorsements are sent prior to the deadline.

---