community

community copied to clipboard

Per @parispittman proposal during SIG-Contribex meeting today:

New Subproject: Elections, SIG-Contribex

The elections subproject would own:

• Recruiting and proposing the Election Committee for the annual Steering elections
• Supporting SIGs and committees in using elections.k8s.io to run other elections for their group (starting in 2022)
• The elections.k8s.io app, shared with SIG-Infra, including /k8s.io/apps/elekto
• A new /elections directory in this repository (historical elections would be moved there)
• Documentation on running elections, and maintenance of that documentation
• /area/elections label (#6083)

It is also possible that this could just be a named role, and not a subproject, but Elections seems to own enough things to make it a de-facto subproject.

Discuss? If we want to do this, I'll write up a full charter.

/sig contributor-experience

/area elections

+1

this would be extremely useful and a good way to organize this work

related: #4586

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

/remove-lifecycle stale

/assign @nikhita @cblecker

FYI: this is mainly waiting on me to do all the directory re-arranging as a PR. That's more complicated than it sounds because moving the elections directory affects our running instance of Elekto.

@jberkus we still need a TL to approve the concept

Ah, point. Well, no rush.

No objections from me.

@nikhita thoughts?

+1

cc @kubernetes/steering-committee - no action needed, just fyi.

cc @mrbobbytables @alisondy

lgtm from me - it was one of the big things to come out of the retro.

@jberkus you're clear to proceed :)

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

this is still planned.

/remove-lifecycle stale

This is created.

/close

@jberkus: Closing this issue.

In response to this:

This is created.

/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.