search

kubernetes / steering

The Kubernetes Steering Committee
Apache License 2.0
86 stars 61 forks source link

2019 Steering Committee Election Retro #140

Closed nikhita closed 4 years ago

nikhita commented 5 years ago

The election officers for the 2019 Steering Committee Election created a retro doc - https://docs.google.com/document/d/1La9ZJPdvgLRzVH_RvE3Tmmx7uw_de8x8Ca4HoCkH8R0/edit.

The crossed out points are already addressed (most of them in https://github.com/kubernetes/community/pull/4148). This is a tracking issue to make sure that all other points in the doc don't get lost.

The following points from the retro doc still need to be addressed. Details about each point can be found in the doc.

/cc @mrbobbytables @castrojo @idvoretskyi @bgrant0607

mrbobbytables commented 5 years ago

/assign So I don't lose track + I can work on some of the items (release style timeline etc).

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

mrbobbytables commented 4 years ago

/remove-lifecycle stale

I'll bump this back up on the todo list.

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

castrojo commented 4 years ago

/close

Had a long discussion with Josh about this, the important changes have been made already. We have open items that are improvements to the email/CIVS process, but after some discussion it's clear that a github integrated application that implements a condorcet voting model is the way forward and not improving the CIVS methods. We're doing decent with what we have now and hyper optimizing this method isn't an efficient use of time.

We need to sync with the CNCF on perhaps speccing out a generic simple app that implements this and removing the email requirements entirely, this would remove a ton of complexity. This is also something that could easily be consumed by the rest of the cloud native landscape. I'll file issues for that in the appropriate places.

k8s-ci-robot commented 4 years ago

@castrojo: Closing this issue.

In response to [this](https://github.com/kubernetes/steering/issues/140#issuecomment-672002451): >/close > >Had a long discussion with Josh about this, the important changes have been made already. We have open items that are improvements to the email/CIVS process, but after some discussion it's clear that a github integrated application that implements a condorcet voting model is the way forward and not improving the CIVS methods. We're doing decent with what we have now and hyper optimizing this method isn't an efficient use of time. > >We need to sync with the CNCF on perhaps speccing out a generic simple app that implements this and removing the email requirements entirely, this would remove a ton of complexity. This is also something that could easily be consumed by the rest of the cloud native landscape. I'll file issues for that in the appropriate places. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
castrojo commented 4 years ago

Follow up issue: https://github.com/cncf/sig-contributor-strategy/issues/51