rich1.0npub1654pkuj4rway0043gcu6rdh4umxescp7ew42d2czqvts3kwvg3esc48xrxhttps://nostr.ae/npub1654pkuj4rway0043gcu6rdh4umxescp7ew42d2czqvts3kwvg3esc48xrxnjumphttps://nostr.ae📅 Original date posted:2011-07-27 🗒️ Summary of this message: Suggestion to offer BTC bounties for fixing bugs on the bug tracker to encourage more bug-fixing and testing of existing functionality. 📝 Original message:Perhaps even add a way for anyone add to the bounty attached to a bug on the bug tracker? Also, a listing page for bugs with their bounties might be nice too. - Joel On Wed, 2011-07-27 at 06:40 +0000, John Smith wrote: > > On Wed, Jul 27, 2011 at 1:31 AM, Gavin Andresen > <gavinandresen at gmail.com> wrote: > Anybody have advice on how to encourage more bug-fixing and > testing of existing functionality instead of > yet-more-features? > > Make a list of bugs. Offer BTC bounties for fixing each one according > to how serious/difficult it is. They don't have to be high, just a few > BTC. It'll also help people get interested in the project and > *current* source base (instead of wanting to implement Yet Another > Incomplete Client from scratch). > > Or we could do the same as the mozilla/chrome projects, offer bounties > for finding new security holes and serious bugs. > > A policy like "that spiffy new feature you want won't be considered > until you've helped close some open bugs" won't work. This is open > source, people can just make their own fork with the spiffy new > feature without fixing any bugs. > > JS > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ Bitcoin-development mailing list Bitcoin-development at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development