From: John Smith <witchspace81@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
Date: Wed, 27 Jul 2011 06:40:12 +0000 [thread overview]
Message-ID: <CAJNQ0sshm=q==++MVXEEkMDHX60HJxpFoR3CF3zK4NvFy2-rsQ@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1171 bytes --]
next prev parent reply other threads:[~2011-07-27 6:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 1:31 [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features Gavin Andresen
2011-07-27 6:40 ` John Smith [this message]
2011-07-27 11:14 ` Joel Joonatan Kaartinen
2011-07-27 14:20 ` John Smith
2011-07-27 14:28 ` Luke-Jr
2011-07-27 14:42 ` Joel Joonatan Kaartinen
2011-07-27 14:53 ` John Smith
2011-07-27 16:02 ` Douglas Huff
2011-07-27 16:07 ` Rick Wesson
2011-07-27 16:47 ` Matt Corallo
2011-07-27 17:11 ` John Smith
2011-07-27 17:15 ` Joel Joonatan Kaartinen
2011-07-27 22:45 ` Gavin Andresen
2011-07-27 22:54 ` Joel Joonatan Kaartinen
2011-07-27 23:07 ` Matt Corallo
2011-07-28 6:31 ` John Smith
2011-07-28 0:15 ` Jeff Garzik
2011-07-28 15:37 ` Caleb James DeLisle
[not found] ` <1311811317.72375.YahooMailNeo@web121005.mail.ne1.yahoo.com>
2011-07-28 0:02 ` [Bitcoin-development] Fw: " Amir Taaki
2011-07-30 11:49 ` [Bitcoin-development] " Mike Hearn
2011-07-30 14:06 ` Rick Wesson
2011-07-30 14:07 ` Matt Corallo
2011-08-03 1:41 ` David Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJNQ0sshm=q==++MVXEEkMDHX60HJxpFoR3CF3zK4NvFy2-rsQ@mail.gmail.com' \
--to=witchspace81@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox