Community: 2019 Steering Committee Election Kick Off

[parispittman]

please do not use this issue as official election documentation, announce your candidacy, or anything else related. this issue is the operations behind those processes.

Knowns:
The Steering Committee will reduce to 7 seats October 2019.
4 seats will be up for election.
dims, timothysc, and spiffxp will carry out another year.

• [x] Steering Committee to set Election Officials per https://git.k8s.io/community/events/elections. I'm recommending @idvoretskyi (cncf, previous official), @mrbobbytables (approver in events folder), and a third TBD. I'm happy to take a step back for another or step into the official role again.

• [x] Steering Committee to define members in standing (who can vote)

• [x] SC and Election Officials to review steering committee process doc. PR in any suggested changes before election announcements start.

• [x] Once election officers are set, they create a timeline. If we go with last years cadence, it will look something like this:

_August (dates/times shown are PT)_
Third Tuesday (20th) - election announcement: eligible voters, exception process for those not listed as eligible, and a request for nominations

_September_
Second Friday (13th) - all candidate bios / statement of intent is due. also, all voting exceptions are due.
Third Wednesday (18th) - voting begins; voters sent poll via email for selection

_October_
First Wednesday (2nd) - voting ends; poll closed and votes are tallied. Election Officials send results to current Steering Committee.
First Thursday (3rd) - results are announced in weekly community meeting by a steering committee member

• [x] Put together a communication channel strategy and prepare to start. Update this issue with list of channels.

Phase 1 issue will include election official tasks such as voter exception form, copy for announcement, and working with devstats to pull official email list of voters.

[markyjackson-taulia]

@parispittman For the 3rd slot, Is it possible to have a shadow or possibly a person to shadow on of the others you have recommended?

[parispittman]

@markyjackson-taulia unsure honestly. I'd rather have the SC weigh in on the election officials first and then discuss shadow topics.

[castrojo]

I'm happy to take a step back for another or step into the official role again.

Same with me!

[smarterclayton]

Since this is a fairly big turnover / change, I would definitely feel like we should create the perception of continuity experience wise. I think it might make sense to have at least two officials from previous involved (with one new and one training)? I'd want to bias towards perception of continuity of institution even as we dramatic reshape the SC.

[dims]

+1 to @smarterclayton 's observation

[dims]

/cc

[castrojo]

The rotation we wrote up in the docs as a recommendation always allows for at least 2 people's worth of continuity. A total three election officers, one brand new person, one person from the year before, and one person with 2 years experience on a rotational basis. Right now this would work out work out as:

mrbobbytables: first year
ihor: this would be his 2nd year
paris/jorge: this would be our third year

Ideally every year we bring in a new person and another retires. We have enough people in contribex with long-standing membership status where this shouldn't be a problem, one person comes in every election and one moves to emertius, and the middle person is the bridge. Since this is a high turnover election Paris and I could once again split the role, allowing for next year to look like:

one new person
mrbobbytables's 2nd election
ihor's 3rd election

And then Paris and I emeritus and/or kick back to the new person role, but ideally new folks volunteer and get involved.

[idvoretskyi]

+1, that works.

On Fri, Jul 26, 2019 at 7:05 AM Jorge O. Castro [e-mail]
wrote:

The rotation we wrote up in the docs as a recommendation always allows for
at least 2 people's worth of continuity. A total three election officers,
one brand new person, one person from the year before, and one person with
2 years experience on a rotational basis. Right now this would work out
work out as:

mrbobbytables: first year
ihor: this would be his 2nd year
paris/jorge: this would be our third year

Ideally every year we bring in a new person and another retires. We have
enough people in contribex with long-standing membership status where this
shouldn't be a problem, one person comes in every election and one moves to
emertius, and the middle person is the bridge. Since this is a high
turnover election Paris and I could once again split the role, allowing for
next year to look like:

one new person
mrbobbytables's 2nd election
ihor's 3rd election

And then Paris and I emeritus and/or kick back to the new person role, but
ideally new folks volunteer and get involved.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/community/issues/3915?email_source=notifications&email_token=AAA45O6Y7LAZVJID7BDMXYTQBJZ2PA5CNFSM4IFZ4XM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD23N3OI#issuecomment-515300793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA45O37E3Y3OTKB47PSL73QBJZ2PANCNFSM4IFZ4XMQ
.

--
Ihor Dvoretskyi [e-mail]
Developer Advocate, Cloud Native Computing Foundation https://cncf.io/

[dims]

Sounds like good plan @castrojo

[castrojo]

Next step: We'll need SC to do the appointments and finalize what the voting criteria is for this election. In the last election was 50 github contributions in the org and then write ins for exemptions.

[castrojo]

As per the meeting, steering needs to explicitly name: @castrojo @parispittman @mrbobbytables and @idvoretskyi as election officers.

[bgrant0607]

Just noting that the PR with this info is here:
https://github.com/kubernetes/community/pull/3991

I will be an additional election officer, while Paris will not be.

Dates:
21 August - Announce Election - first thing in the morning EST, this is
just sending an email
11 Sept - All bios and voting exemptions due - 5pm PST
18 Sept - Voting begins - "Morning of" to account for CIVS setup
2 October - Voting ends - 5pm PST
3 October - Results published on blog/community meeting - Normal
community meeting time, blog published right after.

[mrbobbytables]

Thanks @parispittman for getting this together. :)

With the election well under way, closing in favor of the tracking issue #4118

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

Thanks @parispittman for getting this together. :)

With the election well under way, closing in favor of the tracking issue #4118

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.