The main question you should ask yourself: Will this attract the right kind of contributions? Whenever I contribute to open-source, it’s typically because I fo

The main question you should ask yourself: Will this attract the right kind of contributions? Whenever I contribute to open-source, it’s typically because I found the project on my own, and, by extension, I already have an idea of how it should operate, and so I’m able to recognize issues or missing features. If an open-source project I’m using already works great, I make no changes. This is how people’s mindset should operate. Instead, a project like this seems ripe for people to come in and make any sort of change. OSS maintainers already deal with garbage PRs because of self-taught developers hearing that they should “contribute to open source to learn,” and then it’s just a README change or other unnecessary tweaks from absolute beginners. If an OOS maintainer put their repo on your platform, I feel like they would deal with a lot more of that. It also seems ripe for abuse from nefarious OSS maintainers, who will use that to just promote their own projects, rather than actively seeking contributions. If they have a limited scope as to the changes they’ll accept, and are using your platform just as a means to get more eyeballs on their Donation link, that’s bad for everyone. Just some things to keep in mind before you proceed.