Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XJufY-0007kp-9w for bitcoin-development@lists.sourceforge.net; Wed, 20 Aug 2014 01:26:32 +0000 X-ACL-Warn: Received: from nl.grid.coop ([50.7.166.116]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XJufX-0006QB-8E for bitcoin-development@lists.sourceforge.net; Wed, 20 Aug 2014 01:26:32 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by nl.grid.coop with local; Tue, 19 Aug 2014 20:26:23 -0500 id 000000000006E269.0000000053F3F93F.00000D6F Date: Tue, 19 Aug 2014 20:26:23 -0500 From: Troy Benjegerdes To: Wladimir Message-ID: <20140820012623.GN22640@nl.grid.coop> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1XJufX-0006QB-8E Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Reconsidering github 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, 20 Aug 2014 01:26:32 -0000 On Tue, Aug 19, 2014 at 04:58:48PM +0200, Wladimir wrote: > On Tue, Aug 19, 2014 at 2:02 PM, Jeff Garzik wrote: > > It would be nice if the issues and git repo for Bitcoin Core were not > > on such a centralized service as github, nice and convenient as it is. > > Despite my complaining about github, I don't like the idea of moving > somewhere else. The current way of working - to use github for storing > the tree, and use a custom script for signing+merging - is fine with > me. > > Github has a low barrier to contribution. Almost every open source > developer already has a github account. Switching to something > self-hosted makes it more difficult for people to contribute. > > Plus if we have to take the hosting upon ourselves, we have to handle > sysadmin work ourselves as well. That's not a good use of the limited > manpower available. > > Also it will be a lot of work to migrate over all the current issues > and pulls. I don't look forward to that. I don't see the point of > this, sorry. > > Wladimir If a project cannot be organized enough to run its own hosting/web presense/ counterintelligence/security that starts with installing an OS and patching kernels, then it is really not wise for me to trust my financial future to software written by such a group. There is a great deal of 'work' that is really quite pointless, particularly in regards to claims I see about security that are irrelevant unless you have the understanding that comes from operating and running your own servers. This includes running DDOS protection, so no cloudflare. If bitcoin wants to become irrelevant, then by all means, continue to depend on github and all the unknown attack surface it exposes. Those of us that do run our own servers will migrate to higher quality alternatives. -- ---------------------------------------------------------------------------- Troy Benjegerdes 'da hozer' hozer@hozed.org 7 elements earth::water::air::fire::mind::spirit::soul grid.coop Never pick a fight with someone who buys ink by the barrel, nor try buy a hacker who makes money by the megahash