Allow projects to opt out of codesy

[groovecoder]

https://news.ycombinator.com/item?id=8542969

[skaido]

I don't think I get what tip4commit is trying to achieve - they don't care about the "tips" reaching the developer.

iPhone$B$+$iAw?.(B

Dec 24, 2014 10:10 AM$B!"(Bluke crouch notifications@github.com $B$N%a%C%;!<%8(B:

https://news.ycombinator.com/item?id=8542969

$B!=(B Reply to this email directly or view it on GitHub.

[groovecoder]

Yeah, tip4commit seems especially flaky. James Socol wrote a better post about general concerns with how bounties and tips can negatively affect open-source:

http://coffeeonthekeyboard.com/bounties-and-tips-1204/

IMO codesy mitigates these concerns if it:

• Allows projects to opt-out
• Keeps bids private

[groovecoder]

Oh, also:

• Create a "payout committee" out of the offering bidders who offered more than the median bid amount on a bug; this keeps the "merged" vs. "done" decision in the community and out of codesy

[skaido]

Yep, I get the opt out and private bids. What are the possibilities for the other side of the coin (or is there one?) -sk

On Thu, Dec 25, 2014 at 9:22 AM, luke crouch notifications@github.com wrote:

Oh, also:

• Create a "payout committee" out of the offering bidders who offered more than the median bid amount on a bug; this keeps the "merged" vs. "done" decision in the community and out of codesy

— Reply to this email directly or view it on GitHub https://github.com/codesy/codesy/issues/60#issuecomment-68104595.

[groovecoder]

What other side of the coin do you mean?

[skaido]

perhaps a variety of approaches (of varying degrees of monetary incentives and transparency) for an audience (most likely service companies) who might be up against tight deadlines or needing a fix requiring expertise outside of their core?

-sk

On Sun, Dec 28, 2014 at 11:49 AM, luke crouch notifications@github.com wrote:

What other side of the coin do you mean?

— Reply to this email directly or view it on GitHub https://github.com/codesy/codesy/issues/60#issuecomment-68212316.

[groovecoder]

Ah, yeah so the sides of the coin are:

1. OSS maintainers who don't want monetary transactions conducted on their projects
2. OSS users who want to use monetary incentives to get things fixed

Technically, with an opt-out mechanism, OSS users could fork a project, re-create the issue they want fixed, and bid on the issue in their fork. Though they might run into legal issues if the original software license is something like CC-BY-NC that explicitly disallows copying and using for commercial purposes.