Skip to content
This repository was archived by the owner on Sep 14, 2023. It is now read-only.
This repository was archived by the owner on Sep 14, 2023. It is now read-only.

Use a working license instead of UNLICENSE #1

Closed
@Valloric

Description

@Valloric

[I posted this in your Reddit thread, but it should be an actual issue.]

Please don't use UNLICENSE for your license. It doesn't actually work. All uses of UNLICENSE can be replaced with uses of the Apache 2 license (which actually works); you get the same "do whatever you want with it" support without causing your users pain because your license makes no legal sense.

Apache 2 really is what you want; unlike the MIT license, it covers the following as well:

  • Any patches you receive are also licensed under Apache 2. MIT says nothing on this and thus leaves any project using it in a weird state after merging in external contributions.
  • It gives a patent license as well.
  • Other minor useful tidbits.

I've made the mistake of using UNLICENSE myself before; learn from my experience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions