|
Hey there, Thanks for checking us out :) We have multiple goals we want to achieve with GitHelp, the first one is helping busy open source maintainers to manage all the questions and support requests that comes to them from different sources like GitHub issues, Twitter, Mailing lists, StackOverflow, forums, or even requests for audio and video conversation in one place. You can think of it as ZenDesk for open source projects. The other side of that is for the benefit of developers, by matching them with the best experts and increase their chance of getting the best answers they need as fast as possible. But we don't just depend on matching developers requests with experts. We think there's enough content on the internet from resources like Documentation, Tutorial sites, StackOverflow questions, and blogs that we can match your request with a content/link that can help you without nagging someone. This beta version of GitHelp have the core of the product. Developers can create help requests and we match them with the open source maintainers and maintainers/hackers can reply. What's next for GitHelp is the dashboard for maintainers to manage the all requests and collaborate on that, the matching with content, also the payment is coming up very soon. We focused on the Ruby community right now, but we'll expand to other communities soon like JavaScript. Please let us know what you think! |
I've just had bad experiences before with companies that tried to lever off existing communities that didn't want them.
If your product really is great, then you shouldn't have any worries about offering an opt-out because very few people will use it.