From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QoQgu-0006ri-In for bitcoin-development@lists.sourceforge.net; Wed, 03 Aug 2011 01:56:12 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of webmaster.com designates 216.152.64.169 as permitted sender) client-ip=216.152.64.169; envelope-from=prvs=1196ca3958=davids@webmaster.com; helo=mail1.webmaster.com; Received: from mail1.webmaster.com ([216.152.64.169]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.76) id 1QoQgt-0002Ek-QS for bitcoin-development@lists.sourceforge.net; Wed, 03 Aug 2011 01:56:12 +0000 X-MDAV-Processed: mail1.webmaster.com, Tue, 02 Aug 2011 18:41:32 -0700 Received: from [216.86.191.107] by mail1.webmaster.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v11.0.0) with ESMTP id md50003886022.msg for ; Tue, 02 Aug 2011 18:41:31 -0700 X-Spam-Processed: mail1.webmaster.com, Tue, 02 Aug 2011 18:41:31 -0700 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: joelkatz@webmaster.com X-MDRemoteIP: 216.86.191.107 X-Return-Path: prvs=1196ca3958=davids@webmaster.com X-Envelope-From: davids@webmaster.com X-MDaemon-Deliver-To: bitcoin-development@lists.sourceforge.net Message-ID: <4E38A731.9070703@webmaster.com> Date: Tue, 02 Aug 2011 18:41:05 -0700 From: David Schwartz User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1QoQgt-0002Ek-QS 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 Reply-To: davids@webmaster.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Aug 2011 01:56:12 -0000 On 7/26/2011 6:31 PM, Gavin Andresen wrote: > Anybody have advice on how to encourage more bug-fixing and testing of > existing functionality instead of yet-more-features? Two things would help a lot: 1) Letting people know that bug fixing is needed and would be appreciated. (In fact, until I saw your email, I had no idea this was an issue.) 2) Maintaining a list of the most important bugs that most need to be fixed in a place that's easy to find. I bet there are a lot of talented programmers who just can't quite figure out how best to help or don't realize that this kind of help is needed. Also, even better than a bounty system would probably be a changelog file included in the main source distribution that credited bugfixes to those who contributed them for the next few releases. DS