Главная
Study mode:
on
1
Intro
2
What we had - Wild West
3
GitHub Organization (a.k.a. Org)
4
Cisco DevNet GitHub Org
5
Cisco GitHub Org
6
Public vs. Private
7
What is NOT appropriate?
8
What is appropriate for Cisco Org?
9
Archives
10
Membership/Roles
11
Owners
12
Outside Collaborator
13
Teams
14
Permissions Summary
15
Contributing to DevNet
16
Code of Conduct
17
Contribute a new repo
18
Repo Templates
19
Transfer existing repo
20
Long lived forks
21
Corporate Licensing Challenges
22
Cisco Sample Code License
23
Rationale
24
Open Source Licenses
25
Beyond Licensing
26
Quick and dirty
27
Add your repo to Code Exchange
28
Rendering in Code Exchange
29
Next Steps
30
Questions?
Description:
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.

Using GitHub at Large Corporations to Unlock Sustainable Open Source Contribution

Linux Foundation
Add to list
0:00 / 0:00