From: Tom <tomz@freedommail•ch>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Proposed BIP-1 change removing OPL licensing option.
Date: Tue, 27 Sep 2016 11:51:40 +0200 [thread overview]
Message-ID: <2882300.70fluXe1Lh@garp> (raw)
In-Reply-To: <20160926184136.GA15752@fedora-21-dvm>
On Monday 26 Sep 2016 14:41:36 Peter Todd via bitcoin-dev wrote:
> Note how the OPL is significantly more restrictive than the Bitcoin Core
> license; not good if we can't ship documentation with the code.
Documentation and code can have different licenses, the sole existence of
various documentation licenses attests to that point.
Shipping your docs under a separate licence has never been a problem before,
so you don't have to worry that you can't ship documentation with code.
That said, I wrote my suggestion in reply to Luke's BIP2 revival which is a
more formal suggestion of a solution. Maybe you can ACK that one instead?
Last, in preparation of acceptance of BIP2 I changed the licence of my BIP to
be dual-licensed. Now its also available under a Creative Commons license.
Have a nice day!
next prev parent reply other threads:[~2016-09-27 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 0:21 Gregory Maxwell
2016-09-26 18:41 ` Peter Todd
2016-09-27 9:51 ` Tom [this message]
2016-09-27 19:17 ` Peter Todd
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=2882300.70fluXe1Lh@garp \
--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