As consultants, we would certainly be interested in that kind of approach.<br>And even though right now we are mainly concerned with putting to work some recently freed up resources, it could easily work both ways on other projects.
<br>Coupled with a good issues tracking system (drupal project module) this kind of approach could be very effective for all concerned.<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a>
<br><br><div><span class="gmail_quote">On 3/13/07, <b class="gmail_sendername">The Golden Condor !</b> <<a href="mailto:tgcondor@gmail.com">tgcondor@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Are there more people on this list who would like to see things done<br>and are willing to pay for it? Would you guys be interested in a<br>bounty style solutions? Other projects have used it successfully.<br><br>One reason for NOT using the bounty approach is if you want to keep IP
<br>to the new code.<br><br>On the pros, specs and requirements are visible to all, so any<br>developer could easily jump in and contribute, rather than having to<br>be committed to a project.<br><br>Tony A. A.<br>_______________________________________________
<br>consulting mailing list<br><a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br><a href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a><br></blockquote>
</div><br>