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
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
|
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 1QmK8c-0003GG-Oa
for bitcoin-development@lists.sourceforge.net;
Thu, 28 Jul 2011 06:32:06 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.161.175 as permitted sender)
client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com;
helo=mail-gx0-f175.google.com;
Received: from mail-gx0-f175.google.com ([209.85.161.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1QmK8a-0003bs-G1
for bitcoin-development@lists.sourceforge.net;
Thu, 28 Jul 2011 06:32:06 +0000
Received: by gxk3 with SMTP id 3so2132886gxk.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 27 Jul 2011 23:31:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.116.1 with SMTP id o1mr470220ybc.321.1311834719027; Wed,
27 Jul 2011 23:31:59 -0700 (PDT)
Received: by 10.151.13.9 with HTTP; Wed, 27 Jul 2011 23:31:58 -0700 (PDT)
In-Reply-To: <1311808059.2294.55.camel@Desktop666>
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>
<1311786944.9830.77.camel@mei>
<CABsx9T1667dxUj_iRtgbUR0ymBVOaADkGQU_CMF7z7e1-ctRcQ@mail.gmail.com>
<1311808059.2294.55.camel@Desktop666>
Date: Thu, 28 Jul 2011 06:31:58 +0000
Message-ID: <CAJNQ0sumck6TF1Jj0dFy77aRiWw+3mAc6eUSi3rs9qAKbHXqNw@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: multipart/alternative; boundary=000e0cd3b0406e84c204a91b52e6
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
1.7 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
[URIs: bluematt.me]
-0.8 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QmK8a-0003bs-G1
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: Thu, 28 Jul 2011 06:32:06 -0000
--000e0cd3b0406e84c204a91b52e6
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jul 27, 2011 at 11:07 PM, Matt Corallo <bitcoin-list@bluematt.me>wrote:
> On Thu, 2011-07-28 at 08:45 +1000, Gavin Andresen wrote:
> > "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.
>
> I do think it would motivate some people to fix a bug or two, though I
> would say it wouldn't encourage long-term contributors, just a bunch of
> hacked together patches which "fix" a bug.
>
Which, in many cases, is enough. Many times, fixing a bug is a few hours of
debugging, then fixing three lines of codes.
Sometimes it just takes a monkey to sit behind a PC and bash on it frantic
enough (with a debugger) to find and fix bugs :-) Competition to fix bugs is
(up to a certain level) good, it gets people off their ass. But I think the
competition problem is very hypothetical. It assumes there will suddenly be
*a lot* of people that want to fix the same bug. That's unrealistic...
Writing a few test-cases (which is better than the 0 we have now) also won't
take a Linus-level developer to work on it full time. A reasonable dev just
needs to put some time into it.
That leaves the more difficult work to the lead devs.
For a distributed currency I must say there is very little belief here in a
distributed process. Yes, you can also start a company and hire people to
work on it full time, but then they'll be working on helping customer not
solving bugs of the issue tracker (which might have an overlap, but not
necessarily). And it also isn't clear whether changes are contributed back
to the project.
You should not underestimate the open source community. There's a lot of
smart students eager to work on interesting, high-impact projects. Bitcoin
certainly fits that description, but the problem is that Bitcoin isn't
really that known yet with devs, and they need a little push to get
involved. And to work on the current code-base, because usually they will
look at the code and decide it's a piece of crap and want to rewrite it (new
people syndrome).
Yes, there might be one-time-and-run-off flakes, but hey that's life... you
only need to gain a few (semi)dedicated devs from it anyway, not recruit an
army of loyal minions.
I'm not saying this push has to be bounties. It could be a nice page, for
example just posting the bounties on the forum is a start, but certainly not
enough. They just get buried in troll poop, and a lot of the forum users are
... *psychological analysis removed*. You really want to reach out somehow.
It should at least have a nice page that attracts people on the
bitcoin.orgsite, and explains why you should work on Bitcoin (because
the project is so
awesome and fun) and some form of attribution (not just a mention in the
gitlog, but bounties is only one option) if you do manage to fix a bug.
Heck a scoreboard with "number of bugs squished" could be a start :-) We
need to be creative here...
JS
--000e0cd3b0406e84c204a91b52e6
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 11:07 PM, Matt C=
orallo <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-list@bluematt.me">bi=
tcoin-list@bluematt.me</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">
<div class=3D"im">On Thu, 2011-07-28 at 08:45 +1000, Gavin Andresen wrote:<=
br>
</div><div class=3D"im">> "A couple of bitcoins to fix a bug" =
sounds to me like nothing but<br>
> trouble for whoever is in charge of awarding the bounties, but maybe<b=
r>
> I'm just anti-bounty because spending 2 or 3 hours and getting $30=
<br>
> worth of bitcoins for fixing a bug wouldn't motivate me.<br>
<br>
</div>I do think it would motivate some people to fix a bug or two, though =
I<br>
would say it wouldn't encourage long-term contributors, just a bunch of=
<br>
hacked together patches which "fix" a bug. <br></blockquote><div>=
<br>Which, in many cases, is enough. Many times, fixing a bug is a few hour=
s of debugging, then fixing three lines of codes. <br><br>Sometimes it just=
takes a monkey to sit behind a PC and bash on it frantic enough (with a de=
bugger) to find and fix bugs :-) Competition to fix bugs is (up to a certai=
n level) good, it gets people off their ass. But I think the competition pr=
oblem is very hypothetical. It assumes there will suddenly be *a lot* of pe=
ople that want to fix the same bug. That's unrealistic... <br>
<br>Writing a few test-cases (which is better than the 0 we have now) also =
won't take a Linus-level developer to work on it full time. A reasonabl=
e dev just needs to put some time into it.<br><br>That leaves the more diff=
icult work to the lead devs. <br>
<br>For a distributed currency I must say there is very little belief here =
in a distributed process. Yes, you can also start a company and hire people=
to work on it full time, but then they'll be working on helping custom=
er not solving bugs of the issue tracker (which might have an overlap, but =
not necessarily). And it also isn't clear whether changes are contribut=
ed back to the project.<br>
<br>You should not underestimate the open source community. There's a l=
ot of smart students eager to work on interesting, high-impact projects. Bi=
tcoin certainly fits that description, but the problem is that Bitcoin isn&=
#39;t really that known yet with devs, and they need a little push to get i=
nvolved. And to work on the current code-base, because usually they will lo=
ok at the code and decide it's a piece of crap and want to rewrite it (=
new people syndrome).<br>
<br>Yes, there might be one-time-and-run-off flakes, but hey that's lif=
e... you only need to gain a few (semi)dedicated devs from it anyway, not r=
ecruit an army of loyal minions.<br><br>I'm not saying this push has to=
be bounties. It could be a nice page, for example just posting the bountie=
s on the forum is a start, but certainly not enough. They just get buried i=
n troll poop, and a lot of the forum users are ... *psychological analysis =
removed*. You really want to reach out somehow.<br>
<br>It should at least have a nice page that attracts people on the <a href=
=3D"http://bitcoin.org">bitcoin.org</a> site, and explains why you should w=
ork on Bitcoin (because the project is so awesome and fun) and some form of=
attribution (not just a mention in the gitlog, but bounties is only one op=
tion) if you do manage to fix a bug.<br>
<br>Heck a scoreboard with "number of bugs squished" could be a s=
tart :-) We need to be creative here...<br><br>JS<br></div></div><br>
--000e0cd3b0406e84c204a91b52e6--
|
