summaryrefslogtreecommitdiff
path: root/34/c219d69f47b95ea666c28a40e9b39bcb9ae577
blob: 1d9c62a396c69aac98eda3209677fb2fd5f5c5f9 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
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 <prvs=1196ca3958=davids@webmaster.com>)
	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 <bitcoin-development@lists.sourceforge.net>;
	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 <davids@webmaster.com>
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: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
In-Reply-To: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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