Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

sjn (3626)

sjn
  sjn+useperlNO@SPAMpvv.org

Perl-dude in Oslo, trying to get Oslo.pm up and running... (Send me a message if you'd like to help! :)

Journal of sjn (3626)

Wednesday June 03, 2009
09:08 AM

Micropayments on CPAN/RT?

[ #39069 ]

Has there been any discussions anywhere about setting up a scheme for managing micropayments and/or bounties on CPAN and/or the RT infrastructure?

With the recession and everything, it seems as such a useful feature to have.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • There has been a few attempts over the years to do something like this.

    I remember one attempt that tried to assign bounties in terms of "beers". Fix this bug, we owe you three beers.

    The problem here is not the payment part, it's the micro part.

    Most of the people who write CPAN modules that other people depend on a lot about are professionals. If you assign payments to those packages, you need to be able to hit a number that is actually worthwhile.

    For example, current my $work is paying the author of a modul

    • My $work has also paid CPAN modules to add features we want or need. It's probably pretty common. But a system that allowed us to contribute a few hundred dollars combined with your few hundred, etc could easily reach a point where it's not an insult. Also if it's structured as a bounty then anyone can do the work. I think a system like this could work as long as it was done right.

      The hard part would be making sure that the money got paid to right be people when the work was done in a way that's satisfactor

      • A "couple of hundred dollars" is not micropayment. The latter is more like "a few dollars".
        • Right, but what I was saying is that it adds up and it makes sense that the intended recipient of the work wouldn't do it until it added up to enough to make it worth it.

          And in to those micro-payments the few hundred dollars that companies would be willing to throw in for specific bugs, etc and you'd have a pretty good amount. Such a system could even allow prospective developers to set a target bounty that would need to be reached for the work to be worth it.

    • The problem here is not the payment part, it's the micro part.

      Most of the people who write CPAN modules that other people depend on a lot about are professionals. If you assign payments to those packages, you need to be able to hit a number that is actually worthwhile.

      I was thinking of a model similar to pledgebank.com - several people pledging a "micro" amount, and when the sum is high enough to motivate someone, then something gets done - with maybe some trustworthy middleman keeping track of each micropledge or actual micropayment until the task in question is completed.

      IMO, it's not that important wether or not it's worthwhile to do for the money alone. We're mainly talking about open source development here, so motivation for fixing bugs or making features are alrea