From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Fw: Seeking advice: Encouraging bug-fixing over new features
Date: Wed, 27 Jul 2011 17:02:13 -0700 (PDT) [thread overview]
Message-ID: <1311811333.75173.YahooMailNeo@web121002.mail.ne1.yahoo.com> (raw)
In-Reply-To: <1311811317.72375.YahooMailNeo@web121005.mail.ne1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]
----- Forwarded Message -----
From: Amir Taaki <zgenjix@yahoo•com>
To: John Smith <witchspace81@gmail•com>
Sent: Thursday, July 28, 2011 2:01 AM
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
I already tried the bounties route- made a forum thread offering $4000 worth of bounties and it got very few responses before dropping off the page.
Also, http://forum.bitcoin.org/?topic=4761.0 and http://forum.bitcoin.org/?topic=4543.0
In the end I came to the conclusion that the only was is to bring in projects and pay people to work fulltime on Bitcoin under an organisation.
________________________________
From: John Smith <witchspace81@gmail•com>
To: Joel Joonatan Kaartinen <joel.kaartinen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Sent: Wednesday, July 27, 2011 4:20 PM
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
On Wed, Jul 27, 2011 at 11:14 AM, Joel Joonatan Kaartinen <joel.kaartinen@gmail•com> wrote:
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.
>
Good idea. I'm not sure if the github bug tracker supports extension attributes, but it'd be a great place to add it. Also, people can let know that they're already working on a feature using a comment, to prevent double work.
The biggest problem will be organizational, in getting the BTC together for bounties; only a high profile member such as Gavin will have enough trust to ask for support. Or maybe there's something left in the faucet? :-)
Unrelated: what also might help is publishing a roadmap. Plan a few "bug fix only" releases before scheduling addition of new features. It's also helpful for people that wonder that direction the project is going in...
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@lists•sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 4646 bytes --]
next prev parent reply other threads:[~2011-07-28 0:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 1:31 [Bitcoin-development] " Gavin Andresen
2011-07-27 6:40 ` John Smith
2011-07-27 11:14 ` Joel Joonatan Kaartinen
2011-07-27 14:20 ` John Smith
2011-07-27 14:28 ` Luke-Jr
2011-07-27 14:42 ` Joel Joonatan Kaartinen
2011-07-27 14:53 ` John Smith
2011-07-27 16:02 ` Douglas Huff
2011-07-27 16:07 ` Rick Wesson
2011-07-27 16:47 ` Matt Corallo
2011-07-27 17:11 ` John Smith
2011-07-27 17:15 ` Joel Joonatan Kaartinen
2011-07-27 22:45 ` Gavin Andresen
2011-07-27 22:54 ` Joel Joonatan Kaartinen
2011-07-27 23:07 ` Matt Corallo
2011-07-28 6:31 ` John Smith
2011-07-28 0:15 ` Jeff Garzik
2011-07-28 15:37 ` Caleb James DeLisle
[not found] ` <1311811317.72375.YahooMailNeo@web121005.mail.ne1.yahoo.com>
2011-07-28 0:02 ` Amir Taaki [this message]
2011-07-30 11:49 ` Mike Hearn
2011-07-30 14:06 ` Rick Wesson
2011-07-30 14:07 ` Matt Corallo
2011-08-03 1:41 ` David Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1311811333.75173.YahooMailNeo@web121002.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox