Open Source at commercial organisations
summary
Company reduces open-source release time from almost a year to a few days by replacing ad hoc emails with a GitHub PR workflow that uses labels, stakeholder GitHub teams, and automated checks. More than 30 projects are public and the org now hosts roughly 100 repos after consolidating moved from 10+ GitHub organisations to a single one. CI standardizes on GitHub Actions and Dependabot, artifacts publish to Docker Hub and Maven Central, and access is controlled with centralized org secrets and weekly LDAP sync, contributors doubled.
AI-written summary · about
chapters (6)
- 0:00Start
- 14:49Timeine - GitHub-based process for Releasing Projects
- 24:34Timeline - Open Source Website
- 39:01Recommendations - Documentation
- 42:39Recommendations - Working in the Open
- 53:04Expedia Group Projects
related talks
58mAdopting open source in your organization
25mHow to Grow & Mentor an Open Source Community & Achieve Collaboration with Over 170 Listed Corpor...
20mJuggling the dual life of an enterprise open source project
25mManaging a GitHub Organization: Tools, Tips, and Best Practices
41mSecuring the World’s Open Source Software, Together
18mProject, Process, Product(ion)
31mOpen source work is work
29mHow We Collaborate @ GitHub