I've been noticing a lot of developers asking the same question: "How do I find open-source projects that match my skills?"
Current solutions suck. GitHub explore shows trending projects, not projects that fit YOUR actual experience level.
So I'm thinking about building something that:
- Looks at your GitHub history
- Recommends projects you'd actually want to contribute to
- Filters out unmaintained/toxic projects
- Matches by skill + experience, not just language
Before I spend 8 weeks building this, I want to validate:
1. Would you actually use this?
2. Would you pay $9/month for it?
3. What features would matter most?
Also curious about the maintainer side:
- Maintainers: Would you pay $29/mo to find contributors by skill?
I'm genuinely just validating demand before building. No product yet, no pitch.
Reply with honest feedback!
Top comments (3)
Congratulation for your first post!
This is a really solid idea, and it directly targets a pain point I see developers struggle with all the time. Matching by real experience and project health—not just language—feels like a much more practical approach than what exists today. I’d personally be interested in using something like this, especially if it helped me find projects where my skills actually add value. If it delivers accurate matches and saves time, the pricing sounds reasonable to me.
Umm, bit skepticial. If you are building it for OSS, are you keeping it OSS?
Would I use it? Yes
Would I pay $9/month? Maybe. Price sensitivity is high; you’ll need a free tier and obvious ROI.
features? bounty layer will be great, frictionless contributor onboarding
Maintainers pay $29/mo? Possibly for orgs or active maintainers who recruit regularl, but you’ll get higher willingness to pay from teams/companies hiring contributors than from solo maintainers. Or probably feature bounties to help regular contributors continue in OSS. Expecting maintainers pay $29 would be too much. I would rather say create a space where this could contribute back to OSS economy stability.
Hey!
That’s pretty a good idea.
Personally, I’d like to use a tool like this.
Unfortunately, my GH history is at most related to my studies period.
After that I was committed to work as consultant (client held repos) and push some code only to personal private repos meant for side work projects.
So, I’m curious how this kind of situation can be approached:
almost no visible contributions, but years of practical experience on the ground.