rich1.0npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jaflhttps://nostr.ae/npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jaflnjumphttps://nostr.ae📅 Original date posted:2011-07-27 🗒️ Summary of this message: Gavin Andresen asks for advice on how to encourage more bug-fixing and testing of existing functionality instead of adding more features. Suggestions include offering BTC bounties for fixing bugs and finding security holes. 📝 Original message: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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110727/6d2d3f7d/attachment.html>