summaryrefslogtreecommitdiff
path: root/df/0b0ba5cc93df45803a342ed2d11e03879e0b2a
blob: 58eec2aa5653e64b36959be7f7f4b0b8467cc212 (plain)
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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <joel.kaartinen@gmail.com>) id 1Qm7iA-0008Io-BM
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 Jul 2011 17:15:58 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.171 as permitted sender)
	client-ip=209.85.215.171; envelope-from=joel.kaartinen@gmail.com;
	helo=mail-ey0-f171.google.com; 
Received: from mail-ey0-f171.google.com ([209.85.215.171])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Qm7i9-00043p-By
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 Jul 2011 17:15:58 +0000
Received: by eye22 with SMTP id 22so2152878eye.2
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 27 Jul 2011 10:15:51 -0700 (PDT)
Received: by 10.204.23.67 with SMTP id q3mr9951bkb.338.1311786950961;
	Wed, 27 Jul 2011 10:15:50 -0700 (PDT)
Received: from [91.153.53.68] (a91-153-53-68.elisa-laajakaista.fi
	[91.153.53.68])
	by mx.google.com with ESMTPS id h7sm24812bkd.12.2011.07.27.10.15.48
	(version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 10:15:49 -0700 (PDT)
From: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com>
To: Rick Wesson <rick@support-intelligence.com>
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>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 27 Jul 2011 20:15:44 +0300
Message-ID: <1311786944.9830.77.camel@mei>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.6 (-)
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
	(joel.kaartinen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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
X-Headers-End: 1Qm7i9-00043p-By
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:15:58 -0000

When I first found bitcoin, I was a bit surprised there were no paid by
community developers working on it. However, the bounties would be a
more democratic way of guiding the progress as well as allow things to
happen without a stable flow of money.

Having said that, if it's feasible, having someone hired full time to
work on the software would be great. I'm too much of a newcomer myself
to be able to provide any financial support for that though. I could
most likely contribute towards some bug bounties but if there was a bug
I'd want to offer bounty for, I'd be fixing it myself already.

- Joel

On Wed, 2011-07-27 at 09:07 -0700, Rick Wesson 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
> 
> 
> -rick
> 
> 
> On Wed, Jul 27, 2011 at 7:28 AM, Luke-Jr <luke@dashjr.org> wrote:
>         On Wednesday, July 27, 2011 10:20:07 AM John Smith wrote:
>         > On Wed, Jul 27, 2011 at 11:14 AM, Joel Joonatan Kaartinen
>         > <joel.kaartinen@gmail.com> wrote:
>         > > Perhaps even add a way for anyone add to the bounty
>         attached to a bug on
>         > > the bug tracker? Also, a listing page for bugs with their
>         bounties might
>         > > be nice too.
>         >
>         > Good idea. I'm not sure if the github bug tracker supports
>         extension
>         > attributes, but it'd be a great place to add it. Also,
>         people can let know
>         > that they're already working on a feature using a comment,
>         to prevent
>         > double work.
>         
>         
>         I'm not sure a few small bounties would justify agreeing to
>         GitHub's steep
>         demand for potentially unlimited money in their terms of
>         service...
>         
>         
>         ------------------------------------------------------------------------------
>         Got Input?   Slashdot Needs You.
>         Take our quick survey online.  Come on, we don't ask for help
>         often.
>         Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>         http://p.sf.net/sfu/slashdot-survey
>         _______________________________________________
>         Bitcoin-development mailing list
>         Bitcoin-development@lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>         
> 
> 
> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development