Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.169 as permitted sender)
	client-ip=209.85.223.169; envelope-from=saivann@gmail.com;
	helo=mail-ie0-f169.google.com; 
Message-ID: <52A4E199.3000209@gmail.com>
Date: Sun, 08 Dec 2013 16:16:09 -0500
From: =?windows-1252?Q?Sa=EFvann_Carignan?= <saivann@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <52A3C8A5.7010606@gmail.com>	<1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net>	<52A435EA.7090405@gmail.com>
	<201312081237.24473.luke@dashjr.org>	<CANAnSg2OrmQAcZ+cZdtQeADicH3U29QOgYPfP1AQhOMP6+P1wg@mail.gmail.com>	<CAAS2fgR0khyJxmz9c2Oc87hOFgiNuiPJuaeugGajdo_EcKEW9w@mail.gmail.com>
	<CANEZrP3+AowZZS1=hAkx0KODiT-vbcRKyZaHOE2CWaJk3y5-Dw@mail.gmail.com>
In-Reply-To: <CANEZrP3+AowZZS1=hAkx0KODiT-vbcRKyZaHOE2CWaJk3y5-Dw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org,
 your thoughts?
Precedence: list


> Issues that would need to be resolved:
> 
> 1) Who pays for it? Most obvious answer: Foundation. However there's
> currently a fairly clear line between the foundation website and the
> bitcoin.org <http://bitcoin.org> website. I personally am fine with the
> bitcoin foundation funding the website, it's a lot closer to the bitcoin
> community than github. But some people might care. So next step would be
> to contact the Foundation board and see if they're willing to fund it.

Actually I might find way to fund it. But I needed to have ACK &
comments from developers before anything.

> 2) Anti-DoS? I assume github handles this at the moment, though I doubt
> there's anything to be gained from DoSing the informational website

That is a fair question, we will need anti-DDoS. Unless something better
(and affordable) can be recommended, this would yet put another Bitcoin
website under CloudFlare.

> 4) Who admins it?

Obviously, I thought it would be important that the server is owned by
someone who can be trusted, with ssh access for all core developers.

> 5) Who controls DNS for it?

I'm not sure we'll get any change on this level. I have no idea if the
domain is in good hands, except for the fact that nothing bad happened
thus far. If anything, moving it to core developers (as intended when
the domain was registered) would make more sense IMO. But again, is it
possible, I don't know.