<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://bfwatch.barcampbank.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Bank &amp; Finance Watch - Reverse Bounty - Comments</title>
 <link>http://bfwatch.barcampbank.org/?q=node/202</link>
 <description>Comments for &quot;Reverse Bounty&quot;</description>
 <language>en</language>
<item>
 <title>Reverse Bounty</title>
 <link>http://bfwatch.barcampbank.org/?q=node/202</link>
 <description>&lt;div class=&quot;vote-up-down-widget&quot;&gt;&lt;span class=&quot;up-inact&quot; title=&quot;You must login to vote.&quot;&gt;&lt;/span&gt;&lt;span class=&quot;down-inact&quot; title=&quot;You must login to vote.&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class=&quot;field field-type-text field-field-url&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;URL:&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item&quot;&gt;&lt;p&gt;&lt;a href=&quot;http://www.bryght.com/blog/boris-mann/reverse-bounties&quot; title=&quot;http://www.bryght.com/blog/boris-mann/reverse-bounties&quot;&gt;http://www.bryght.com/blog/boris-mann/reverse-bounties&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-type-text field-field-short-description&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Short description:&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item&quot;&gt;&lt;p&gt;A &amp;quot;reverse bounty&amp;quot; is a concept I was discussing at the &lt;a href=&quot;http://www.drupal.org/drupalcon-2005&quot;&gt;2005 Drupal conference&lt;/a&gt;. Bounties are a fairly well known concept within the open source world: users post bounties in order that bugs get fixed or features get added.&lt;/p&gt;
&lt;p&gt;The main issue with this is that it is user driven, and end users often don&#039;t have any concept of how easy or hard something is to implement -- or even what might be possible given the platform.&lt;/p&gt;
&lt;p&gt;Reverse bounties are instead posted by developers. It is an idea and feature description of something that the developer actually wants to work on, along with the money required. The developer knows that it can be done, knows what the platform can do, and has the skills to actually implement it. The money allows them to dedicate time to actually work on it.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <comments>http://bfwatch.barcampbank.org/?q=node/202#comment</comments>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/43">P2PVenture</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/13">Financing</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/14">Microfinance</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/55">Reputation Management - Trust Scoring</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/1">English</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/7">Article or whitepaper</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/91">bounty</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/90">open source software</category>
 <category domain="http://bfwatch.barcampbank.org/?q=taxonomy/term/92">peerfunding</category>
 <pubDate>Sun, 02 Sep 2007 14:09:18 +0000</pubDate>
 <dc:creator>Sam Rose</dc:creator>
 <guid isPermaLink="false">202 at http://bfwatch.barcampbank.org</guid>
</item>
</channel>
</rss>
