Sharing real-world DevOps stories from the GitHub community
GitHub works with thousands of organizations on their DevOps practices, from entrenched enterprises to cloud-native startups. Along the way, a consistent pattern has emerged: there is no single correct approach to DevOps, so teams often learn the most from peers facing similar challenges. Developers and engineers regularly seek advice on toolchain selection, collaboration culture, meaningful metrics, and recovery from failed initiatives.
To give the community a venue for these conversations, GitHub's The ReadME Project is publishing a series of articles from leaders across the business and open source landscape. Each contributor walks through one end-to-end engineering process in detail, covering their toolchain, best practices, key performance indicators (KPIs), and the lessons they believe will help others. The first three entries feature:
- Autodesk: George Swan explains how the company dismantled silos and increased innersourcing across teams, standardizing processes into a cohesive pipeline that synchronizes product, documentation, and localization releases.
- Netdata: Austin Hemmelgarn describes how site reliability engineers and developers continually refine their workflows for a distributed team, and how they automate and manage releases for a business built on open source software.
- Front: Kevin Mo discusses the reasoning behind Front's migration to Kubernetes and how the team made continuous deployment possible.
The ReadME Project is open to nominations for future contributors. GitHub is specifically seeking individuals and teams with diverse goals, backgrounds, and technical challenges who can share their experiences and expertise. Additional community-contributed articles are planned for the coming weeks, covering not just enterprise stories but also open source communities and those supporting DevOps toolchains.
