Turning Policies, Standards, and Governance Into Enablers for Open-Source Innovation
summary
Three concrete governance patterns: right-size guard rails, frequency reduces difficulty, and no conflict. A bank-level example injects standards, controls and audit artifacts into microservices via a sidecar so policies travel with code; CI/CD enforces controls continuously so audits become routine and auditors get executable artifacts instead of screenshots. The San Mateo Bridge metaphor guides how much oversight to add, automation replaces human-only separation of duties, and the approach is field-tested (2017–2018) in regulated environments.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:18Governance patterns for open-source
- 5:23Right-size guardrails
- 9:35Frequency reduces governance difficulty
- 10:40Governance in microservices
- 14:11Governance vs innovation
- 17:00Conclusion and Q&A invitation
related talks
22mPutting Governance Into your DevOps Processes
01h 07mGovern with Agility
33mAutomating Industry Regulation (SoX, SoC 2) Enforcement...
22mRethinking Risk, Governance, and Compliance Applying Automation
30mAutomating Governance - Dear Security, Compliance, & Auditors We’re Sorry. Love DevOps
31mWrangling Compliance in the Wild West of Software Delivery
22mBridging Compliance and Innovation: A Guide for DevOps Leaders
29mCultivating architecture