Governance in Open Source - KDE's model
summary
KDE runs governance as risk management: pick one of the big five licenses (CC0, BSD, Apache 2.0, LGPLv3, GPL) rather than inventing a new one; use an optional FLA (worked with FSFE) or decide on a CLA early; register domains, trademarks and t-shirt sales under the KDE Association (a German legal entity) so assets don’t get lost; codify vision and a manifesto, enforce a code of conduct via a community working group, improve onboarding and bug triage; KDE is 21 years old and about one third of attendees read the conference code of conduct.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:52Managing Risks
- 4:40Big 5 Licenses
- 19:26Umbrella Services
- 21:08Ktt Code of Conduct
- 21:19Community Working Group
- 23:26Overview of Bikini Code of Conducts
- 24:52General Governance Advice
related talks
23mGood Governance Practices for Healthy Open Source Projects
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
01h 01mKeynote - Open source is just about the source, isn't it?
01h 04mQt's Open Governance Model, Discussed
09mFla Fla Fla Fla Fla ing Alive
24mThe KDE Free Qt Foundation
50mRunning a Successful Open Source Project
38mOpen Source Governance for Software Engineers