summaryrefslogtreecommitdiff
path: root/74/70982c66d599adc8b2033263857c1fc6a9ab94
blob: 121a4df6fa81e63d0918f465e83b13e558905ada (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
98
99
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <ibrightly@gmail.com>) id 1Z2lR7-0003Pb-Ih
	for bitcoin-development@lists.sourceforge.net;
	Wed, 10 Jun 2015 19:13:17 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.176 as permitted sender)
	client-ip=209.85.214.176; envelope-from=ibrightly@gmail.com;
	helo=mail-ob0-f176.google.com; 
Received: from mail-ob0-f176.google.com ([209.85.214.176])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z2lR6-0002Ky-R0
	for bitcoin-development@lists.sourceforge.net;
	Wed, 10 Jun 2015 19:13:17 +0000
Received: by obbqz1 with SMTP id qz1so42017173obb.3
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 10 Jun 2015 12:13:11 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.73.199 with SMTP id n7mr4179411oev.39.1433963591403; Wed,
	10 Jun 2015 12:13:11 -0700 (PDT)
Received: by 10.76.177.164 with HTTP; Wed, 10 Jun 2015 12:13:11 -0700 (PDT)
In-Reply-To: <20150610184725.GP27932@nl.grid.coop>
References: <1943127.DBnVxmfOIh@1337h4x0r>
	<20150610093556.GA11409@amethyst.visucore.com>
	<557869F9.8030109@AndySchroder.com>
	<CAAre=yQSkFAHLfJ0h2rQY5vOFExSq2GDiRV32qe=EEVYOxCpqg@mail.gmail.com>
	<20150610184725.GP27932@nl.grid.coop>
Date: Wed, 10 Jun 2015 15:13:11 -0400
Message-ID: <CAAre=yRAzwBswqnpMcpL7dU+LEh5HM7u_FGu4nu2kt94CpwBKg@mail.gmail.com>
From: Ivan Brightly <ibrightly@gmail.com>
To: Troy Benjegerdes <hozer@hozed.org>
Content-Type: multipart/alternative; boundary=001a113601047c905a05182eaa2b
X-Spam-Score: -0.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
	(ibrightly[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1Z2lR6-0002Ky-R0
Cc: Andy Schroder <info@andyschroder.com>,
	bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough
 to host this list?
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, 10 Jun 2015 19:13:17 -0000

--001a113601047c905a05182eaa2b
Content-Type: text/plain; charset=UTF-8

"My opinion is the most sustainable solution would be to identify a
team of admins and use something like Digital Ocean's new team accounts
feature and have someone like SolidX contribute funds for the servers
and a few hours a week from one of their sysadmins to the team."

This is a perfectly fine option. Alternatively, if the paid mailing list
option is preferred, I'd suggest Intermedia:

--001a113601047c905a05182eaa2b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><span style=3D"font-size:12.800=
0001907349px">&quot;My opinion is the most sustainable solution would be to=
 identify a</span><br style=3D"font-size:12.8000001907349px"><span style=3D=
"font-size:12.8000001907349px">team of admins and use something like Digita=
l Ocean&#39;s new team accounts</span><br style=3D"font-size:12.80000019073=
49px"><span style=3D"font-size:12.8000001907349px">feature and have someone=
 like SolidX contribute funds for the servers</span><br style=3D"font-size:=
12.8000001907349px"><span style=3D"font-size:12.8000001907349px">and a few =
hours a week from one of their sysadmins to the team.&quot;</span><br></div=
><div class=3D"gmail_extra"><span style=3D"font-size:12.8000001907349px"><b=
r></span></div><div class=3D"gmail_extra"><span style=3D"font-size:12.80000=
01907349px">This is a perfectly fine option. Alternatively, if the paid mai=
ling list option is preferred, I&#39;d suggest Intermedia:</span></div><div=
 class=3D"gmail_extra"><span style=3D"font-size:12.8000001907349px"><br></s=
pan></div></div>

--001a113601047c905a05182eaa2b--