This is an automated archive made by the Lemmit Bot.
The original was posted on /r/opensource by /u/hello_code on 2026-02-15 15:57:39+00:00.
I am building a developer tool and I want to open source part of it in a way that is actually useful to people, not just a marketing move.
I have been thinking a lot about what makes someone trust a new project enough to contribute. Not stars, not hype, real contributors who stick around.
What I am planning so far
• Clear README with one quick start path
• Good first issue labels with real context
• Contribution guide that explains architecture in plain language
• Small roadmap so people know what matters now
• Fast responses on issues and PRs
For people who have done this well, what made the biggest difference in your project
What did you do early that you wish more founders would do
If you are open to sharing examples, I would love to study them