From: Christian Decker <decker.christian@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Hosting of compiled bitcoin client
Date: Mon, 15 Oct 2012 00:09:48 +0200 [thread overview]
Message-ID: <CALxbBHW9wwe9yEUZp0pEzt+optFVmmRF27rBCYoLCeb8=p4iqg@mail.gmail.com> (raw)
In-Reply-To: <201210142202.47221.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Being an international team I'm pretty sure we can find someone who is in a
more permissive country.
Would someone knowledgeable point us to the specific laws, so that we can
look it up in our respective jurisdiction?
Regards,
Chris
On Mon, Oct 15, 2012 at 12:02 AM, Luke-Jr <luke@dashjr•org> wrote:
> 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
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2167 bytes --]
next prev parent reply other threads:[~2012-10-14 22:10 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
2012-10-14 22:09 ` Christian Decker [this message]
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='CALxbBHW9wwe9yEUZp0pEzt+optFVmmRF27rBCYoLCeb8=p4iqg@mail.gmail.com' \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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