Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qm4y5-0002Gb-V8 for bitcoin-development@lists.sourceforge.net; Wed, 27 Jul 2011 14:20:13 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com; helo=mail-gx0-f175.google.com; Received: from mail-gx0-f175.google.com ([209.85.161.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Qm4y5-00013M-8l for bitcoin-development@lists.sourceforge.net; Wed, 27 Jul 2011 14:20:13 +0000 Received: by gxk3 with SMTP id 3so1401164gxk.34 for ; Wed, 27 Jul 2011 07:20:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.69.27 with SMTP id r27mr62069yba.435.1311776407675; Wed, 27 Jul 2011 07:20:07 -0700 (PDT) Received: by 10.151.13.9 with HTTP; Wed, 27 Jul 2011 07:20:07 -0700 (PDT) In-Reply-To: <1311765274.9830.3.camel@mei> References: <1311765274.9830.3.camel@mei> Date: Wed, 27 Jul 2011 14:20:07 +0000 Message-ID: From: John Smith To: Joel Joonatan Kaartinen Content-Type: multipart/alternative; boundary=000e0cd5905acde44a04a90dbe29 X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (witchspace81[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (witchspace81[at]gmail.com) 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Qm4y5-00013M-8l Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 14:20:14 -0000 --000e0cd5905acde44a04a90dbe29 Content-Type: text/plain; charset=ISO-8859-1 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 --000e0cd5905acde44a04a90dbe29 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 gi= thub bug tracker supports extension attributes, but it'd be a great pla= ce 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 tr= ust 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 &qu= ot;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

--000e0cd5905acde44a04a90dbe29--