Guide to getting started in open source
summary
Explains that documentation work is the most-requested contribution and lists concrete benefits: portfolio pieces, new skills, wider network, and measurable career moves (several jobs gained via referrals). Walks through tools to learn: git/GitHub, a text editor (Atom or equivalent), Markdown, and static site generators. Recommends concrete steps: check project activity and labels like good first issue, read contributing guides and code of conduct, start small, and be explicit about time available.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:45Project structure
- 3:38Documentation
- 4:23Benefits
- 8:37Find a project
- 11:09Research a project
- 13:49Consider new contributors
- 14:56Tools
- 16:06Markdown
- 18:36Expert
- 23:51Dont be me
- 25:23Thank you
- 25:34Twitter
- 26:11Accessibility
- 26:58Banana Bread
- 28:05How much support do you get
- 29:38What skills do you need
- 31:30How do you handle reaching out to SMEES
- 33:08How do you identify skill requirements
- 34:50How did you find a project
- 36:04Follow up
related talks
22mA beginner's guide to Open Source
45mGetting Started with Open Source
38mA beautiful arrangement: Gaining experience & giving back through open source docs
27m"Getting Started with Open Source Contributions"
26mMake The Most Out Of Open Source
27mDesign Your Open Source Project
29mThe Technical Writers Guide to Contributing to Open Source Projects
31mGetting Started with Open Source Contributions