Open Source Protips from the Trenches
summary
A practical set of concrete rules and examples: a 2003 KDE patch and an angry reply that drives a contributor away; an 80/20 estimate for effort distribution that motivates active outreach; specific behaviors that increase uptake — dont respond while angry, ask questions dont give orders — pairing, merging pull requests with emoji and short praise, and a week-old first-time contributor whose docs PR actually lands. Each item explains the action, the tool or phrase used, and the measurable outcome.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:45Open Source isnt about code
- 1:56An example of community awesomeness
- 5:10Dont respond while angry
- 6:55Encourage more people to contribute
- 9:43Ask questions
- 10:34Offer help
- 12:21Wrap up
related talks
28mGet yourself heard in Open Source
44mBuilding On-Ramps for Non-Code Contributors in Open Source
49mOpen Source At Work - How Contribute On The Clock
24mOpen Source for your Benefit
50mOpen Source Survival Guide
36mAll the Things they didnt teach you at University
47mPanel Discussion: A How-to Guide for Contributing to Open Source as an Employee
33mIncluding People