Become an Open Source Service
summary
Claim: services can be truly open now if every service asset is published and outsiders can contribute using the same deploy/test/review pipeline that the team uses. Concrete practices already used: database dumps from production (with secrets removed), exhaustive deployment docs, an open planning Kanban on GitHub, containerized dev environments, and a UI badge linking live APIs to source. Remaining gaps are runtime contribution, data residency, and building a cryptographic chain of trust from commit to running instance.
AI-written summary · about
chapters (8)
- 0:00Introductions and welcome
- 2:55The paradox of SaaS
- 6:16Defining the challenge
- 9:18Practical requirements
- 14:21Beyond the code
- 17:58Building ecosystems
- 20:05Conference workshops
- 25:26Audience Q&A
related talks
35mYour Service is not Open Source
40mOpen Operations for Clouds and Services
15mAdopting Open Source Practices To Build More Inclusive Products and Services
13mHow can we truly arrive at "open-source everywhere"?
45mFostering an Open Environment for Developers in a Regulated Industry
04mThe role of open source in a company
40mOpening Open-Source with DevOps
40mHow to Open Source a Project and Possibly Not Fail While Trying