Lessons learned: Guidance on how to make open source development a success
summary
OpenCloud releases its code under Apache 2 and GPL while operating as a for‑profit selling services, and a fork causes a surge: six months = five years of stars. Development and planning move from closed systems to GitHub with an open by default policy (less than 10% of work stays private), plus public roadmaps and architecture decision records. To avoid database-caused data loss the project stores metadata in extended file attributes and keeps a lightweight nutsjs (like Reddus) cache for speed.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 1:50Why open source matters
- 3:59Misunderstanding open source value
- 5:48Beyond open code to open process
- 8:15Simplicity in design
- 11:50Key learnings summary
- 12:11Q&A session
related talks
01h 03mThe Value of Open Source
42mOpen Source in the Age of Cloud and Microservices
23mThe Open Source Journey of the Most Unlikely Participant
40mHow to Open Source a Project and Possibly Not Fail While Trying
27mCan Open Source and Corporate Interests Merge in the Cloud?
10mOpen Source vs Open Core
23mThe Future of Open Source Looks like Cloud (Keynote)
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..