From: Ahmed Zsales <ahmedzsales18@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Tue, 1 Sep 2015 23:02:36 +0100 [thread overview]
Message-ID: <CADr=VrQeQ2=Htcen-oJrJWWhf5aQ8-cjYK28ic1UWNFWMf2nDQ@mail.gmail.com> (raw)
In-Reply-To: <55E61A64.2030609@bitcoins.info>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
Russ,
The general points and questions you have raised are covered in the draft
BIP:
https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing
Regards,
Ahmed
On Tue, Sep 1, 2015 at 10:36 PM, Milly Bitcoin via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> We considered whether data existing before a licence change would be
>> covered, but we hadn't factored the potential need for gaining
>> permissions for a change to be considered effective.
>>
>> We have proposed that miners be the main beneficiaries of licensing and
>> there is a consideration on whether they should vote to adopt the new
>> terms. While not the preferred route, that would overcome any issues to
>> what is an otherwise honest 'error and omission.' There doesn't seem to
>> be anyone who could claim to have suffered any economic losses so this
>> may not be an issue. It merits further investigation.
>>
>
> Like I said, you need to talk to a lawyer. What exactly would be the
> purpose of any license? How can someone be a "beneficiary" to a license
> when you can't even explain who holds the license to begin with? How do
> they "benefit?" I don't see any purpose to putting a license on the Core
> software or the blockchain because nobody can explain who actually holds
> the license and there is no mechanism to enforce any license and there is
> no revenue to be shared. The whole discussion makes no sense.
>
> Russ
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2728 bytes --]
next prev parent reply other threads:[~2015-09-01 22:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 13:30 Ahmed Zsales
2015-09-01 13:43 ` Milly Bitcoin
2015-09-01 13:50 ` Bryan Bishop
2015-09-01 15:11 ` Ahmed Zsales
2015-09-01 16:05 ` Natanael
2015-09-01 17:39 ` Luke Dashjr
2015-09-01 18:12 ` Btc Drak
2015-09-01 19:36 ` Ahmed Zsales
2015-09-01 21:36 ` Milly Bitcoin
2015-09-01 22:02 ` Ahmed Zsales [this message]
2015-09-01 22:42 ` Milly Bitcoin
2015-09-01 23:21 ` Ahmed Zsales
2015-09-01 23:40 ` Milly Bitcoin
2015-09-01 22:02 ` Btc Drak
2015-09-01 22:11 ` Ahmed Zsales
2015-09-01 22:47 ` Btc Drak
2015-09-01 22:20 ` Natanael
2015-09-01 22:28 ` Ahmed Zsales
2015-09-01 21:51 ` Wladimir J. van der Laan
2015-09-01 23:39 ` hurricanewarn1
2015-09-02 8:56 ` Warren Togami Jr.
2015-09-02 20:28 ` Ahmed Zsales
2015-09-02 20:58 ` Milly Bitcoin
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='CADr=VrQeQ2=Htcen-oJrJWWhf5aQ8-cjYK28ic1UWNFWMf2nDQ@mail.gmail.com' \
--to=ahmedzsales18@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