Skip to content
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

establish conflict of interest guidelines #270

Closed
ultrasaurus opened this issue Aug 1, 2019 · 4 comments
Closed

establish conflict of interest guidelines #270

ultrasaurus opened this issue Aug 1, 2019 · 4 comments
Assignees

Comments

@ultrasaurus
Copy link
Member

Clear conflict of interest guidelines can mitigate the risk that there is real or perceived bias and accelerate the work of the SIGs, supporting TOC "No Kingmakers" principle.

The CNCF TOC relies on TOC Contributors and SIG (previously Working Groups) for technical analysis and project review that informs decisions. Almost all of the individuals who do the work are employees by a company who benefits from the Cloud Native ecosystem, and TOC decisions can positively or negatively affect business outcomes. This creates potential issues:

  1. individuals could intentionally or unintentionally promote their own company's project
  2. CNCF decision-makers could intentionally or unintentionally limit the participation of an individual unfairly by asserting conflict of interest
  3. projects can get stalled while groups discuss whether this person or that person should be allowed to participate

This would help SIG members to comply with the responsibility to be unbiased:

"It is of utmost importance that the information and proposals provided to the TOC by SIGs be highly accurate and unbiased, driven by the goal to improve the CNCF as a whole, rather than benefit one project or company over another. We believe that the rising tide lifts all boats, and that is our goal." -- SIG Responsibilities

@jbeda
Copy link
Contributor

jbeda commented Aug 1, 2019

Sounds good to me. There is always gray here but this sounds like a good start. Regardless we want to make sure that there are outside eyes on any projects/info/evaluation.

@dims
Copy link
Member

dims commented Aug 4, 2019

IEEE seems to distinguish between Employment and Affiliation ( https://standards.ieee.org/faqs/affiliation.html ) probably too much for us..

@ultrasaurus
Copy link
Member Author

FYI: SIG-Security has established conflict of interest guidelines for security reviewers (with discussion in PR cncf/tag-security#125)

Writing something down helps streamline our process. We're happy to adjust anything, as needed, whenever CNCF TOC decides to move forward with more general guidance.

@amye
Copy link
Contributor

amye commented Dec 14, 2021

Closing, this can be reopened if there's still outstanding issues.

@amye amye closed this as completed Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants