From: Marco Falke <marco.falke@tum.de>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 revival and rework
Date: Sat, 15 Oct 2016 12:25:43 +0200 [thread overview]
Message-ID: <CAK51vgAeBBd14enaDdhdL+sC2QmYJrwPrFvkRCoUkbvbOAFViA@mail.gmail.com> (raw)
In-Reply-To: <2024168.qgaqMetGW1@kiwi>
On Sat, Sep 24, 2016 at 11:41 AM, Tom via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> I'd suggest saying that "Share alike" is required and "Attribution" is
> optional.
Please note there is no CC license that requires SA and at the same
time has BY as an option.
Generally, I think CC0 is best suited as license for BIPs. If authors
are scared that they won't get proper attribution, they can choose
MIT/BSD or CC-BY. Other than that I don't think that more restrictive
licenses are suitable for BIPs. The BIP repo seems like the wrong
place to promote Open Access (e.g. by choosing a CC-BY-SA license).
BIP 2 allows such licenses, but does not recommend them, which is
fine.
I think that BIP 2 in its current form (
https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki
@6e47447b ) 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.
Marco
next prev parent reply other threads:[~2016-10-15 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 6:36 [bitcoin-dev] BIP 2 revival and rework Luke Dashjr
2016-09-24 9:41 ` Tom
2016-10-15 10:25 ` Marco Falke [this message]
[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
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=CAK51vgAeBBd14enaDdhdL+sC2QmYJrwPrFvkRCoUkbvbOAFViA@mail.gmail.com \
--to=marco.falke@tum.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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