Keeping contributors
Open-source culture rewards a funny kind of stoicism. We're supposed to bang our head against something for a week before filing a bug report.
Then we see FOSS projects and devrel programs designed like corporate tech support. Layers of escalation. Ticket systems.
The healthier pattern? Stuck → get eyes on it, fast. Anyone who's pair-programmed has felt how this keeps you in flow! Problems seem to melt away as fast as they appear.
But we can't just drop that pattern into FOSS culture. We need to make places that enable vulnerability. Where asking for help counts as a contribution. Because it is. Someone else learns too.
If you look at contributors as if they're product users, you'll see horrible churn. We take in people already motivated enough to use and contribute, then spit most them out frustrated. Or failing silently.
Repos and devrel rooms feel intimidating or cold. But meet a maintainer at a conference? Usually warm and open to help however they can.
The problem's in between: tools built around issues, or processes, or projects. Not contributors.
Discord makes help requests disappear in the scroll. GitHub shows you issue #1234, not "this person tried three times and gave up." The people disappear, the tickets remain.
It tells people: Figure it out yourself. Be worthy before you speak.
Then on the other side, project maintainers feel alone, struggling to attract help.
What's stopping us from making "I helped someone get unstuck" count more than "I closed an issue?" From making active contributors more visible than open issues? From tracking "time to first response from a human?"
We're friendly and willing! We need to make our tools that reflect that.