From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8A55387A for ; Sat, 15 Oct 2016 12:12:13 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from postout2.mail.lrz.de (postout2.mail.lrz.de [129.187.255.138]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BECA0A5 for ; Sat, 15 Oct 2016 12:12:12 +0000 (UTC) Received: from lxmhs52.srv.lrz.de (localhost [127.0.0.1]) by postout2.mail.lrz.de (Postfix) with ESMTP id 3sx3Hb1wl6zyVC for ; Sat, 15 Oct 2016 14:12:11 +0200 (CEST) Authentication-Results: postout.lrz.de (amavisd-new); dkim=pass (2048-bit key) reason="pass (just generated, assumed good)" header.d=tum.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tum.de; h= content-transfer-encoding:content-type:content-type:subject :subject:message-id:date:date:from:from:references:in-reply-to :received:mime-version:received:received:received; s=postout; t= 1476533530; bh=FshgeyRAR+ZVmW4bwcec3YfeGmg1MFCbEhmRGV/Kv18=; b=n Yi5VARCAZ2gmExc2uLgpxJI4+dLsLoarQgMdsw07VKo9yM2Orczcqeabz4mSVc8C 5KOJbhzv9Kn5xFNhEI37hpVe+8b3ShzFTfshDLy2fTfUIOjdlRNxUuc8efpkNI0h gpE8/q2LMQBC9J/9eskujZwWJ7rk1vSrKCPjzyiHZ0MCsy8k1w2kl5ckaR6MiXtQ wZ+MoRJv0Dd5kzf/znhx8+BI2om3lwrwzD8dUXh76lbVK4/gtgFIfPECN+yfXoH6 AN575NDXN1z6b6oXp+qbRF/AjtDvfcL5fBPP1EZhVwlYzakbm498N/PByCunPq1T m5JJ/3qwqgYn5v6ffwrKw== X-Virus-Scanned: by amavisd-new at lrz.de in lxmhs52.srv.lrz.de X-Spam-Score: -2.792 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_MED, RCVD_IN_SORBS_SPAM autolearn=ham version=3.3.1 Received: from postout2.mail.lrz.de ([127.0.0.1]) by lxmhs52.srv.lrz.de (lxmhs52.srv.lrz.de [127.0.0.1]) (amavisd-new, port 20024) with LMTP id TrmVSC5GRQCx for ; Sat, 15 Oct 2016 14:12:10 +0200 (CEST) Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by postout2.mail.lrz.de (Postfix) with ESMTPSA id 3sx3HZ5bvjzyV1 for ; Sat, 15 Oct 2016 14:12:10 +0200 (CEST) Received: by mail-wm0-f51.google.com with SMTP id d128so27034827wmf.1 for ; Sat, 15 Oct 2016 05:12:10 -0700 (PDT) X-Gm-Message-State: AA6/9Rlt1gma39xLYxoaZVViyma37Ps/tGqiH5dgY2whLF9TsrAWjEbI4mdXDfPMBW470M02FDpqY10+gqBgSw== X-Received: by 10.28.131.72 with SMTP id f69mr1697674wmd.33.1476533530397; Sat, 15 Oct 2016 05:12:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.1.17 with HTTP; Sat, 15 Oct 2016 05:12:09 -0700 (PDT) In-Reply-To: <1574488.v0vhHDvJj4@strawberry> References: <201609240636.01968.luke@dashjr.org> <2024168.qgaqMetGW1@kiwi> <1574488.v0vhHDvJj4@strawberry> From: Marco Falke Date: Sat, 15 Oct 2016 14:12:09 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Tom Zander , Bitcoin Protocol Discussion Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sat, 15 Oct 2016 12:13:11 +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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Oct 2016 12:12:13 -0000 On Sat, Oct 15, 2016 at 1:00 PM, Tom Zander via bitcoin-dev wrote: > My suggestion (sorry for not explaining it better) was that for BIPS to b= e 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) > I like you agree with that part, but I see you added two licenses. > Do you have a good reason to add MIT/BSD to that list? Otherwise I think = we > agree. Licenses that only require attribution are generally compatible with each other. I don't think we should pick one and only promote/endorse this one. Let's just leave the decision to the BIP author. > Well, it has this sentence; > >> This BIP is dual-licensed under the Open Publication License and >> BSD 2-clause license. > > Which is a bit odd in light of the initial email from Luke that suggested= we > drop the Open Publication License and we use the CC ones instead in addit= ion > to the public domain one. I am pretty sure this is required to host the current text of BIP 2 in the repo, as currently BIP 1 still applies and still requires for all BIPs either OPL or PD, which is one of the reasons I think we should move forward with BIP 2 or amending BIP 1. > Marco: >> looks good and addressed the feedback which was >> accumulated last year. If there are no objections I'd suggest to move >> forward with BIP 2 in the next couple of days/weeks. > > Thats odd, you just stated you like the public domain (aka CC0) license, = yet > you encourage the BIP2 that states we can no longer use public domain for > BIPs... Did you read it? > It says; > =C2=ABPublic domain is not universally recognised as a legitimate action= , thus > it is inadvisable.=C2=BB [1] BIP 2 does not forbid you to release your work under PD in legislations where this is possible. None of the licenses mentioned in BIP 2 is exclusive, so you can choose as many options as you like. One of the goals of BIP 2 is to no longer allow PD as the only copyright option. > > Also; > This list has not seen a lot of traffic, if you want to make sure people = keep > using the BIP process, I think you need to reach out to the rest of the > community and make sure this has been heard and discussed. > Moving forward the way it is now will likely deminish the importance of t= he > BIP process. > > I strongly suggest people make very clear any and all changes that are > proposed and defend each of them with reasons why you want to change thin= gs. > > > 1) if you write as a rationale "In some jurisdictions, public domain is n= ot > recognised as a legitimate legal action" then you can at least name those > jurisdictions and explain how they *do* support things like GPL. Burden o= f > proof is on the man who wants to change things. > It looks fishy when lawyers disagree. See the CC wikipedia page; > "public domain: cc0 Freeing content globally without restrictions" Luke is the BIP champion of BIP 2, so please cc him if you have suggestions on how to improve the process of gathering community consensus. Marco