Navigating Uncertainty: Operational Risk Management in the Open-Source Sector
summary
Collabora frames operational resilience as an emergent property built from adaptive planning, scenario planning (about 60% of planning effort), and flexible resourcing, using continuous CI tests to catch upstream breakage and modular backlogs to redeploy engineers fast. Practical tools called out include SPDX/SBOM automation and OpenChain-style compliance boards with quarterly audits and re‑certification cycles, plus response triggers for maintainer departure or license shifts like Elasticsearch’s 2021 change that spawned OpenSearch. This yields faster detection, documented mitigations, and predictable delivery.
AI-written summary · about
chapters (9)
- 0:00Operational risk in open source
- 1:03Why resilience matters
- 4:14Four operational risk domains
- 9:08Principles for resilience
- 14:31Traditional vs modern risk
- 18:23Steps for operational resilience
- 23:20OpenChain compliance benefits
- 27:00Building upstream resilience
- 28:45Final thoughts & Q&A
related talks
29mNavigating Open Source Risk: A Strategic Approach
38mPanel: Open Source Management Based on Open Source
42mThe Role of Open Source Management Talent in Ensuring Software...
45mMastering Operational Health for Engineering Leaders
28mTalking with management about open source
28mSustainability beyond funds: Extrospective OSPOs
30mEvaluating Business Risk for Open Source Cloud Native Projects
21mScaling Internal Collaboration with Open Source Operating Models