How to Be a Good open-source Maintainer
SMRTR summary
A new piece by Ally Piechowski digs into why so many open source projects go quiet, and why the silent, uncommented close of a contributor's pull request is rarely malice. It's overload. Most popular projects run on a single unpaid person, and that person's worst week becomes every contributor's experience.
The fix, Piechowski argues, isn't willpower. It's architecture. Build a second responder. Put every decision in a public, archived channel with a reason attached. Make the first contribution genuinely easy. Research backs this up: newcomers who received a same-day human reply were about 15% more likely to contribute again.
The piece also takes on AI-generated submissions, noting that fabricated bug reports already killed curl's bug bounty program in January 2026, after the confirmed-vulnerability rate collapsed from over 15% of submissions to under 5%.
The closing advice is blunt: if you're done, archive the repo. Let your dependents know the difference between "slow month" and "it's over."
SMRTR provides this summary for quick context. The original article belongs to Hacker News.
Read the original article