How to Avoid Creating a GitHub Junkyard
summary
Zalando discovers that unfettered publishing creates a cluttered GitHub: about 400 repositories pile up in a year, many missing licenses, CONTRIBUTING.md, tests or users. A review group, a mandatory checklist and an incubator with six-month trial prune and validate projects; successful ones move to the public org. A small automation, zapper GitHub integration, enforces four-eyes merges for audits. Outcome: far fewer repos, clearer documentation and licensing, and visible projects with real users and contributors instead of a junkyard.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:43About Zalando
- 4:43Why we open source
- 8:04Empathy is a software skill
- 17:072008-2015: Command & Control
- 18:54We published things like this
- 26:01We loved to publish, hated to delete
- 27:51We didn't plan our junkyard
- 30:55How to excavate
- 32:23No exceptions policy
- 34:22Create Rules of Play
- 35:42Project publication checklist
- 38:57Envision actual users
- 40:59Teaching this takes time
related talks
25mManaging a GitHub Organization: Tools, Tips, and Best Practices
43mMy First Year of Pull Requests
43mTop Ten Worst Repositories to host on GitHub
17mBootstrapping an Open Source Project on GitHub
05mAdoption Agency for Abandoned Repos (AAAR)
39mA Guide to Securing GitHub Based on Lessons Learned
27mManaging A Healthy GitHub Community
44mGitHub Flavored Ruby