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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
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 <drak@zikula.org>) id 1VplKA-0001yg-Tn
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 20:51:34 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of zikula.org
designates 74.125.82.174 as permitted sender)
client-ip=74.125.82.174; envelope-from=drak@zikula.org;
helo=mail-we0-f174.google.com;
Received: from mail-we0-f174.google.com ([74.125.82.174])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VplK9-00087P-UK
for bitcoin-development@lists.sourceforge.net;
Sun, 08 Dec 2013 20:51:34 +0000
Received: by mail-we0-f174.google.com with SMTP id q58so2594804wes.5
for <bitcoin-development@lists.sourceforge.net>;
Sun, 08 Dec 2013 12:51:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=PdP4LuJZ6yIKoFtp9ZVAfzHUH4SQKoimVDafsmEqkUk=;
b=N0tdMl4FCG+oyNKI/cthMA1mTnRcNA+k3DdZ8P8HXn6JUzOhYhX5ncuQrQHVspLU27
9wkW3yl7VNAY1UI1hRy3NBAVU9H5xMF0YMYrt4Gywo2/oGmC6sjBmedUqFBundBfeCEA
kIv1JGJNsh76FAF279HLTWX+r5UiB/IEKbB6bcHDpvZE8FN/wuh/U1k0WmVpaJM1Eh0U
0wSX9EL8D2rt+bglPbDqFZz1edEcVtAzMUyJ3KyCWFlPaq4LyI5eEB3TiJ7dD+aIHQIj
Y/dohCKZivvK3YRLmTG03lr0RdBxq//ErKrESKkpEQUOqo/TGOOWpiB+huUg9SdvLqT6
em3Q==
X-Gm-Message-State: ALoCoQkKyc2QHAG8FpmT7CIXsWseB5C2gUqY/xcrFmBf2gOED3q4RdHm+UNWSsjj5A8s043GXW3J
X-Received: by 10.180.108.162 with SMTP id hl2mr11131249wib.56.1386535887591;
Sun, 08 Dec 2013 12:51:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.93.105 with HTTP; Sun, 8 Dec 2013 12:51:07 -0800 (PST)
In-Reply-To: <CAAS2fgT2x3iLnRiLabPT28eO6rbGuBBgi2s-Yhtgwo+3XWq7+Q@mail.gmail.com>
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>
<CAAS2fgT2x3iLnRiLabPT28eO6rbGuBBgi2s-Yhtgwo+3XWq7+Q@mail.gmail.com>
From: Drak <drak@zikula.org>
Date: Sun, 8 Dec 2013 20:51:07 +0000
Message-ID: <CANAnSg3GeLPyXXK5Osg1hcC7MQ=Na3BWrGCe95ab7UcbeG2Jgw@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f3bac6f0c71d304ed0c0b7a
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: bitcoin.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VplK9-00087P-UK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org,
your thoughts?
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: Sun, 08 Dec 2013 20:51:35 -0000
--e89a8f3bac6f0c71d304ed0c0b7a
Content-Type: text/plain; charset=UTF-8
On 8 December 2013 20:40, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Sun, Dec 8, 2013 at 12:28 PM, Mike Hearn <mike@plan99.net> wrote:
> > Right now I think Sirius still owns DNS for bitcoin.org which is
> nonsense.
> > He needs to pass it on to someone who is actually still involved with the
> > project. Again, the most obvious neutral candidate would be the
> Foundation.
>
> I am opposed to Bitcoin Foundation having control of Bitcoin.org, and
> I think it would be foolish of the foundation to accept it were it
> offered.
>
What do you suggest though? We will need to trust someone (even in a group
each person can act autonomously).
The only thing I can suggest would be to hand the keys to the bitcoin
project lead.
Otherwise, who has admin rights to the code projects
(github/sourceforge/this mailing list)? Those people have proven they can
be trusted so far.
Drak
--e89a8f3bac6f0c71d304ed0c0b7a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 8=
December 2013 20:40, Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mail=
to:gmaxwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>></span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Sun, Dec 8, 2013 at 12:=
28 PM, Mike Hearn <<a href=3D"mailto:mike@plan99.net">mike@plan99.net</a=
>> wrote:<br>
> Right now I think Sirius still owns DNS for <a href=3D"http://bitcoin.=
org" target=3D"_blank">bitcoin.org</a> which is nonsense.<br>
> He needs to pass it on to someone who is actually still involved with =
the<br>
> project. Again, the most obvious neutral candidate would be the Founda=
tion.<br>
<br>
</div>I am opposed to Bitcoin Foundation having control of Bitcoin.org, and=
<br>
I think it would be foolish of the foundation to accept it were it<br>
offered.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">What do you suggest=
though? We will need to trust someone (even in a group each person can act=
autonomously).</div><div class=3D"gmail_extra">The only thing I can sugges=
t would be to hand the keys to the bitcoin project lead.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Otherwise, =
who has admin rights to the code projects (github/sourceforge/this mailing =
list)? Those people have proven they can be trusted so far.</div><div class=
=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Drak</div></div>
--e89a8f3bac6f0c71d304ed0c0b7a--
|
