Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
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.