Panel Discussion: It Takes a Village - The Case for a Versatile Open Source Workforce
summary
Panel describes concrete practices: running an IETF hackathon: 4 projects, 40 people to ship reference implementations; using TiDB and Chaos Mesh inside CNCF ecosystems; encouraging 10% time for community work and internal hackathons to produce upstream fixes (Pinkap finds users from v1.0 after 10 years). Compliance teams push SBOMs and OpenSSF baseline checks, HPE grants 60 volunteer hours and recommends publishing ESBOMs with releases. The EU Cyber Resilience Act obligates reporting exploited vulnerabilities and contributing fixes upstream.
AI-written summary · about
chapters (12)
- 0:00Panel discussion intro
- 1:30Panelists' open source roles
- 9:21Diverse job roles beyond software development
- 11:07Organizational placement of open source roles
- 16:49Cross-collaboration in open source
- 17:31Standards for open source
- 21:02Skills for open source roles
- 26:45Community management in corps
- 31:03Leadership support for open source
- 36:26Regulation and open source
- 39:57Teaching open source philosophy
- 41:21Closing remarks & Q&A
related talks
48mPanel Discussion - Women In FOSS
44mIt takes a Village - Role Diversity in Open Source
13mOpen Web, Open Source, Open Communities
49mPanel Discussion: Words Matter: Inclusive Language in Software, Open Source, & the Enterprise
44mBuilding On-Ramps for Non-Code Contributors in Open Source
41mDiversity in Open Source
45mPanel Discussion: Open Source as a Second Language
37mHow to Make Open Source Work for Your Career