Skip to content

Committee Conflict of Interest resolution (Steering's version) - #272

Open
justaugustus wants to merge 2 commits into
kubernetes:mainfrom
justaugustus:coi
Open

Committee Conflict of Interest resolution (Steering's version)#272
justaugustus wants to merge 2 commits into
kubernetes:mainfrom
justaugustus:coi

Conversation

@justaugustus

Copy link
Copy Markdown
Member

Fixes #221.
/hold for merge of kubernetes/community#7468

Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 16, 2023
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 16, 2023

@nikhita nikhita left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm as elections subproject owner

Would like a review from @jberkus though
/assign @jberkus

@k8s-triage-robot

Copy link
Copy Markdown

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 21, 2024

@BenTheElder BenTheElder left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 16, 2025
@BenTheElder

Copy link
Copy Markdown
Member

/lgtm cancel
Can we drop the bit referencing the retracted kubernetes/community#7468 and land the rest of these cleanups?

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 16, 2025
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus, nikhita

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Comment thread elections.md
Steering committee members who intend to run for re-election _may_
self-nominate but are otherwise expected to adhere to this recusal.

[committee-coi]: https://git.k8s.io/community/elections/committee-conflict-of-interest.md

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does no exist, should it?

@vitrixLab vitrixLab Jul 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding the conflict of interest guidance to the Steering Committee election process.

From a contributor perspective, having this documented here is helpful because election candidates may not always be familiar with the expected recusal process or how conflicts are evaluated during the election cycle.

One thing that may be worth clarifying is the source of truth for the COI policy. The current reference appears to point to community/elections/committee-conflict-of-interest.md, but that document does not seem to exist anymore.

Would it make sense to either:

update the reference to the current COI policy location, or
include a short explanation directly in the election guide describing the expected recusal process for candidates and existing Steering Committee members?

This would make the election process easier to follow for contributors who are participating for the first time.

@vitrixLab

Copy link
Copy Markdown

It might also be useful to clarify whether the COI recusal applies only during election activities or also during Steering Committee decision-making after election.

Having that distinction explicit would help contributors understand the boundary between campaign participation and committee responsibilities.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

Resolving conflicts of interest with committee membership

8 participants