public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: John Smith <witchspace81@gmail.com>
To: Rick Wesson <rick@support-intelligence.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
Date: Wed, 27 Jul 2011 17:11:13 +0000	[thread overview]
Message-ID: <CAJNQ0suX-KFKHL3jxPR2KM+C64sEPoCtsY0CGohzT9qHcx542A@mail.gmail.com> (raw)
In-Reply-To: <CAJ1JLtuuUUmrWGScbvYikAY_FOQhWpX5bt1NGp8VkpHk-hHOsQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

On Wed, Jul 27, 2011 at 4:07 PM, Rick Wesson
<rick@support-intelligence.com>wrote:

> personally, if the software works better (less bugs) then btc will be more
> valuable. offering bounty is orthorginal to finding the right technical lead
> that will hurd the effort.
>
> put a bounty (salary) on the person to lead the effort, not the bugs
>

Bounties would be much less than a developer salary. The idea is not to pay
for people full time, but it would be more of a symbolic gesture to attract
developers and get them some coins.  People with coins are also more
motivated to make the project more valuable, otherwise you have a "tragedy
of the commons" problem.

Not that I don't agree Gavin with getting a salary but that's a completely
independent issue :)

JS

[-- Attachment #2: Type: text/html, Size: 1072 bytes --]

  parent reply	other threads:[~2011-07-27 17:11 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
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 [this message]
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=CAJNQ0suX-KFKHL3jxPR2KM+C64sEPoCtsY0CGohzT9qHcx542A@mail.gmail.com \
    --to=witchspace81@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=rick@support-intelligence.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