From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QmCrI-0005Yh-6g for bitcoin-development@lists.sourceforge.net; Wed, 27 Jul 2011 22:45:44 +0000 Received-SPF: pass (sog-mx-2.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; Received: from mail-pz0-f43.google.com ([209.85.210.43]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QmCrH-0004ws-8x for bitcoin-development@lists.sourceforge.net; Wed, 27 Jul 2011 22:45:44 +0000 Received: by pzk1 with SMTP id 1so3584436pzk.30 for ; Wed, 27 Jul 2011 15:45:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.29.105 with SMTP id j9mr592520pbh.76.1311806737262; Wed, 27 Jul 2011 15:45:37 -0700 (PDT) Received: by 10.142.163.9 with HTTP; Wed, 27 Jul 2011 15:45:37 -0700 (PDT) In-Reply-To: <1311786944.9830.77.camel@mei> References: <1311765274.9830.3.camel@mei> <201107271028.28057.luke@dashjr.org> <1311786944.9830.77.camel@mei> Date: Thu, 28 Jul 2011 08:45:37 +1000 Message-ID: From: Gavin Andresen To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=bcaec520ef7396a68e04a914ce03 X-Spam-Score: -0.8 (/) 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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service -0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QmCrH-0004ws-8x 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 22:45:44 -0000 --bcaec520ef7396a68e04a914ce03 Content-Type: text/plain; charset=ISO-8859-1 RE: bounties: "A couple of bitcoins to fix a bug" sounds to me like nothing but trouble for whoever is in charge of awarding the bounties, but maybe I'm just anti-bounty because spending 2 or 3 hours and getting $30 worth of bitcoins for fixing a bug wouldn't motivate me. Anybody know how cash bounties have worked for other projects? Have any others paid bounties on run-of-the-mill bugs, and did that cause any problems? I'm worried that if contributors start getting bounties that will change the dynamic from cooperative to competitive. For example, if somebody has figured out how to solve 90% of some tricky bug I don't want them to hesitate to ask for help on the last 10% because they're worried "if I describe the progress I've made so far somebody might swoop in and steal my bounty...." RE: road-map and bug-fix-only-releases: Great ideas. RE: paid full-time project lead: I arranged to get paid to work on bitcoin full-time before I left for Australia; more details when I get back week-after-next. -- -- Gavin Andresen --bcaec520ef7396a68e04a914ce03 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable RE: bounties:

"A couple of bitcoins to fix a bug&qu= ot; sounds to me like nothing but trouble for whoever is in charge of award= ing the bounties, but maybe I'm just anti-bounty because spending 2 or = 3 hours and getting $30 worth of bitcoins for fixing a bug wouldn't mot= ivate me.

Anybod= y know how cash bounties have worked for other projects? =A0Have any others= paid bounties on run-of-the-mill bugs, and did that cause any problems? = =A0I'm worried that if contributors start getting bounties that will ch= ange the dynamic from cooperative to competitive. =A0For example, if somebo= dy has figured out how to solve 90% of some tricky bug I don't want the= m to hesitate to ask for help on the last 10% because they're worried &= quot;if I describe the progress I've made so far somebody might swoop i= n and steal my bounty...."

RE: road-ma= p and bug-fix-only-releases: =A0Great ideas.

RE: paid full-time project lead: =A0= I arranged to get paid to work on bitcoin full-time before I left for Austr= alia; more details when I get back week-after-next.

--
--
Gavin Andresen

--bcaec520ef7396a68e04a914ce03--