From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Hosting of compiled bitcoin client
Date: Sun, 14 Oct 2012 22:02:45 +0000 [thread overview]
Message-ID: <201210142202.47221.luke@dashjr.org> (raw)
In-Reply-To: <CA+QPp0rDb9cKThWZuvC=OuvKmh4YBWLVAcP6rFjt0g47tLaAoA@mail.gmail.com>
On Sunday, October 14, 2012 8:52:33 PM Kyle Henderson wrote:
> Given that sourceforge has shown to restrict access to a number of
> countries at the request of the USA
This needs some clarification. If the USA has "requested" it, then presumably
there's some legality involved, and our US developers shouldn't be made liable
for it. The specific reason SourceForge has restricted access should be made
known so non-US developers (or gitian builders) can evaluate their own laws
and hopefully at least one will be in a jurisdiction that allows it.
But GitHub is also US-located, so hosting it there may be a problem too.
Luke
next prev parent reply other threads:[~2012-10-14 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 20:52 Kyle Henderson
2012-10-14 22:02 ` Luke-Jr [this message]
2012-10-14 22:09 ` Christian Decker
2012-10-14 22:33 ` Gregory Maxwell
2012-10-14 22:49 ` Mike Hearn
2012-10-20 7:43 Mark Lister
2012-10-20 8:33 ` Wladimir
2012-10-20 14:19 ` Caleb James DeLisle
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=201210142202.47221.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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