Beyond the license: measuring real openness in open source
summary
Nextcloud positions an on‑premise Microsoft 365 replacement used by governments and rolled out 100,000 sovereign digital workplaces per month last year. Licensing (GPL vs MIT) matters but practical openness rests on three things: public code, ability to build and external contributors. A web tool IsItReallyFOSS.com scores projects by buildability, contribution access, governance and business model; examples include AGPL projects with binary blobs and CLAs that block PRs, and the risk that VC pressure enables vendor lock‑in. Tools mentioned: GitHub/GitLab, build scripts, and LLMs for code explanation.
AI-written summary · about
chapters (17)
- 0:00Introduction and Nextcloud
- 1:29Open source assumptions and trust
- 3:15License goals and power shifts
- 6:04GPL vs permissive licenses
- 7:49Real open development practices
- 10:16Lock-in beyond the license
- 12:01Experiences with open source lock-in
- 13:48Stakeholders and project resilience
- 14:51Introducing reallyfoss.com
- 17:39Evaluating project openness
- 19:21Q&A on risk evaluation criteria
- 22:11Open LLMs and openness challenges
- 24:44Hosting platforms and pragmatism
- 26:51Forges and network effects
- 27:33Documentation and AI tools
- 29:00VC funding and project risks
- 31:12Closing and Q&A summary
related talks
25mWhat Makes Open Source Work: Licensing and Beyond
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
44m7 Things you can Learn from Microsoft's Open Source Experience
30mEvaluating Business Risk for Open Source Cloud Native Projects
01h 04mOpen Source, Open Mind: The Cost of Free Software
42mOpen Source Licenses: Between Parish Wars and Radicalism
36mPanel: Openwashing – How Do We Handle (and Enforce?) OSS Policies in Products?
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer