1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1Qm7df-0006yz-Vi
for bitcoin-development@lists.sourceforge.net;
Wed, 27 Jul 2011 17:11:19 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.175 as permitted sender)
client-ip=209.85.213.175; envelope-from=witchspace81@gmail.com;
helo=mail-yx0-f175.google.com;
Received: from mail-yx0-f175.google.com ([209.85.213.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1Qm7df-00023J-4g
for bitcoin-development@lists.sourceforge.net;
Wed, 27 Jul 2011 17:11:19 +0000
Received: by yxi19 with SMTP id 19so1156239yxi.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 27 Jul 2011 10:11:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.137.6 with SMTP id p6mr30812ybn.264.1311786673663; Wed, 27
Jul 2011 10:11:13 -0700 (PDT)
Received: by 10.151.13.9 with HTTP; Wed, 27 Jul 2011 10:11:13 -0700 (PDT)
In-Reply-To: <CAJ1JLtuuUUmrWGScbvYikAY_FOQhWpX5bt1NGp8VkpHk-hHOsQ@mail.gmail.com>
References: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
<1311765274.9830.3.camel@mei>
<CAJNQ0su9Qbi=zMaJA0G77UuHkXBy8k7YLBd4cec=Rc_-FGPBjA@mail.gmail.com>
<201107271028.28057.luke@dashjr.org>
<CAJ1JLtuuUUmrWGScbvYikAY_FOQhWpX5bt1NGp8VkpHk-hHOsQ@mail.gmail.com>
Date: Wed, 27 Jul 2011 17:11:13 +0000
Message-ID: <CAJNQ0suX-KFKHL3jxPR2KM+C64sEPoCtsY0CGohzT9qHcx542A@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Rick Wesson <rick@support-intelligence.com>
Content-Type: multipart/alternative; boundary=000e0cd58e98b46e0204a9102283
X-Spam-Score: -0.4 (/)
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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
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.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qm7df-00023J-4g
Cc: bitcoin-development@lists.sourceforge.net
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 17:11:20 -0000
--000e0cd58e98b46e0204a9102283
Content-Type: text/plain; charset=ISO-8859-1
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
--000e0cd58e98b46e0204a9102283
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Wed, Jul 27, 2011 at 4:07 PM, Rick We=
sson <span dir=3D"ltr"><<a href=3D"mailto:rick@support-intelligence.com"=
>rick@support-intelligence.com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
personally, if the software works better (less bugs) then btc will be more =
valuable. offering bounty is orthorginal to finding the right technical lea=
d that will hurd the effort.<div><br></div><div>put a bounty (salary) on th=
e person to lead the effort, not the bugs</div>
</blockquote><div><br>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 symb=
olic gesture to attract developers and get them some coins.=A0 People with =
coins are also more motivated to make the project more=20
valuable, otherwise you have a "tragedy of the commons" problem.<=
br><br>Not that I don't agree Gavin with getting a salary but that'=
s a completely independent issue :)<br><br>JS<br></div></div>
--000e0cd58e98b46e0204a9102283--
|
