I like the business model, but what prevents someone from looking at a developer's solution and incorporating it without paying the developer? Say the company is charged when they use the patching mechanism to bring developer's work into their product. What would stop them from simply going around this mechanism and just copy and paste the solution into their own repository?
Also is the developer responsible for fixing bugs in their solution? Can a developer exploit the process by submitting buggy code they'll be paid extra to fix? Can a developer be required to fix bugs in their solution?
If a company can't inspect code before they pay they can't be certain it's relatively bug free, if they can inspect the code they could use it without paying for it easily.
You raise a great point. Still stuff to work out. This is the result of 54 hours of work (Philadelphia Startup Weekend) so definitely expect more in the coming weeks.
I think it's a great idea. Our company has various projects on github that could use a second pair of eyes other than our engineers. We wouldn't mind putting a bounty on it if someone were to commit a python library or two.
The paid platform will be a bit more involved to get working, for sure. Right now we're focusing on getting this useful for open source projects to find collaborators then we'll worry about making it useful for companies.
Also is the developer responsible for fixing bugs in their solution? Can a developer exploit the process by submitting buggy code they'll be paid extra to fix? Can a developer be required to fix bugs in their solution?
If a company can't inspect code before they pay they can't be certain it's relatively bug free, if they can inspect the code they could use it without paying for it easily.