summaryrefslogtreecommitdiff
path: root/48/46a98a89b40d2c130d9b3f9e8425820750e1aa
blob: 7879b358f79f8a1406c3dcaaefc9c4892f559dab (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <joel.kaartinen@gmail.com>) id 1Qm5KH-0003VX-5N
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 Jul 2011 14:43:09 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.47 as permitted sender)
	client-ip=209.85.215.47; envelope-from=joel.kaartinen@gmail.com;
	helo=mail-ew0-f47.google.com; 
Received: from mail-ew0-f47.google.com ([209.85.215.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Qm5KC-00059y-UN
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 Jul 2011 14:43:07 +0000
Received: by ewy5 with SMTP id 5so1952573ewy.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 27 Jul 2011 07:42:58 -0700 (PDT)
Received: by 10.204.136.129 with SMTP id r1mr553149bkt.204.1311777778519;
	Wed, 27 Jul 2011 07:42:58 -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 i1sm408516bku.54.2011.07.27.07.42.56
	(version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 07:42:57 -0700 (PDT)
From: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com>
To: Luke-Jr <luke@dashjr.org>
In-Reply-To: <201107271028.28057.luke@dashjr.org>
References: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
	<1311765274.9830.3.camel@mei>
	<CAJNQ0su9Qbi=zMaJA0G77UuHkXBy8k7YLBd4cec=Rc_-FGPBjA@mail.gmail.com>
	<201107271028.28057.luke@dashjr.org>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 27 Jul 2011 17:42:54 +0300
Message-ID: <1311777774.9830.14.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: 1Qm5KC-00059y-UN
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 14:43:09 -0000

As it's unlikely to be an automated system anyway, I do not see why
people claiming the bounties would need to agree with the GitHub TOS.
Besides which, I suspect most people contributing to bitcoin already
have agreed to it.

Although, if GitHub can't support the feature, it could be an argument
for setting up a bug tracker unrelated to GitHub.

- Joel

On Wed, 2011-07-27 at 10:28 -0400, Luke-Jr 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...
>