From: Gavin Andresen <gavinandresen@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
Date: Thu, 28 Jul 2011 08:45:37 +1000 [thread overview]
Message-ID: <CABsx9T1667dxUj_iRtgbUR0ymBVOaADkGQU_CMF7z7e1-ctRcQ@mail.gmail.com> (raw)
In-Reply-To: <1311786944.9830.77.camel@mei>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1371 bytes --]
next prev parent reply other threads:[~2011-07-27 22:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 1:31 Gavin Andresen
2011-07-27 6:40 ` John Smith
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 [this message]
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=CABsx9T1667dxUj_iRtgbUR0ymBVOaADkGQU_CMF7z7e1-ctRcQ@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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