{"type":"rich","version":"1.0","author_name":"npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl","author_url":"https://nostr.ae/npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-07-27\n🗒️ 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.\n📝 Original message:On Wed, Jul 27, 2011 at 11:14 AM, Joel Joonatan Kaartinen \u003c\njoel.kaartinen at gmail.com\u003e wrote:\n\n\u003e Perhaps even add a way for anyone add to the bounty attached to a bug on\n\u003e the bug tracker? Also, a listing page for bugs with their bounties might\n\u003e be nice too.\n\u003e\n\nGood idea. I'm not sure if the github bug tracker supports extension\nattributes, but it'd be a great place to add it. Also, people can let know\nthat they're already working on a feature using a comment, to prevent double\nwork.\n\nThe biggest problem will be organizational, in getting the BTC together for\nbounties; only a high profile member such as Gavin will have enough trust to\nask for support. Or maybe there's something left in the faucet? :-)\n\nUnrelated: what also might help is publishing a roadmap. Plan a few \"bug fix\nonly\" releases before scheduling addition of new features. It's also helpful\nfor people that wonder that direction the project is going in...\n\nJS\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110727/b57f8cf1/attachment.html\u003e"}