public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom <tomz@freedommail•ch>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 2 revival and rework
Date: Sat, 24 Sep 2016 11:41:57 +0200	[thread overview]
Message-ID: <2024168.qgaqMetGW1@kiwi> (raw)
In-Reply-To: <201609240636.01968.luke@dashjr.org>

On Saturday, 24 September 2016 06:36:00 CEST Luke Dashjr via bitcoin-dev 
wrote:
> * OPL will no longer be an acceptable license. Many in the community feel
> that prohibiting publication is unacceptable for BIPs, and I haven't
> heard any arguments in favour of allowing it.

My suggestion would be that we replace OPL as an allowed license with one 
or two Creative Commons licenses. Following the suggestion from the OPL 
creators themselves.
According to Wikipedia;

> Open Publication License was created by the Open Content Project in 1999 
> as public copyright license for documents. The license was superseded
> in 2003/2007 by the Creative commons licenses.

I'd suggest saying that "Share alike" is required and "Attribution" is 
optional.

Executive summary; give the user the choice (next to public domain) between 
CCO and BY-SA
see;
https://en.wikipedia.org/wiki/
Creative_Commons_license#Seven_regularly_used_licenses


  reply	other threads:[~2016-09-24  9:42 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 [this message]
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
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=2024168.qgaqMetGW1@kiwi \
    --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