Why choose open infrastructure?
summary
Argument: open source code wins but most build platforms remain proprietary, creating vendor lock in, surprise $10k bills, or sudden shutdowns. Recommends concrete alternatives: GitLab for repo hosting, Jenkins or Travis CI for testing, IRC or Matrix for chat, and OpenStack for IaaS. Emphasizes three decision criteria—transparency, interoperability, influence—and warns a monoculture of closed platforms risks community control and project continuity.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:27Infrastructure
- 0:59Testing
- 1:15Communication
- 1:58Choices
- 3:53Were in trouble
- 4:39Open principles
- 5:26Gitlab
- 5:55Other good options
- 6:58Providers
- 7:29Conclusion
related talks
43mThe Open Sourcing of Infrastructure
17mOpen Source Infrastructure: Another Path of Growth for Open Source
22mContinuous Everything: Open-Source and the Future of DevOps
09mCloudy Futures? The Role of Open Source in Creating Competitive Markets
38mCode, Control, and Community: How Open Source is Reshaping Innova...
32mMastering Enterprise Open Source for Cloud and Vendor Independence
23mKeynote: Open Source and Startup Business Models
36mOpen-Source: Open Choice - A DevOps Guide for OSS Adoption
