fe3dba1298a4e8aa4ae50b1b9fcf5e5bd4aad2
1 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] 2 helo=mx.sourceforge.net) 3 by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) 4 (envelope-from <witchspace81@gmail.com>) id 1Qlxn0-0001rF-Kr 5 for bitcoin-development@lists.sourceforge.net; 6 Wed, 27 Jul 2011 06:40:18 +0000 7 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com 8 designates 209.85.161.175 as permitted sender) 9 client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com; 10 helo=mail-gx0-f175.google.com; 11 Received: from mail-gx0-f175.google.com ([209.85.161.175]) 12 by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) 13 (Exim 4.76) id 1Qlxn0-0008L3-0D 14 for bitcoin-development@lists.sourceforge.net; 15 Wed, 27 Jul 2011 06:40:18 +0000 16 Received: by gxk3 with SMTP id 3so1110023gxk.34 17 for <bitcoin-development@lists.sourceforge.net>; 18 Tue, 26 Jul 2011 23:40:12 -0700 (PDT) 19 MIME-Version: 1.0 20 Received: by 10.150.63.10 with SMTP id l10mr6077950yba.378.1311748812456; Tue, 21 26 Jul 2011 23:40:12 -0700 (PDT) 22 Received: by 10.150.147.15 with HTTP; Tue, 26 Jul 2011 23:40:12 -0700 (PDT) 23 In-Reply-To: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com> 24 References: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com> 25 Date: Wed, 27 Jul 2011 06:40:12 +0000 26 Message-ID: <CAJNQ0sshm=q==++MVXEEkMDHX60HJxpFoR3CF3zK4NvFy2-rsQ@mail.gmail.com> 27 From: John Smith <witchspace81@gmail.com> 28 To: Gavin Andresen <gavinandresen@gmail.com> 29 Content-Type: multipart/alternative; boundary=000e0cd39bee00435e04a907523f 30 X-Spam-Score: -0.4 (/) 31 X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. 32 See http://spamassassin.org/tag/ for more details. 33 -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for 34 sender-domain 35 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider 36 (witchspace81[at]gmail.com) 37 -0.0 SPF_PASS SPF: sender matches SPF record 38 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in 39 digit (witchspace81[at]gmail.com) 40 1.0 HTML_MESSAGE BODY: HTML included in message 41 -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from 42 author's domain 43 0.1 DKIM_SIGNED Message has a DKIM or DK signature, 44 not necessarily valid 45 -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 46 0.1 AWL AWL: From: address is in the auto white-list 47 X-Headers-End: 1Qlxn0-0008L3-0D 48 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> 49 Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing 50 over new features 51 X-BeenThere: bitcoin-development@lists.sourceforge.net 52 X-Mailman-Version: 2.1.9 53 Precedence: list 54 List-Id: <bitcoin-development.lists.sourceforge.net> 55 List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 56 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> 57 List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> 58 List-Post: <mailto:bitcoin-development@lists.sourceforge.net> 59 List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> 60 List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 61 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> 62 X-List-Received-Date: Wed, 27 Jul 2011 06:40:18 -0000 63 64 --000e0cd39bee00435e04a907523f 65 Content-Type: text/plain; charset=ISO-8859-1 66 67 On Wed, Jul 27, 2011 at 1:31 AM, Gavin Andresen <gavinandresen@gmail.com>wrote: 68 69 > Anybody have advice on how to encourage more bug-fixing and testing of 70 > existing functionality instead of yet-more-features? 71 72 73 Make a list of bugs. Offer BTC bounties for fixing each one according to how 74 serious/difficult it is. They don't have to be high, just a few BTC. It'll 75 also help people get interested in the project and *current* source base 76 (instead of wanting to implement Yet Another Incomplete Client from 77 scratch). 78 79 Or we could do the same as the mozilla/chrome projects, offer bounties for 80 finding new security holes and serious bugs. 81 82 A policy like "that spiffy new feature you want won't be considered until 83 you've helped close some open bugs" won't work. This is open source, people 84 can just make their own fork with the spiffy new feature without fixing any 85 bugs. 86 87 JS 88 89 --000e0cd39bee00435e04a907523f 90 Content-Type: text/html; charset=ISO-8859-1 91 Content-Transfer-Encoding: quoted-printable 92 93 <br><div class=3D"gmail_quote">On Wed, Jul 27, 2011 at 1:31 AM, Gavin Andre= 94 sen <span dir=3D"ltr"><<a href=3D"mailto:gavinandresen@gmail.com">gavina= 95 ndresen@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote= 96 " style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> 97 Anybody have advice on how to encourage more bug-fixing and testing of exis= 98 ting functionality instead of yet-more-features?</blockquote><div><br>Make = 99 a list of bugs. Offer BTC bounties for fixing each one according to how ser= 100 ious/difficult it is. They don't have to be high, just a few BTC. It= 101 9;ll also help people get interested in the project and *current* source ba= 102 se (instead of wanting to implement Yet Another Incomplete Client from scra= 103 tch).<br> 104 <br>Or we could do the same as the mozilla/chrome projects, offer bounties = 105 for finding new security holes and serious bugs.<br><br>A policy like "= 106 ;that spiffy new feature you want won't be considered until you've = 107 helped close some open bugs" won't work. This is open source, peop= 108 le can just make their own fork with the spiffy new feature without fixing = 109 any bugs.<br> 110 <br>JS<br><br></div></div> 111 112 --000e0cd39bee00435e04a907523f-- 113 114