Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.43 as permitted sender)
	client-ip=209.85.210.43; envelope-from=gavinandresen@gmail.com;
	helo=mail-pz0-f43.google.com; 
MIME-Version: 1.0
Date: Wed, 27 Jul 2011 11:31:14 +1000
Message-ID: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=bcaec520f4b91112db04a903011e
Subject: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over
	new features
Precedence: list

--bcaec520f4b91112db04a903011e
Content-Type: text/plain; charset=ISO-8859-1

Anybody have advice on how to encourage more bug-fixing and testing of
existing functionality instead of yet-more-features?

When I get back home from here in Australia I plan on trying to
lead-by-example by starting to tackle the huge backlog of reported bugs, but
I'd like to know if anybody has seen other open source projects successfully
get people to fix bugs instead of constantly adding features. Would policies
like "that spiffy new feature you want won't be considered until you've
helped close some open bugs" be effective (or would it just encourage people
to create shill accounts to open trivial-to-fix issues)?

If this was your run-of-the-mill open source project I would be much
more lackadaisical about letting in new features... but when people lose
money because bugs slip through (and several people HAVE recently lost money
because of bugs slipping through) we obviously have a pretty big problem
just making sure that the features we have now work properly.

(Thanks VERY much to those of you have HAVE been helping test and have been
submitting bug fixes; I don't mean to imply that everybody has been
feature-happy, just that it seems like a lot of potential bitcoin
contributors start out by submitting a nifty new feature that sure would be
nice to have if we weren't so busy trying to make sure the features we
already have work properly all the time).

-- 
--
Gavin Andresen

--bcaec520f4b91112db04a903011e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Anybody have advice on how to encourage more bug-fixing and testing of exis=
ting functionality instead of yet-more-features?<div><br></div><div>When I =
get back home from here in Australia I plan on trying to lead-by-example by=
 starting to tackle the huge backlog of reported bugs, but I&#39;d like to =
know if anybody has seen other open source projects successfully get people=
 to fix bugs instead of constantly adding features. Would policies like &qu=
ot;that spiffy new feature you want won&#39;t be considered until you&#39;v=
e helped close some open bugs&quot; be effective (or would it just encourag=
e people to create shill accounts to open trivial-to-fix issues)?</div>
<div><br></div><div>If this was your run-of-the-mill open source project I =
would be much more=A0lackadaisical=A0about letting in new features... but w=
hen people lose money because bugs slip through (and several people HAVE re=
cently lost money because of bugs slipping through) we obviously have a pre=
tty big problem just making sure that the features we have now work properl=
y.</div>
<div><br></div><div>(Thanks VERY much to those of you have HAVE been helpin=
g test and have been submitting bug fixes; I don&#39;t mean to imply that e=
verybody has been feature-happy, just that it seems like a lot of potential=
 bitcoin contributors start out by submitting a nifty new feature that sure=
 would be nice to have if we weren&#39;t so busy trying to make sure the fe=
atures we already have work properly all the time).</div>
<div><br>-- <br>--<br>Gavin Andresen<br><br>
</div>

--bcaec520f4b91112db04a903011e--