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: Sun, 16 Oct 2016 16:56:36 +0200 [thread overview]
Message-ID: <1564094.f9m6WVpBae@strawberry> (raw)
In-Reply-To: <CAK51vgDRngpTEtnQpwCKN8Jznj2T-HSLEkXD4Z=JiNhV1BOONg@mail.gmail.com>
On Saturday, 15 October 2016 17:02:30 CEST Marco Falke wrote:
> >> BIP 2 does not forbid you to release your work under PD in
> >> legislations where this is possible
> >
> > It does, actually.
>
> Huh, I can't find it in the text I read. The text mentions "not
> acceptable", but I don't read that as "forbidden".
You suggest that a person can dual license something under both CC-BY-SA as
well as under public domain.
That means you don't understand copyright,
See, all licenses are based on you having copyright. In contrast; public
domain is not a license, it means a certain text does not have copyright.
Public domain is the lack of copyright.
One text can not at the same time have copyright and not have copyright,
making your assumption impossible.
Hence, with PD not explicitly being allowed, you can't use PD.
Personally I prefer copyleft licenses, so the lack of PD is fine with me. The
lack of a good copyleft we can use in BIPs is what got me involved in this
discussion in the first place.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2016-10-16 14:56 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
2016-10-15 15:02 ` Marco Falke
2016-10-16 14:56 ` Tom Zander [this message]
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=1564094.f9m6WVpBae@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