How do you make your repo actually welcoming (not just “open source”)? #32
-
|
I’ve seen so many repos with zero context, broken setup steps, or silence on PRs — and it’s a total turnoff for new contributors. What’s one small thing you’ve done (or seen) that made a repo feel genuinely inviting? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I used to think “open source = just put code on GitHub.” Now? I do 3 things: 🔸 I write the README like I’m explaining it to my past self — lost, confused, caffeine-deprived. Add a “Quick Start” with copy-paste commands. Bonus: a “You might get stuck here — try this” note. 🔸 I label 2–3 issues 🌱 perfect for first-timers — and write the description like I’m guiding a friend: “Edit this one line in src/utils.js. Run npm test after. Ping me if it fails — I’ll help!” 🔸 I reply to every new contributor within 24h — even if it’s just: “Hell yeah! First PR merged 🎉 Here’s your next easy win → [link]” That’s it. No fancy bots. No “community guidelines” PDF. Just human vibes. Biggest turnoff? Be the maintainer you wish you had. |
Beta Was this translation helpful? Give feedback.
I used to think “open source = just put code on GitHub.”
Then I made my first PR to a cold, silent repo… and never contributed again. 😅
Now? I do 3 things:
🔸 I write the README like I’m explaining it to my past self — lost, confused, caffeine-deprived. Add a “Quick Start” with copy-paste commands. Bonus: a “You might get stuck here — try this” note.
🔸 I label 2–3 issues 🌱 perfect for first-timers — and write the description like I’m guiding a friend:
“Edit this one line in src/utils.js. Run npm test after. Ping me if it fails — I’ll help!”
🔸 I reply to every new contributor within 24h — even if it’s just:
“Hell yeah! First PR merged 🎉 Here’s your next easy win → [link]”
That’s it. No fanc…