Whale Care 101 - How We Organize A 200+ Devs Project
summary
Two GitHub orgs host 200+ members, ~100 repositories and 30+ committers; a monorepo migrates into an Eclipse-managed org with 58 repos while the consortium keeps ~128. A merged system team runs Azure AKS and Kubernetes clusters provisioned by Terraform, supplies golden-path GitHub Workflows and Helm charts, and builds a product dashboard with metadata files. Release coordination bundles 15+ components quarterly, guided by Tractus-X Release Guidelines and a custom GitHub Action for dash; community growth and onboarding improve, while release checks remain largely manual.
AI-written summary · about
chapters (11)
- 0:00Tractor 6 project intro
- 1:06Tractor 6 background
- 3:55Early project structure challenges
- 6:03Merging teams and infrastructure
- 9:15Scaling infrastructure and move
- 13:08Weekly office hours
- 14:35Tractor 6 release guidelines
- 18:30Tractor 6 current state
- 25:59Journey summary and future plans
- 27:03Open source lessons
- 32:25Q&A
related talks
25mManaging a GitHub Organization: Tools, Tips, and Best Practices
31mGitHub as a self-sustaining product for large-scale environments
57mOpen Source at commercial organisations
47mPolicing Open-Source Projects at Scale
01h 06mHow GitHub delivers GitHub using GitHub
37mConfiguration as a Code: Managing Hundreds of GitHub Organizations to Streamline Supply Chain Security
46mBuilding Developer Community One Pull Request at a Time
29mHow We Collaborate @ GitHub