1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
Return-Path: <tomz@freedommail.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E164393D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 14:56:42 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mx-out03.mykolab.com (mx.kolabnow.com [95.128.36.1])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 71B70D3
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 14:56:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at kolabnow.com
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
Received: from mx05.mykolab.com (mx05.mykolab.com [10.20.7.161])
by mx-out03.mykolab.com (Postfix) with ESMTPS id 04CA622CA0
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 Oct 2016 16:56:38 +0200 (CEST)
From: Tom Zander <tomz@freedommail.ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Date: Sun, 16 Oct 2016 16:56:36 +0200
Message-ID: <1564094.f9m6WVpBae@strawberry>
In-Reply-To: <CAK51vgDRngpTEtnQpwCKN8Jznj2T-HSLEkXD4Z=JiNhV1BOONg@mail.gmail.com>
References: <201609240636.01968.luke@dashjr.org>
<1866359.UpcIIOnrOv@strawberry>
<CAK51vgDRngpTEtnQpwCKN8Jznj2T-HSLEkXD4Z=JiNhV1BOONg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sun, 16 Oct 2016 14:57:52 +0000
Subject: Re: [bitcoin-dev] BIP 2 revival and rework
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2016 14:56:43 -0000
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
|
