GitHub Gone Wrong - Lessons Learned from Organic Open Source
summary
GitHub use at Cisco grows organically into dozens of orgs and about 681 repos (673 public), causing confusion over ownership and contact info; governance fixes include turned off member repo creation, roughly 20 owners (2FA mandatory), ~150 members, and >500 outside collaborators as repo admins. A template repo plus a script standardizes README, CONTRIBUTING, CODE_OF_CONDUCT and license choices (BSD/MIT for samples, Apache for big projects). A pragmatic but non‑open Cisco Sample Code License speeds sharing. Security scanning, audit metrics and recognition for contributors remain unfinished.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:25Overview
- 2:03Why GitHub
- 2:31GitHub Groups
- 3:36GitHub Organization
- 4:23The Problem
- 5:32Cisco Devnet
- 6:38Cisco GitHuborg
- 7:24Cisco Devnet vs GitHuborg
- 8:44Public vs Private
- 11:20Membership Permissions
- 11:40Owners
- 13:05Members
- 14:14Collaborators
- 16:03Contribution
- 17:23Code of Conduct
- 18:00Good Readme
- 20:40Copyright
- 21:53Corporate License Challenge
- 22:50Cisco Sample Code License
- 23:57Code Exchange
- 24:35Next Steps
related talks
25mLessons Learned from Cultivating Open Source Projects and Communities
57mOpen Source at commercial organisations
25mHow to Grow & Mentor an Open Source Community & Achieve Collaboration with Over 170 Listed Corpor...
45mAn OSPO for OSPOs: Managing Open Source at GitHub
25mLessons Learned from Cultivating Open Source Projects and Communities
23mGrowing A Successful and Sustainable Project
23mGood Governance Practices for Healthy Open Source Projects
39mA Guide to Securing GitHub Based on Lessons Learned