I really do appreciate the complexity. I thought about it after my post, particularly about verification of delivery -- it can't just be "bug closed" on the RT. My best idea so far is to agree up front on a test script and the platform(s) on which it must run. If the script passes, the coder gets paid. Incremental payments can come when X% of tests pass. While writing the test script takes effort, too, that's another way of triaging the most important items to address -- i.e. the ones where someone is motivated enough to write a good, testable spec.

And while I get that this is complex, nevertheless, when US comp-sci students can outsource their homework to RentACoder for under $100 a shot, I've got to imagine that there's some existing infrastructure that could facilitate micro-payments for small, focused pieces of work. (And I'm not saying it's rentacoder.com, per se, I'm just using that as an example of the kind of infrastructure I mean.)

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re^3: The Perl 5 Conspiracy by xdg
in thread The Perl 5 Conspiracy by chromatic

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.