search

kubernetes / steering

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

Iterate on charter changes around committee membership/elections #250

Closed justaugustus closed 1 year ago

justaugustus commented 2 years ago

Problem Statement

https://github.com/kubernetes/steering/pull/248 and https://github.com/kubernetes/steering/pull/249 propose charter changes related to the elections process and committee membership.

In presenting these changes, we've received a lot of useful feedback that would likely be best handled in separate PRs.

Proposed Solution

Cost

If you are requesting funding please file requests issues here , otherwise please add any associated costs with your request if it is applicable.

Open Questions

Next Steps

Other Considerations, Notes, or References

jberkus commented 2 years ago

One follow-up is "how we replace empty seats" which needs further development beyond what we've already merged.

jberkus commented 2 years ago

Second task (for the Elections Subproject): create the rules for conducting a special election, including how EOs are chosen and timelines.

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/steering/issues/250#issuecomment-1345646915): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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.