From: Tom Zander <tomz@freedommail•ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 revival and rework
Date: Sat, 15 Oct 2016 16:21:41 +0200 [thread overview]
Message-ID: <1866359.UpcIIOnrOv@strawberry> (raw)
In-Reply-To: <CAK51vgAyuW+832F7+O-ZB9pusp=si-u_gATgTJbyEXnrb08Xqg@mail.gmail.com>
On Saturday, 15 October 2016 14:12:09 CEST Marco Falke wrote:
> On Sat, Oct 15, 2016 at 1:00 PM, Tom Zander via bitcoin-dev
>
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> > My suggestion (sorry for not explaining it better) was that for BIPS to
> > be a public domain (aka CC0) and a CC-BY option and nothing else.
>
> Indeed, we agree that BIPs should be licensed as permissive as
> possible. Still, I wonder why you chose otherwise with BIP 134.
> (Currently OPL and CC-BY-SA)
OPL was the only allowed option apart from CC0.
I dual licensed it so future acceptance of the CC-BY-SA one may mean someone
can just remove the OPL from the BIP and no futher action or permission is
needed from all the authors.
> BIP 2 does not forbid you to release your work under PD in
> legislations where this is possible
It does, actually.
> One
> of the goals of BIP 2 is to no longer allow PD as the only copyright
> option.
That's odd as PD was never the only copyright option.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2016-10-15 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 6:36 Luke Dashjr
2016-09-24 9:41 ` Tom
2016-10-15 10:25 ` Marco Falke
[not found] ` <CAK51vgAhpOFQRgnSxrNrP1JyhBZA3dr7mWKYKD15h0xgO6rR5A@mail.gmail.com>
2016-10-15 11:00 ` Tom Zander
2016-10-15 12:12 ` Marco Falke
2016-10-15 14:21 ` Tom Zander [this message]
2016-10-15 15:02 ` Marco Falke
2016-10-16 14:56 ` Tom Zander
2016-10-15 13:01 ` 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=1866359.UpcIIOnrOv@strawberry \
--to=tomz@freedommail$(echo .)ch \
--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