How the magic of open source helps our project
summary
Concrete workflows for using open source: inspect node_modules and npm registry, trace a flaky image bug from fast-image down to SDAnimatedImageView, verify a fix on main, then choose to wait, import main, fork and cherry‑pick, or apply npx patch-package to ship a targeted fix. Teams use patches to alter WatermelonDB behavior and tweak React Native libs; patches reapply on every install and avoid long forks. Claims mattermost keeps >90% of code open and reports clear wins: faster fixes, community QA and localization, and security audits.
AI-written summary · about
chapters (14)
- 0:00intro
- 0:22preamble
- 1:36agenda
- 5:32what kind of open source exist?
- 7:27npm and node_modules
- 7:58what is npm?
- 8:31node_modules folder
- 9:32understanding
- 14:04fixing
- 17:36changing
- 20:32closing
- 22:22give back
- 23:35summary
- 24:41thank you, connect
related talks
39mManaging an Open Source Project
36mOpen Source at Scale
25mThe node_modules Iceberg: Mysteries Below the Waterline
35mOpen Source at Scale
19mConsuming Open-source: A maintainer's perspective
52mCollaborating to Improve Open Source Security: How the Ecosystem Is Stepping Up
39mSOS: Sustainable Open Source
31mSolving a Tooling Problem For React Native