Open Source

Why Open Source Inclusion Requires Real Codes of Conduct | Kat Cosgrove, Minimus

0

Guests: Kat Cosgrove | Billy Thompson
Companies: Minimus |Akamai
Show Name: KubeStruck
Topics: Kubernetes, Open Source, CNCF

Open source communities often talk about being welcoming, but far fewer are willing to enforce what that actually means. In this clip, Kat Cosgrove, Kubernetes Release Team Subproject Lead and Head of Developer Advocacy at Minimus, explains why inclusion only works when it’s backed by clear rules and real consequences.

Strong communities start with trust. According to Cosgrove, that trust begins with a code of conduct that clearly defines acceptable and unacceptable behavior, offers anonymous reporting, and includes escalation paths — even when complaints involve leadership. Without those guardrails, marginalized contributors are left to navigate risk on their own, and many simply opt out.

She points to the CNCF and Kubernetes communities as examples of enforcement done right. Bad behavior isn’t ignored or quietly tolerated. People can be removed from events or banned entirely. That reputation matters. Once a community is known to act decisively, more contributors feel safe participating, speaking, and leading.

The impact extends beyond individual interactions. KubeCon speaker selection policies, including requirements for diverse panels and first-time speakers, intentionally broaden who gets visibility. These rules aren’t symbolic. They directly shape who feels represented and who sees a future for themselves in the ecosystem.

Billy Thompson, Senior Global DevOps & Platform Engineering, Office of the CTO at Akamai, adds another dimension: community health directly affects open source sustainability. Volunteers donate years of unpaid labor that ultimately supports billion-dollar companies. Inclusive, respectful communities make it easier for contributors to stay engaged — and for companies to step up with meaningful support through open source program offices and sponsorships.

Together, their perspectives highlight a simple truth: inclusion isn’t a “nice to have.” It’s a structural requirement for open source projects that want to grow, endure, and remain relevant.

Why Multi Cloud Strategies Are Now Essential for Infrastructure Resilience | Greg Tucker, SIOS

Previous article