Date & time
17:00
Register for the panel discussion
Login or join LeadDev.com to view this content
Right now, your platform team is the only team that can fix what they built, leaving every other developer at the mercy of the ticket queue. InnerSource opens the platform’s codebase so developers can read it, debug it, and submit a fix directly — a collaborative, cross-team approach that gives them a chance to upskill and saves platform teams time. But how do you open the platform without starting from scratch?
Learn how to make your code, configs, and documentation readable to outsiders, and how to extend trusted-contributor rights to those who prove themselves.
This panel brings together platform, security, and engineering leaders to explain how to redesign workflows, how to weigh compliance risk against skill development, and which systems are suited to shared ownership between platform and developer teams.
You will learn how to:
- Tell whether an easy button is closing a compliance gap or quietly becoming the next single point of failure
- Design contribution paths that keep developers debugging instead of ticket-waiting
- Extend trusted-contributor rights without handing over the guardrails that keep compliance and security intact
