New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steering committee elections 2018 #63

Open
quinton-hoole opened this Issue Jul 18, 2018 · 17 comments

Comments

8 participants
@quinton-hoole
Member

quinton-hoole commented Jul 18, 2018

Draft timeline:

  • Election results announced - early Oct 2018? (‘t’)
  • Open for votes - t-2 weeks?
  • Announce who may vote (and allow exception applications) - t-4 weeks?
  • Candidate bio distribution deadline - t-4 weeks?
  • Candidate solicitation - t-6 weeks?
  • Sounds like we need to kickstart the process ~early Aug (t-8 weeks).
@timothysc

This comment has been minimized.

Show comment
Hide comment
@timothysc
Member

timothysc commented Jul 19, 2018

@castrojo

This comment has been minimized.

Show comment
Hide comment
@castrojo

castrojo Aug 1, 2018

Contributor

I would recommend starting the process next week. Last time we added a ton of padding to ensure we had enough time to write up a voter's guide, an election process, investigate CIVS, etc. This time we have all of that and we purposely future proofed the documentation. This has the steps and duties of everyone needed to start an election:

https://github.com/kubernetes/community/tree/master/events/elections#steering-committee

I would say the top 3 things for the SC to deal with are:

1 - Selection of election officers. Last time we had two. I would like to add a third so we can have a a new shadow. I would be happy to serve in this role again if asked.
2 - Exact date selection, Quinton's schedule seems fine to me.
3 - Select criteria for Kubernetes Members of Standing

Last election we kept it loose, it was basically "Mail Tim and he'll add you to a sheet." Paris and I then checked each contributor to see if they had k8s contributions. This time we should for sure leverage devstats to include the obvious ones, and then make the selection process more of an exception handler than checking each one. We don't yet have exact wording for sustained contributions to Kubernetes and how that affects membership, but I can help with that wording/process.

Contributor

castrojo commented Aug 1, 2018

I would recommend starting the process next week. Last time we added a ton of padding to ensure we had enough time to write up a voter's guide, an election process, investigate CIVS, etc. This time we have all of that and we purposely future proofed the documentation. This has the steps and duties of everyone needed to start an election:

https://github.com/kubernetes/community/tree/master/events/elections#steering-committee

I would say the top 3 things for the SC to deal with are:

1 - Selection of election officers. Last time we had two. I would like to add a third so we can have a a new shadow. I would be happy to serve in this role again if asked.
2 - Exact date selection, Quinton's schedule seems fine to me.
3 - Select criteria for Kubernetes Members of Standing

Last election we kept it loose, it was basically "Mail Tim and he'll add you to a sheet." Paris and I then checked each contributor to see if they had k8s contributions. This time we should for sure leverage devstats to include the obvious ones, and then make the selection process more of an exception handler than checking each one. We don't yet have exact wording for sustained contributions to Kubernetes and how that affects membership, but I can help with that wording/process.

@parispittman

This comment has been minimized.

Show comment
Hide comment
@parispittman

parispittman Aug 1, 2018

+1 to what Jorge said. IMO, the members in standing voting requirements should be the first decision to be made since that will kick off other process and possibly some that we haven’t done before. I can provide some devstats dashboard examples and possibly have one custom made depending on what you are looking for.

Happy to help with this.

parispittman commented Aug 1, 2018

+1 to what Jorge said. IMO, the members in standing voting requirements should be the first decision to be made since that will kick off other process and possibly some that we haven’t done before. I can provide some devstats dashboard examples and possibly have one custom made depending on what you are looking for.

Happy to help with this.

@quinton-hoole

This comment has been minimized.

Show comment
Hide comment
@quinton-hoole

quinton-hoole Aug 1, 2018

Member

Thanks. I believe that @timothysc has such a dashboard already, and a proposed cutoff line score. @parispittman just to clarify, are you willing to be an election officer? In that case we have two volunteers, and ideally need to solicit a third. Could you and George find a third, ideally from a third company?

There is a steering committee meeting today, where I'll make sure that the committee is OK with the above proposal, and the election officers should go ahead as described above. Given that I'll be standing in the election, I'll bow out from involvement after that.

Member

quinton-hoole commented Aug 1, 2018

Thanks. I believe that @timothysc has such a dashboard already, and a proposed cutoff line score. @parispittman just to clarify, are you willing to be an election officer? In that case we have two volunteers, and ideally need to solicit a third. Could you and George find a third, ideally from a third company?

There is a steering committee meeting today, where I'll make sure that the committee is OK with the above proposal, and the election officers should go ahead as described above. Given that I'll be standing in the election, I'll bow out from involvement after that.

@timothysc

This comment has been minimized.

Show comment
Hide comment
@timothysc

timothysc Aug 3, 2018

Member

3 - Select criteria for Kubernetes Members of Standing

@jorge - The general roll'd up activity across the org, cut @ 50-60 for the last year was the general "ok" line that the steering committee thought was a reasonable metric

https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20year&var-metric=contributions&var-repogroup_name=All

/cc @jbeda @spiffxp

Member

timothysc commented Aug 3, 2018

3 - Select criteria for Kubernetes Members of Standing

@jorge - The general roll'd up activity across the org, cut @ 50-60 for the last year was the general "ok" line that the steering committee thought was a reasonable metric

https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20year&var-metric=contributions&var-repogroup_name=All

/cc @jbeda @spiffxp

@spiffxp

This comment has been minimized.

Show comment
Hide comment
@spiffxp
Member

spiffxp commented Aug 3, 2018

@castrojo

This comment has been minimized.

Show comment
Hide comment
@castrojo

castrojo Aug 8, 2018

Contributor

Just a reminder that we're blocking on the membership criteria.

If that's still in progress we can at least move forward with election officers and schedule. @jberkus has shown interest in volunteering and can probably help us wrangle the info we need out of devstats. That would give us our third shadow from three different companies.

Contributor

castrojo commented Aug 8, 2018

Just a reminder that we're blocking on the membership criteria.

If that's still in progress we can at least move forward with election officers and schedule. @jberkus has shown interest in volunteering and can probably help us wrangle the info we need out of devstats. That would give us our third shadow from three different companies.

@quinton-hoole

This comment has been minimized.

Show comment
Hide comment
@quinton-hoole

quinton-hoole Aug 9, 2018

Member

@spiffxp I was the one who said something like "about 100, from memory", which is what ended up in the notes. I think @timothysc 's "50-60" is more accurate, and consistent with the demo given in the meeting. Lets go with 50 over the trailing 12 months, to err on the side of inclusion.

Member

quinton-hoole commented Aug 9, 2018

@spiffxp I was the one who said something like "about 100, from memory", which is what ended up in the notes. I think @timothysc 's "50-60" is more accurate, and consistent with the demo given in the meeting. Lets go with 50 over the trailing 12 months, to err on the side of inclusion.

@timothysc

This comment has been minimized.

Show comment
Hide comment
@timothysc

timothysc Aug 9, 2018

Member

@spiffxp cut line is relatively arbitrary.

Member

timothysc commented Aug 9, 2018

@spiffxp cut line is relatively arbitrary.

@timothysc

This comment has been minimized.

Show comment
Hide comment
@timothysc

timothysc Aug 9, 2018

Member

@castrojo @parispittman - can you please start the ball rolling on elections and pick dates. We need to get a move on this.

/cc @kubernetes/steering-committee

Member

timothysc commented Aug 9, 2018

@castrojo @parispittman - can you please start the ball rolling on elections and pick dates. We need to get a move on this.

/cc @kubernetes/steering-committee

@parispittman

This comment has been minimized.

Show comment
Hide comment
@parispittman

parispittman Aug 10, 2018

Updates

  1. @idvoretskyi is confirmed as 3rd Election Official
  2. Draft schedule

August
15th - election announcement: who is eligible to vote, exception process for those who believe they should have a vote, and a request for nominations

September
14th - all candidate bios / statement of intent is due. also, all voting exceptions are due.
19th - voting begins; voters sent poll via email for selection

October
3rd - voting ends; poll closed and votes are tallied. Election officials
4th - results are announced in weekly community meeting by TBD

Between now and Wednesday of next week:

  • Prepare the voting membership list that has a cut off of 50 or more contributions (already extracted from devstats but need to collect emails from another data source)
  • Update election docs with new and updated details
  • Put together a small marketing campaign strategy and execute

parispittman commented Aug 10, 2018

Updates

  1. @idvoretskyi is confirmed as 3rd Election Official
  2. Draft schedule

August
15th - election announcement: who is eligible to vote, exception process for those who believe they should have a vote, and a request for nominations

September
14th - all candidate bios / statement of intent is due. also, all voting exceptions are due.
19th - voting begins; voters sent poll via email for selection

October
3rd - voting ends; poll closed and votes are tallied. Election officials
4th - results are announced in weekly community meeting by TBD

Between now and Wednesday of next week:

  • Prepare the voting membership list that has a cut off of 50 or more contributions (already extracted from devstats but need to collect emails from another data source)
  • Update election docs with new and updated details
  • Put together a small marketing campaign strategy and execute
@jberkus

This comment has been minimized.

Show comment
Hide comment
@jberkus

jberkus Aug 11, 2018

Wait, what's the process for non-GH contribution claims? Do we already have a spec on that?

If we don't already have a doc on non-GH contributions, I can prepare an spec sheet with example contributions for the SC to approve.

jberkus commented Aug 11, 2018

Wait, what's the process for non-GH contribution claims? Do we already have a spec on that?

If we don't already have a doc on non-GH contributions, I can prepare an spec sheet with example contributions for the SC to approve.

@parispittman

This comment has been minimized.

Show comment
Hide comment
@parispittman

parispittman Aug 12, 2018

@jberkus We will have a form to fill out and send it out to k-dev on the 15th.

parispittman commented Aug 12, 2018

@jberkus We will have a form to fill out and send it out to k-dev on the 15th.

@spiffxp

This comment has been minimized.

Show comment
Hide comment
@spiffxp

spiffxp Aug 15, 2018

Member

I'd like to clear up where the one true copy of election rules should live, ref: kubernetes/community#2542 (comment)

Member

spiffxp commented Aug 15, 2018

I'd like to clear up where the one true copy of election rules should live, ref: kubernetes/community#2542 (comment)

@philips

This comment has been minimized.

Show comment
Hide comment
@philips

philips Aug 15, 2018

Contributor
Contributor

philips commented Aug 15, 2018

@spiffxp

This comment has been minimized.

Show comment
Hide comment
@spiffxp
Member

spiffxp commented Aug 16, 2018

@spiffxp

This comment has been minimized.

Show comment
Hide comment
@spiffxp

spiffxp Aug 29, 2018

Member

The announcement went out https://groups.google.com/forum/#!topic/kubernetes-dev/jXXCL_ilZkQ

As far as I know, our involvement in this is done until it comes time to announce results. Moving this into blocked/waiting

Member

spiffxp commented Aug 29, 2018

The announcement went out https://groups.google.com/forum/#!topic/kubernetes-dev/jXXCL_ilZkQ

As far as I know, our involvement in this is done until it comes time to announce results. Moving this into blocked/waiting

@spiffxp spiffxp moved this from In Progress to Blocked/Waiting in Steering Aug 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment