Becoming an awesome open source contributor
summary
Practical roadmap: set up Git and GitHub, fork the repo, send a pull request and expect review and delays; the first contribution can be a documentation fix that gets merged overnight (example: a NuGet docs PR that fixed a broken build flow). Expect maintainers to require attach unit tests with PRs, to follow coding standards and contribution guides, and to check licenses; use discovery sites like first-timers-only / up-for-grabs / CodeTriage and aim at active projects with an explicit license. Claim: modern ecosystems (e.g. .NET Core) get roughly 40% of contributions from the community.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:21About Christos
- 2:31Not just a developer
- 2:49How we learn
- 3:13First experience with open source
- 7:25What is open source
- 8:01Its a community
- 8:37Who uses open source
- 9:45Apple
- 11:37SNS Core
- 12:28Dotnet Foundation
- 13:27Microsoft
- 13:53Why should you care
- 19:56Why do I care
- 20:48Magic happens
- 21:25How to get started
- 23:48Where to find projects
- 26:23My contributors checklist
- 30:51Becoming a maintainer
- 31:02Other things you can do
- 33:22You dont get paid
- 33:37Becoming a better maintainer
- 39:10When things go bad
- 40:17Can things go bad
- 40:58The Cathedral in the Bazaar
- 41:28Git Repository
- 43:11Questions
- 45:02How often do you contribute
related talks
40mI wanna do Open Source, but I don't know how
10mDemystifying Contributing to Open Source
32mContributing to Open Source: A Guide
28mBest Practices for an Effective Open Source Contribution
13mHow to Make Your First Open Source Contribution
11mContributing to Open Source
22mA beginner's guide to Open Source
51mMy awesome journey with Open Source