diff options
author | Joel Joonatan Kaartinen <joel.kaartinen@gmail.com> | 2011-07-27 14:14:34 +0300 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2011-07-27 11:14:45 +0000 |
commit | 5713270f3e1adc36f9fde1b73aa556ffce04bfdd (patch) | |
tree | 865bbf1dff63de7551282d16ca5497ae12bb6ef2 | |
parent | 386eb3152172625e43e12f09a6df9bcb6d8a420f (diff) | |
download | pi-bitcoindev-5713270f3e1adc36f9fde1b73aa556ffce04bfdd.tar.gz pi-bitcoindev-5713270f3e1adc36f9fde1b73aa556ffce04bfdd.zip |
Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
-rw-r--r-- | 74/9891869339e8d493f1be40d25fe9f7a5d3f5c2 | 106 |
1 files changed, 106 insertions, 0 deletions
diff --git a/74/9891869339e8d493f1be40d25fe9f7a5d3f5c2 b/74/9891869339e8d493f1be40d25fe9f7a5d3f5c2 new file mode 100644 index 000000000..e352e27eb --- /dev/null +++ b/74/9891869339e8d493f1be40d25fe9f7a5d3f5c2 @@ -0,0 +1,106 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <joel.kaartinen@gmail.com>) id 1Qm24b-0000NA-Dd + for bitcoin-development@lists.sourceforge.net; + Wed, 27 Jul 2011 11:14:45 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.161.47 as permitted sender) + client-ip=209.85.161.47; envelope-from=joel.kaartinen@gmail.com; + helo=mail-fx0-f47.google.com; +Received: from mail-fx0-f47.google.com ([209.85.161.47]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1Qm24a-000885-HR + for bitcoin-development@lists.sourceforge.net; + Wed, 27 Jul 2011 11:14:45 +0000 +Received: by fxg11 with SMTP id 11so365756fxg.34 + for <bitcoin-development@lists.sourceforge.net>; + Wed, 27 Jul 2011 04:14:38 -0700 (PDT) +Received: by 10.204.23.6 with SMTP id p6mr461072bkb.368.1311765278244; + Wed, 27 Jul 2011 04:14:38 -0700 (PDT) +Received: from [91.153.53.68] (a91-153-53-68.elisa-laajakaista.fi + [91.153.53.68]) + by mx.google.com with ESMTPS id t19sm347225bku.40.2011.07.27.04.14.36 + (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 04:14:37 -0700 (PDT) +From: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com> +To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +In-Reply-To: <CAJNQ0sshm=q==++MVXEEkMDHX60HJxpFoR3CF3zK4NvFy2-rsQ@mail.gmail.com> +References: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com> + <CAJNQ0sshm=q==++MVXEEkMDHX60HJxpFoR3CF3zK4NvFy2-rsQ@mail.gmail.com> +Content-Type: text/plain; charset="UTF-8" +Date: Wed, 27 Jul 2011 14:14:34 +0300 +Message-ID: <1311765274.9830.3.camel@mei> +Mime-Version: 1.0 +X-Mailer: Evolution 2.30.3 +Content-Transfer-Encoding: 7bit +X-Spam-Score: -1.6 (-) +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 + (joel.kaartinen[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -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 +X-Headers-End: 1Qm24a-000885-HR +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: <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, 27 Jul 2011 11:14:45 -0000 + +Perhaps even add a way for anyone add to the bounty attached to a bug on +the bug tracker? Also, a listing page for bugs with their bounties might +be nice too. + +- Joel + +On Wed, 2011-07-27 at 06:40 +0000, John Smith wrote: +> +> On Wed, Jul 27, 2011 at 1:31 AM, Gavin Andresen +> <gavinandresen@gmail.com> 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 +> +> +> ------------------------------------------------------------------------------ +> Got Input? Slashdot Needs You. +> Take our quick survey online. Come on, we don't ask for help often. +> Plus, you'll get a chance to win $100 to spend on ThinkGeek. +> http://p.sf.net/sfu/slashdot-survey +> _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development + + + + + |