From: Daniel Robinson <danrobinson010@gmail•com>
To: Adam Ficsor <adam.ficsor73@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Possible change to the MIT license
Date: Tue, 13 Feb 2018 17:46:18 +0000 [thread overview]
Message-ID: <CAD438HtV4UUKZ=UsHQky8kYfgLZQCgJ0aQoe15KSBqNcQujk1g@mail.gmail.com> (raw)
In-Reply-To: <CAEPKjgfJxFebb2NaoT1Jet9_wzcpTbQvq0jk+d6Qi6DZExJB=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
Custom open-source licenses are basically never a good idea. Every
deviation in wording from universally-accepted open-source licensing terms
is a major compliance headache from the perspective of any organization
trying to use the software. You don’t want users having to clear their use
of Bitcoin Core through their employers’ legal departments, whether or not
they would ultimately approve that use. For that reason alone I think such
a change is not viable, no matter how you phrased it.
On Tue, Feb 13, 2018 at 9:27 AM Adam Ficsor via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> I agree with the opposition on changing the license, because of the
> branding attacks.
>
> However having two coins with the same Proof Of Work is a zero sum game
> from a security point of view. It may not be a bad idea to consider
> changing the license in a way that only limits cryptocurrencies with the
> same Proof Of Work, since they directly affect the stability and security
> of Bitcoin.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1641 bytes --]
next prev parent reply other threads:[~2018-02-13 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 17:25 Adam Ficsor
2018-02-13 17:46 ` Daniel Robinson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 10:09 Damian Williamson
2018-02-13 12:25 JOSE FEMENIAS CAÑUELO
2018-02-13 14:25 ` Natanael
2018-02-13 15:24 ` Jameson Lopp
2018-02-13 15:37 ` Brian Lockhart
2018-02-13 15:45 ` Jameson Lopp
2018-02-13 17:04 ` Patrick Murck
2018-02-13 15:45 ` Aymeric Vitte
2018-02-13 15:47 ` Bedri Ozgur Guler
2018-02-13 17:28 ` Felix Wolfsteller
2018-02-13 19:08 ` Cory Fields
2018-02-13 19:08 ` CryptAxe
2018-02-13 15:22 ` Aymeric Vitte
2018-02-13 17:53 ` Luke Dashjr
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='CAD438HtV4UUKZ=UsHQky8kYfgLZQCgJ0aQoe15KSBqNcQujk1g@mail.gmail.com' \
--to=danrobinson010@gmail$(echo .)com \
--cc=adam.ficsor73@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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