From: Ivan Brightly <ibrightly@gmail•com>
To: Troy Benjegerdes <hozer@hozed•org>
Cc: Andy Schroder <info@andyschroder•com>,
bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 15:13:11 -0400 [thread overview]
Message-ID: <CAAre=yRAzwBswqnpMcpL7dU+LEh5HM7u_FGu4nu2kt94CpwBKg@mail.gmail.com> (raw)
In-Reply-To: <20150610184725.GP27932@nl.grid.coop>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
"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:
[-- Attachment #2: Type: text/html, Size: 1038 bytes --]
next prev parent reply other threads:[~2015-06-10 19:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:25 xor
2015-06-10 9:35 ` Wladimir J. van der Laan
2015-06-10 16:46 ` Andy Schroder
2015-06-10 18:02 ` Troy Benjegerdes
2015-06-10 18:41 ` Andy Schroder
[not found] ` <DB12E925-11C6-4A82-BC81-FB3DA26BC5B3@newcastle.ac.uk>
[not found] ` <20150610185810.GQ27932@nl.grid.coop>
[not found] ` <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-06-11 1:46 ` Troy Benjegerdes
2015-06-10 18:28 ` Ivan Brightly
2015-06-10 18:47 ` Troy Benjegerdes
2015-06-10 19:13 ` Ivan Brightly [this message]
2015-06-10 18:36 ` s7r
2015-06-10 18:59 ` Andy Schroder
2015-06-10 19:03 ` Peter Todd
2015-06-10 19:12 ` Andy Schroder
2015-06-10 19:20 ` Peter Todd
2015-06-10 19:36 ` Andy Schroder
2015-06-10 19:43 ` Peter Todd
2015-06-10 20:03 ` Andy Schroder
2015-06-10 19:54 ` Jeff Garzik
2015-06-11 9:27 ` Wladimir J. van der Laan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAre=yRAzwBswqnpMcpL7dU+LEh5HM7u_FGu4nu2kt94CpwBKg@mail.gmail.com' \
--to=ibrightly@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=hozer@hozed$(echo .)org \
--cc=info@andyschroder$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox