Intersource is GitHub culture and open source principles
summary
Argues that deploying GitHub Enterprise across a company yields searchable, auditable code, real time telemetry and automation tied to CI tools like Jenkins CircleCI Travis plus coverage and test signals from Coveralls and Cypress and metrics via Prometheus Grafana, and that tracking pull request velocity and consolidating into a mono repository reveals reuse, security risk and developer activity. Recommends going all in, building community of practice and a product development lab, using Slack or Discord and Docker Terraform to make quick reproducible demos.
AI-written summary · about
chapters (21)
- 0:00Introduction to Intersource
- 1:09Why GitHub in enterprises
- 5:13Open source team structures
- 7:01Communities of practice
- 8:31Learning by doing with GitHub
- 10:00Data collection and insights
- 12:37Pull requests and parallel work
- 14:06Mono repositories benefits
- 16:00Automation and process efficiency
- 17:32Compliance automation
- 19:00Customer and product visibility
- 20:29Cross-department collaboration
- 21:36Tool chain integration
- 23:26Real-time business communication
- 26:23External collaboration examples
- 27:49Feedback and software innovation
- 29:58Mindset shift challenges
- 31:28Product development labs
- 32:55GitHub Enterprise rollout
- 34:03Philosophy beyond cost reduction
- 35:08Q&A and closing
related talks
26mWhy innersource is a critical component of FOSS sustainability
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
27mInnerSource at scale Let's innovate together!
28mA Frictionless Inner Source Journey
25mLooking at the Future of InnerSource
36mInnerSource at Scale: A Platform-centric Approach
28mInner Source
52mBottom-Up Open Source Culture