Comments (4)
To be explicit about a current issue; as of last week, I am now an employee of the CNCF.
We DO have policies in place around maximal representation, and my employer does not technically run afoul of that. However, there is potentially a greater level of CoI as there is a direct project-level relationship with the CNCF.
In addition to maximal representation policy, we do have some guidance for voting abstention or as a worst case scenario a no confidence vote.
Is this enough? should we make a CoI policy more explicit? or some policy around CNCF employment? I am also happy to bow out of the discussion until there is some sort of consensus.
from steering.
Disclaimer: While I do sit on the CNCF Governing Board as a representative for the Kubernetes project, the following represents my thoughts as a community member and not that of the foundation or it's board.
Individuals elected to project leadership roles such as the Steering Committee are just that -- individuals. We don't represent our employers. This value is so important to us, we enshrine it in our values document.
It's not that our employers don't have a vested interest in the project; they do and should. But we as individuals agree to set those interests aside when making leadership decisions for the project to ensure that we are making decisions for the good of the community and project as a whole, and not to advance the interests of any specific employer.
To the specifics at hand here:
- In accordance with our values, I trust the members of the Steering Committee to be able to set the interests of their employer aside and represent the community.
- In the case that an issue comes up related to their employer where they are unable to avoid a direct or perceived conflict of interest, I trust that the impacted members of the Steering Committee would abstain on that issue no matter who the employer is.
- In the case that the other the members of the Steering Committee feel differently on an issue than a specific member does, I trust that each member will vote their conscious. We have an explicit maximal representation policy to ensure that no employer (the CNCF included) can force a vote to go a certain way.
- Lastly, in either the course of working at a company, or leading an open source project, there may be times where someone has knowledge of non-public information that shouldn't be shared outside of the context in which it was learned. For example, internal company information around future plans, or project information such as private Steering Committee discussions. In the case employer information is improperly shared with the project, I expect this would be investigated by said employer and the person involved would face disciplinary consequences. And in the case that private project information is improperly shared with folks not on the Steering Committee, I would personally view that breach of trust very seriously and the Steering Committee has mechanisms (up to and including a vote of no confidence) in order to repair such a breach.
Basically, the conclusion I personally arrived to in my head is that the mechanisms we have seem to cover all the bases here around potential conflicts. While the relationship between the project and the CNCF may feel unique in comparison to other employers, the test of a good/just/fair policy is that even when applied to novel situations, the policy holds up to scrutiny.
from steering.
/committee steering
from steering.
Individuals elected to project leadership roles such as the Steering Committee are just that -- individuals. We don't represent our employers. This value is so important to us, we enshrine it in our values document.
This. And as mentioned repeatedly above, aside from abstention in any somehow dubious topic, in the case that we somehow fail to uphold this, we structurally have maximal employer representation and no confidence mechanisms to make it impossible for any one employer to throw a steering vote anyhow.
Working for the CNCF is a new one for sure, but we already set out to prevent employers from forcing votes and we already expect that our members are democratically elected by the community to uphold our values, "Community over product or company" is very core to the project to me and I think to most, if not all, of the voters.
If there's any gaps in the governance we should address them, but I don't think there are any in this particular case.
I think we've already been quite proactive and forward thinking on this subject, the foundation and steering exist in no small part to ensure that ~neutral space.
I personally don't even see employers forcing steering votes as particularly likely, but just in case and to ensure if nothing else that there's no room to even suspect that such a subversion happened, we have the maximal representation (and a sufficiently large body) and no confidence governance rules in place already.
IMO - even if it is determined that no changes are needed, I'd lean towards moving the section regarding maximal representation from the election doc to the charter. That might be a separate issue to discuss, but I think adding a note about it in the general steering composition section would be good move.
I would compromise: I think it's important that the specific handling of this is maintained in the election doc, but we should mention it in the general charter with a link to the elections subsection for the exacting details because it's also important that we highlight this This whole ecosystem thrives off of working together across organizations and I think it's vital that we make this visible.
from steering.
Related Issues (20)
- Community Annual Report Feedback HOT 14
- DMARC failing on kubernetes.io HOT 11
- checklist for publishing '21 annual reports summary HOT 3
- Iterate on charter changes around committee membership/elections HOT 6
- Steering onboarding - @mrbobbytables, @palnabarun, @BenTheElder HOT 9
- Formalize SC Visa Support Letters HOT 5
- Collect usage metrics for minikube HOT 13
- Steering member transition: @parispittman --> @cpanato HOT 5
- Document private communication channels HOT 6
- celebrating orgs with full time maintainers HOT 5
- Logo for Kueue, subproject of SIG Scheduling HOT 17
- V2 Contributor Badge HOT 27
- Election Officers for 2023 for Approval HOT 9
- Document rule around CoCC and SC HOT 2
- Update Steering members following 2023 election cycle HOT 3
- Logo for Jobset, subproject of SIG Scheduling HOT 4
- DMCA Takedown for "Ingress" docs HOT 5
- Include SIG Leads as voting CNCF Maintainers HOT 21
- Proposal: Enable gitvote for steering repo HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from steering.