A community has to do, what a community has to do!
summary
A new company forms in January with about 20 experienced employees, forks the ownCloud OES repo and publishes the code on GitHub after a 4–5 week cleanup, then ships the first paid long‑term support in March. The stack is rewritten in Go, cloud‑native, offered as a one-file binary or Kubernetes container, integrates OpenTalk and Collabora, and targets million‑user platforms with migration paths off legacy PHP stores. Legal pushback from the acquirer appears but the AGPL codebase remains public and runnable.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 0:43About the Highline Group
- 1:48Freedom and open source
- 3:11Open source benefits and governance
- 4:39Vendor lock-in risks
- 6:04File sharing as system relevant
- 8:10Acquisition of ownCloud
- 10:21Community must act
- 11:47Forking ownCloud OES
- 13:32Launching openCloud
- 15:00Future of openCloud
- 17:08Q&A session
related talks
15mLessons learned: Guidance on how to make open source development a success
01h 04mThe future of private clouds
29mHow to Disengage the Open Source Community
31mCreating Community in a Complex World: Everything Old is New Again
22mGerman Administration and Open Source
33mIs Your OSS Project Ready to Spin off Into a Company?
31mBuilding a Successful Open Source Community as an End-user Company
23mKeynote: Open Source and Startup Business Models