<oembed><type>rich</type><version>1.0</version><author_name>npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl</author_name><author_url>https://nostr.ae/npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2011-07-27&#xA;🗒️ Summary of this message: A suggestion to add a way for anyone to add to the bounty attached to a bug on the bug tracker and a listing page for bugs with their bounties. A roadmap could also help.&#xA;📝 Original message:On Wed, Jul 27, 2011 at 11:14 AM, Joel Joonatan Kaartinen &lt;&#xA;joel.kaartinen at gmail.com&gt; wrote:&#xA;&#xA;&gt; Perhaps even add a way for anyone add to the bounty attached to a bug on&#xA;&gt; the bug tracker? Also, a listing page for bugs with their bounties might&#xA;&gt; be nice too.&#xA;&gt;&#xA;&#xA;Good idea. I&#39;m not sure if the github bug tracker supports extension&#xA;attributes, but it&#39;d be a great place to add it. Also, people can let know&#xA;that they&#39;re already working on a feature using a comment, to prevent double&#xA;work.&#xA;&#xA;The biggest problem will be organizational, in getting the BTC together for&#xA;bounties; only a high profile member such as Gavin will have enough trust to&#xA;ask for support. Or maybe there&#39;s something left in the faucet? :-)&#xA;&#xA;Unrelated: what also might help is publishing a roadmap. Plan a few &#34;bug fix&#xA;only&#34; releases before scheduling addition of new features. It&#39;s also helpful&#xA;for people that wonder that direction the project is going in...&#xA;&#xA;JS&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110727/b57f8cf1/attachment.html&gt;</html></oembed>