This seems like an accidental perverse incentive. While you only get the top if your commit is accepted, I would be worried the maintainers will just end up with a bunch of low effort trivial patches.
the solution is probably a moving-knife procedure[1]:
have a list of rewardable issues. grow the reward for each issue with time. once the reward makes the time spent on the project worthwhile, people will be incentivized to commit. they won't let the reward grow too high, for fear that someone else will take it.
you could let coders freeze the reward for some amount of time, and get exclusive rights to claim that reward, until the time expires.
Comments
This seems like an accidental perverse incentive. While you only get the top if your commit is accepted, I would be worried the maintainers will just end up with a bunch of low effort trivial patches.
the solution is probably a moving-knife procedure[1]:
have a list of rewardable issues. grow the reward for each issue with time. once the reward makes the time spent on the project worthwhile, people will be incentivized to commit. they won't let the reward grow too high, for fear that someone else will take it.
you could let coders freeze the reward for some amount of time, and get exclusive rights to claim that reward, until the time expires.
[1] http://en.wikipedia.org/wiki/Moving-knife_procedure
That is very neat idea!
Indeed, my first thought was actually "let's see if there are any whitespace issues to fix".
I love how whitespace has turned into an "issue" and how a problem has also turned into an "issue"
Maybe encouraged by git's behavior of coloring "incorrect" whitespace.
Hopefully in the long term low effort trivial (but yet useful) fixes will become a scarce resource.