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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1Qm4y5-0002Gb-V8
for bitcoin-development@lists.sourceforge.net;
Wed, 27 Jul 2011 14:20:13 +0000
Received-SPF: pass (sog-mx-4.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-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1Qm4y5-00013M-8l
for bitcoin-development@lists.sourceforge.net;
Wed, 27 Jul 2011 14:20:13 +0000
Received: by gxk3 with SMTP id 3so1401164gxk.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 27 Jul 2011 07:20:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.69.27 with SMTP id r27mr62069yba.435.1311776407675; Wed,
27 Jul 2011 07:20:07 -0700 (PDT)
Received: by 10.151.13.9 with HTTP; Wed, 27 Jul 2011 07:20:07 -0700 (PDT)
In-Reply-To: <1311765274.9830.3.camel@mei>
References: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
<CAJNQ0sshm=q==++MVXEEkMDHX60HJxpFoR3CF3zK4NvFy2-rsQ@mail.gmail.com>
<1311765274.9830.3.camel@mei>
Date: Wed, 27 Jul 2011 14:20:07 +0000
Message-ID: <CAJNQ0su9Qbi=zMaJA0G77UuHkXBy8k7YLBd4cec=Rc_-FGPBjA@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd5905acde44a04a90dbe29
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: 1Qm4y5-00013M-8l
Cc: Bitcoin Dev <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 14:20:14 -0000
--000e0cd5905acde44a04a90dbe29
Content-Type: text/plain; charset=ISO-8859-1
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.
The biggest problem will be organizational, in getting the BTC together for
bounties; only a high profile member such as Gavin will have enough trust to
ask for support. Or maybe there's something left in the faucet? :-)
Unrelated: what also might help is publishing a roadmap. Plan a few "bug fix
only" releases before scheduling addition of new features. It's also helpful
for people that wonder that direction the project is going in...
JS
--000e0cd5905acde44a04a90dbe29
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Wed, Jul 27, 2011 at 11:14 AM, Joel Joonatan Kaartinen <span dir=3D"ltr"=
><<a href=3D"mailto:joel.kaartinen@gmail.com">joel.kaartinen@gmail.com</=
a>></span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex;">
Perhaps even add a way for anyone add to the bounty attached to a bug on<br=
>
the bug tracker? Also, a listing page for bugs with their bounties might<br=
>
be nice too.<br></blockquote><div><br>Good idea. I'm not sure if the gi=
thub bug tracker supports extension attributes, but it'd be a great pla=
ce to add it. Also, people can let know that they're already working on=
a feature using a comment, to prevent double work.<br>
<br>The biggest problem will be organizational, in getting the BTC together=
for bounties; only a high profile member such as Gavin will have enough tr=
ust to ask for support. Or maybe there's something left in the faucet? =
:-)<br>
<br>Unrelated: what also might help is publishing a roadmap. Plan a few &qu=
ot;bug fix only" releases before scheduling addition of new features. =
It's also helpful for people that wonder that direction the project is =
going in...<br>
<br>JS <br><br></div></div>
--000e0cd5905acde44a04a90dbe29--
|
