Open Source at Scale

"Standing on the shoulders of giants"
We could say the same for Open Source Software (OSS).

Daily we're using a countless number of OSS libraries, tools, and frameworks to build our applications. We rely on the work of contributors, companies, and foundations which are dedicating their time and resources to the Open Source ecosystem.

However, building Open Source Software is not as easy as copy-n-pasting a folder on GitHub. Great Open Source Software needs dedicated resources, top-notch documentation, openness to the community, and a mindset to follow industry trends and directions.
Moreover, releasing OSS as an individual and as a company has deep fundamental differences.

Inside the React Team, we strive to build first-class OSS frameworks, to empower developers across the globe to build elegant UI experiences across Mobile & Web.

In this talk, I'll walk you through my experience building OSS Software, how you can get started, how to get your organization involved, and how to bring your project to success.

Transcript

2. Open Source at Scale Nicola Corti he/him @cortinico i.e. what I’ve learned from one year at React Native
3. he/him Android @ React Native twitter.com/cortinico 
 
 github.com/cortinico 
 
 ncorti.com Nicola Corti
4. LAMP
6. Idea Pre-launch Launch Maturity Graduation
7. Idea
8. Hackathon Project
9. Production Level OSS react buck pytorch componentkit docusaurus flipper litho fresco infer
10. Pre-launch
11. We build from source
12. We build from main
13. The Source of Truth fbsource sync
14. The Source of Truth fbsource import commit & close PR github.com/facebook/fbshipit
15. Build Tools • Challenges • Align the frameworks to tools that are not alien in the ecosystem • Expose relevant build failures to contributors
16. Prerequisites • Be able to build both internally and externally • Valuable/Stable CI Signals & Test Coverage • Team onboard with 
 OSS capacity • OSS is a tech & people challenge
17. Launch
18. Live
19. Live
20. Issue Triaging
21. Issue Triaging
22. Issue Triaging • Define a process • Use meaningful labels • actions/github-script to react to labels • actions/stale to close old issues • Canned Responses • reactnative.dev/contributing/bots- reference
23. Self-service APIs • Useful Error Messages • react-native doctor 
 To auto-inspect the user environment • react-native info 
 To auto-inspect the user environment
24. Reproducers • Mandatory reproducers as: • Failing Test cases • react-native init repos • Snack
25. Pull Requests
26. Pull Requests • (again) Define a process • Rotate reviewers (CODEOWNERS) • github.com/danger/danger
27. Pull Requests
28. Maturity
29. Releases
30. Releases Release Captain Release Co-pilot … Release Supporter • Drives the 
 release process • Makes final call on critical decisions • Generally from a partner company • Supports the 
 release process • Helps with comms and testing • Joined as a voluntary program • Helps with early feedback on RCs
31. Releases
32. Releases
33. Releases reactnative.dev/contributing/
34. Migrations
35. Migrations
36. Migrations
37. What does Support mean for you? • You can’t help everyone • How long is a version supported: • Define clear expectations 
 for users and tool developers
38. External Engagement Twitter Conferences Surveys Podcasts
39. External Engagement
40. Internal Engagement
41. Graduation
42. By Organizational Structure of Open Source Projects: A Life Cycle Approach - D. Wynn Introduction Growth Maturity Decline or Revive Adoption
43. Archiving
44. Transfer
45. Idea Pre-launch Launch Maturity Graduation Wrap-up
46. todogroup.org/ • Get a OSPO • Get a CLA process • github.com/todogroup/repolinter • README.md • LICENSE • CONTRIBUTING • CODE-OF-CONDUCT • CHANGELOG
47. “If I have seen further… …it is by standing on the shoulders of Giants” ― Isaac Newton, The Correspondence Of Isaac Newton
48. Nicola Corti @cortinico Thank You & Contribs are Welcome
49. Ecosystem
50. Ecosystem
51. Ecosystem
52. Ecosystem