Using GitHub at Large Corporations to Unlock Sustainable Open Source Contribution

Explore strategies for leveraging GitHub in large corporate environments to foster sustainable open source contributions. Dive into the evolution from a "Wild West" approach to structured GitHub Organizations, examining Cisco's DevNet and main GitHub Orgs as case studies. Learn about public vs. private repositories, appropriate content for corporate GitHub Orgs, and the importance of archives. Understand membership roles, permissions, and the process of contributing to DevNet. Delve into corporate licensing challenges, including Cisco's Sample Code License and open source licensing considerations. Discover how to contribute new repositories, use repo templates, transfer existing repos, and manage long-lived forks. Gain insights on integrating with Cisco's Code Exchange and explore next steps for implementing these practices in your organization.

Intro
What we had - Wild West
GitHub Organization (a.k.a. Org)
Cisco DevNet GitHub Org
Cisco GitHub Org
Public vs. Private
What is NOT appropriate?
What is appropriate for Cisco Org?
Archives
Membership/Roles
Owners
Outside Collaborator
Teams
Permissions Summary
Contributing to DevNet
Code of Conduct
Contribute a new repo
Repo Templates
Transfer existing repo
Long lived forks
Corporate Licensing Challenges
Cisco Sample Code License
Rationale
Open Source Licenses
Beyond Licensing
Quick and dirty
Add your repo to Code Exchange
Rendering in Code Exchange
Next Steps
Questions?