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 ) 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 ; 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 To: Luke-Jr In-Reply-To: <201107271028.28057.luke@dashjr.org> References: <1311765274.9830.3.camel@mei> <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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 > > 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... >