Skip to content

Choosing a license and handling open design contributions #15

Closed

Description

@johnsBeharry

Wanted to start the discussion around how we handle the licensing to the guide, and other community initiatives.
We definitely need some legal peoples to also chime in.

Current State: No License

When you make a creative work (which includes code), the work is under exclusive copyright by default

Although a code host such as GitHub may allow you to view and fork the code, this does not imply that you are permitted to use, modify, or share the software for any purpose.

Project Content / Software License

  • How do we handle derivatives, do we use a copyleft or more permissive software license?
  • What happens if the project gets copied rebranded, attributions removed, and relicensed?
  • What happens if some YouTuber decides to create a course out of the content and charge for it?

Contributor License Agreement

  • What happens if someone contributes copyrighted material and it gets merged?
  • What protections are given to other contributors?
  • What happens if an anon on a Design Review Call Design Review call #1 #14 contributes a sketch or idea. Do they need to sign a CLA?

Compliance Tools

CLA Assistant is a tool that is used to add a status check on a PR which prompted the contributor to sign the agreement so checks can pass and the contribution can be merged. It only needs to be done on the first contribution, and will apply to all others unless the agreement is updated. If the agreement does change, CLA Assistant will trigger the agreement to be resigned by all contributors.

EDIT: We don't need a CLA. Read why

REF

Activity

  1. Bosch-0 commented on Sep 10, 2020

    @Bosch-0
    Contributor

    Core has this doc for icon licensing - https://github.com/bitcoin/bitcoin/blob/master/contrib/debian/copyright

    May be useful to see how they do it.

  2. moneyball commented on Sep 10, 2020

    @moneyball
    Contributor

    Rust-lightning just adopted a dual-license approach which I'd recommend for this community. MIT provides permissiveness and Apache provides language around patents. https://github.com/rust-bitcoin/rust-lightning/blob/master/LICENSE.md

  3. added
    governanceHow we organize ourselves as a community
    on Sep 11, 2020
  4. GBKS commented on Sep 29, 2020

    @GBKS
    Contributor

    After doing some studying, here is what I found:

    The MIT license does not protect from patent litigation. That was apparently not a big problem when it was created, and the Apache 2.0 license addresses this.

    For images, as Alexa suggested, it would be good to also offer a Creative Commons license as that is more applicable to creative work. Figma community files are licensed under Creative Commons Attribution 4.0 International, while Mastering Bitcoin by Andreas Antonopoulos is licensed under Creative Commons Attribution-ShareAlike 4.0 International. The difference is that any work that builds on Mastering Bitcoin has to use the same license as the original. Remixes of Figma files can be distributed under other licenses also (same as MIT and Apache 2.0 licenses). Any thoughts on this?

    I spliced together some text from a few sources to come up with a suggestion. References:

    This project is free software. There is no warranty; not even for
    merchantability or fitness for a particular purpose.
    
    Some files retain their own copyright notice, however, for full authorship
    information, see version control history.
    
    Except as otherwise noted in individual files, or LICENSE files in source code 
    directories, all files in this repository are licensed under the [Apache License, Version 2.0](LICENSE-APACHE) 
    or the [MIT license](LICENSE-MIT], at your option.
    
    In addition, you may -- at your option -- use, copy, modify and redistribute all
    images included in this distribution under the directory named `assets`
    according to the terms and conditions of the [Creative Commons Attribution 4.0
    International License](LICENSE-CC-BY).
    
    You may not use, copy, modify, merge, publish, distribute, sublicense, and/or
    sell copies of this software or any files in this repository except in
    accordance with one, both, or all three of these licenses.
    

    Once we have setup a license file, we can then install the CLA assistant Johns linked to for getting all contributions/contributors automatically on the right licensing model.

    That's what I gathered from reading up on this today. I'm sure I missed things, so please let me know what your take is. It's a balance of being permissive so others can contribute and improve things, but also being a bit defensive so nobody can easily abuse or profit from the effort of the community.

    I'll also look into best practices for attributing sources and references on rendered content pages but I think that's a separate task.

  5. moneyball commented on Sep 29, 2020

    @moneyball
    Contributor

    Thank you for researching this! I lean toward as permissive as possible so ShareAlike doesn't sound consistent with community goals.

  6. danielnordh commented on Oct 1, 2020

    @danielnordh
    Contributor

    Thanks Christoph!
    Why offer a choice of MIT or Apache, wouldn't it be simpler to just stick with Apache?
    Agree with Steve that ShareAlike seems unnecessary.

  7. moneyball commented on Oct 1, 2020

    @moneyball
    Contributor
  8. GBKS commented on Oct 1, 2020

    @GBKS
    Contributor

    @moneyball rust-lightning, which you referenced further up, uses a dual-license approach.

    We're essentially saying that when somebody uses this content and publishes it elsewhere, that they can choose one of those licenses for that new publication. So if they are worried about patents, they can use Apache. Or if they come from a design background and are more familiar with creative commons, they can choose that one.

    None of those licenses include anything about warranty or liability (see here), that's why I included that first sentence (also copied from a reference). Otherwise, I am not sure what type of problems are likely to come up. Are you aware of any incidents or discussions on what can go wrong with different licenses?

  9. moneyball commented on Oct 1, 2020

    @moneyball
    Contributor
  10. GBKS commented on Oct 2, 2020

    @GBKS
    Contributor

    That's my understanding, too. Contributors state that their work is good to be published under all licenses as described. Users can choose under which license they want to use the code/content for their own purposes.

  11. added a commit that references this issue on Oct 7, 2020
  12. GBKS commented on Oct 7, 2020

    @GBKS
    Contributor

    I created a PR for this license update here. Please take a look.

  13. johnsBeharry commented on Dec 9, 2020

    @johnsBeharry
    ContributorAuthor

    Closing this off as all aspects have been addressed. We don't need a CLA or use a compliance tool like CLA Assistant either since it's a fully open source community -- read more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    governanceHow we organize ourselves as a community

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions