Remove OPL licensing option. #446

pull gmaxwell wants to merge 1 commits into bitcoin:master from gmaxwell:opl-bye-bye changing 1 files +1 −1
  1. gmaxwell commented at 12:08 AM on September 24, 2016: contributor

    The OPL enables the author to both prohibit modifications without their explicit approval, as well as enabling them to prohibit distribution in print form.

    This is antithetical to the goals of having transparent, public, collaborative, community standards for interoperability and I don't believe it was anyone's intention here.

  2. Remove OPL licensing option.
    The OPL enables the author to both prohibit modifications
     without their explicit approval, as well as enabling them
     to prohibit distribution in print form.
    
    This is antithetical to the goals of having transparent,
     public, collaborative, community standards for interoperability
     and I don't believe it was anyone's intention here.
    3548ea23b6
  3. luke-jr added the label Proposed BIP modification on Sep 24, 2016
  4. luke-jr commented at 12:11 AM on September 24, 2016: member

    I think a change like this really needs a new BIP.

  5. btcdrak commented at 12:33 AM on September 24, 2016: contributor

    ACK 3548ea23b624d0bd62f36b5bcd9cd08effca367c

  6. gmaxwell commented at 1:56 AM on September 24, 2016: contributor

    @luke-jr As of a week ago it would have pretty much been a total no-op.

    Tricky here, so what we have a BIP-1 saying you can do X but then a BIP-N that says you can't? not exactly the best documentation. I suppose what we'd need to do is create a BIP-N that supersedes BIP1. ... I suppose it's good that BIP1 isn't an unmodifiable OPL document. :P

  7. kanzure commented at 2:37 AM on September 24, 2016: contributor

    ACK 3548ea23b624d0bd62f36b5bcd9cd08effca367c. My contributions to BIP1 should be considered part of the public domain.

    I think there are some jurisdictions where authors cannot place works into the public domain directly. Perhaps some alternative recommendation should be made for those cases. Maybe the Creative Commons people figured out what to do about issues like this.

    By the way, it would seem that we keep running into weird text found in BIP1. We should really encourage more people to read BIP1. I made BIP1 edits within the past year for some basic formatting issues such as fixing how entire new sections which were appended at the end of a line that nobody had noticed for years. This particular error had even been copied into other projects such as EIPs......

    https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-September/013164.html

  8. btcdrak commented at 8:06 AM on September 24, 2016: contributor

    Creative Commons wrote about PD copyright here https://wiki.creativecommons.org/wiki/Public_domain

    I also think we should avoid BIPs turning into a mirror for how legislation works where you need to scour several documents to find out the law. I think BIP1 should be amended, even if it's entirely replaced. BIP1 is clearly different to the other BIPs since it is the document that describes and defined the BIP process. It is already hard enough to get people to actually read BIP1 without them having to read and merge several references.

  9. laanwj commented at 9:57 AM on September 24, 2016: member

    I think this makes sense. This was never the intention, just another result of copy-pasting carelessly from Python. ACK

  10. in bip-0001.mediawiki:None in 3548ea23b6
      66 | @@ -67,7 +67,7 @@ Each BIP should have the following parts:
      67 |  
      68 |  * Abstract -- a short (~200 word) description of the technical issue being addressed.
      69 |  
      70 | -* Copyright/public domain -- Each BIP must either be explicitly labelled as placed in the public domain (see this BIP as an example) or licensed under the Open Publication License.
      71 | +* Copyright/public domain -- Each BIP must either be explicitly labelled as placed in the public domain (see this BIP as an example).
    


    MarcoFalke commented at 10:28 AM on September 24, 2016:

    This sentence no longer makes sense.

    I'd suggest the following:

    * Copyright -- Each BIP must be explicitly labeled as placed in the public domain or licensed under at least one of the following licenses:
    ** BSD-2-Clause: [https://opensource.org/licenses/BSD-2-Clause OSI-approved BSD 2-clause license]
    ** CC0-1.0: [https://creativecommons.org/publicdomain/zero/1.0/ Creative Commons CC0 1.0 Universal]
    ** CC-BY-SA-4.0: [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International]
    

    This would allow us to keep all the BIPs that are currently not placed in the public domain instead of having to delete them.


    laanwj commented at 8:12 AM on September 25, 2016:

    A quick grep shows that the only BIPs with alternative licenses are:

    • bip-0002: dual-licensed under the Open Publication License and BSD 2-clause license
    • bip-0145: dual-licensed under the Open Publication License and BSD 2-clause license

    We should just try to get these re-licensed. I don't see anything under CC-BY-SA or CC0. Or I may have missed something?

    BTW BIP1 itself also needs a copyright heading.


    MarcoFalke commented at 9:40 AM on September 25, 2016:

    @laanwj Currently the copyright suggestions by BIP1 are a complete mess. I think we agree that OPL should be removed and at least BSD 2-clause be added, so we don't have to delete BIPs.

    However, as we are touching this line anyway, we might want to provide an alternative for the public domain rule as well. As pointed out earlier, placing a work into the public domain is not possible (or even prohibited) in some countries. (c.f. http://opensource.stackexchange.com/a/1372) Thus, choosing a license such as CC0, WTFPL, UNLINCENSE or similar is the legally "proper" way of placing a work in the public domain. To the best of my knowledge, CC0 seems to be the preferred way of placing something in the public domain.

    Right now, adding CC0 to the acceptable licenses by BIP1 is a noop, but it would solve the issue in the future where a BIP author just wants to place the BIP into public domain and thus has to dual-license as BSD 2-clause and CC0, because just CC0 is not accepted by BIP1.

    (I understand that my suggestion to add CC-BY-SA may be controversial, and I don't care too much, so we could just leave this for "later")


    luke-jr commented at 1:29 PM on September 25, 2016:

    Would be helpful to put this effort into reviewing and finalising BIP 2...


    laanwj commented at 2:15 PM on September 25, 2016:

    @MarcoFalke I agree. @luke-jr Heh yes, this is typical scope creep. @gmaxwell 's point here is to get rid of a license that is clearly not a good idea for this kind of thing. Enumerating which licenses are a good match for the BIP process is important, but maybe for another time.


    luke-jr commented at 5:31 PM on September 25, 2016:

    @laanwj We did the latter several months ago, but it got held up by arguments over what wiki to use for the (unrelated) BIP Comments. Might as well just finish it...


    MarcoFalke commented at 5:49 PM on September 25, 2016:

    Though, I don't see what advantage there is to create another BIP to supersede BIP1, when it is possible to just amend BIP1. This will save a lot of confusion and time.

  11. MarcoFalke commented at 10:39 AM on September 24, 2016: member

    Concept ACK and I also agree with @btcdrak. BIP1 should always represent the current state of the BIP process/guidelines. I think it makes sense to incrementally improve BIP1 such that it converges to BIP2 over time. Otherwise we may run into the risk of not going anywhere, when it turns out that some people object specific changes of BIP2 and thus block any improvement that BIP2 tries to achieve.

  12. MarcoFalke cross-referenced this on Sep 30, 2016 from issue BIP1: Update copyright requirements by MarcoFalke
  13. super3 commented at 6:52 PM on October 1, 2016: none

    @MarcoFalke Has there been any objections to BIP 2 in its current form? I can't find any.

  14. MarcoFalke commented at 7:06 PM on October 1, 2016: member

    No, I am not aware of any objections, which does not mean that no objections will come up.

  15. luke-jr commented at 4:36 AM on December 15, 2016: member

    BIP 1 has been Replaced by BIP 2, which no longer allows OPL. Considering this fixed.

  16. luke-jr closed this on Dec 15, 2016


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bips. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-14 11:10 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me