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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qlxn0-0001rF-Kr for bitcoin-development@lists.sourceforge.net; Wed, 27 Jul 2011 06:40:18 +0000 Received-SPF: pass (sog-mx-1.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-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Qlxn0-0008L3-0D for bitcoin-development@lists.sourceforge.net; Wed, 27 Jul 2011 06:40:18 +0000 Received: by gxk3 with SMTP id 3so1110023gxk.34 for ; Tue, 26 Jul 2011 23:40:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.63.10 with SMTP id l10mr6077950yba.378.1311748812456; Tue, 26 Jul 2011 23:40:12 -0700 (PDT) Received: by 10.150.147.15 with HTTP; Tue, 26 Jul 2011 23:40:12 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 06:40:12 +0000 Message-ID: From: John Smith To: Gavin Andresen Content-Type: multipart/alternative; boundary=000e0cd39bee00435e04a907523f 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: 1Qlxn0-0008L3-0D 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 06:40:18 -0000 --000e0cd39bee00435e04a907523f Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 27, 2011 at 1:31 AM, Gavin Andresen wrote: > Anybody have advice on how to encourage more bug-fixing and testing of > existing functionality instead of yet-more-features? Make a list of bugs. Offer BTC bounties for fixing each one according to how serious/difficult it is. They don't have to be high, just a few BTC. It'll also help people get interested in the project and *current* source base (instead of wanting to implement Yet Another Incomplete Client from scratch). Or we could do the same as the mozilla/chrome projects, offer bounties for finding new security holes and serious bugs. A policy like "that spiffy new feature you want won't be considered until you've helped close some open bugs" won't work. This is open source, people can just make their own fork with the spiffy new feature without fixing any bugs. JS --000e0cd39bee00435e04a907523f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Jul 27, 2011 at 1:31 AM, Gavin Andre= sen <gavina= ndresen@gmail.com> wrote:
Anybody have advice on how to encourage more bug-fixing and testing of exis= ting functionality instead of yet-more-features?

Make = a list of bugs. Offer BTC bounties for fixing each one according to how ser= ious/difficult it is. They don't have to be high, just a few BTC. It= 9;ll also help people get interested in the project and *current* source ba= se (instead of wanting to implement Yet Another Incomplete Client from scra= tch).

Or we could do the same as the mozilla/chrome projects, offer bounties = for finding new security holes and serious bugs.

A policy like "= ;that spiffy new feature you want won't be considered until you've = helped close some open bugs" won't work. This is open source, peop= le can just make their own fork with the spiffy new feature without fixing = any bugs.

JS

--000e0cd39bee00435e04a907523f--