Skip to content

Proposal: Dual-licensing under Apache 2.0 or MIT #53

Closed

Description

@xtqqczze

The project is currently licensed under the Apache License, Version 2.0.

It might be worth considering a dual-licensing approach under both Apache 2.0 or MIT terms, similar to how the Rust Project is licensed.

Adopting dual-licensing could help increase adoption and improve compatibility with projects that prefer the MIT license.

@cmpute Would this be something you’d be open to exploring?

Activity

  1. oech3 commented on Feb 19, 2026

    @oech3
    Contributor

    Why? It is already compat license with MIT.

  2. xtqqczze commented on Feb 19, 2026

    @xtqqczze
    ContributorAuthor

    Apache-2.0 is not compatible with GPL-2.0 or LGPL-2.1. Rust is dual-licensed under MIT OR Apache-2.0, which is GPL-compatible.

  3. oech3 commented on Feb 19, 2026

    @oech3
    Contributor

    needs agreements of all contributors. I think contributors from uutils would say OK, but there are some other contributors.

  4. xtqqczze commented on Feb 19, 2026

    @xtqqczze
    ContributorAuthor

    Do you agree to relicense your contributions under MIT OR Apache-2.0 (dual license)?

  5. robinhundt commented on Feb 19, 2026

    @robinhundt
    Contributor

    Yes, I agree.

  6. oech3 commented on Jul 25, 2026

    @oech3
    Contributor

    Any progress? 2 people left.

  7. xtqqczze commented on Jul 25, 2026

    @xtqqczze
    ContributorAuthor

    The following command lists all users who reacted to #53 (comment) with 👍:

    gh api repos/uutils/num-prime/issues/comments/3928741263/reactions \
      --jq '.[] | select(.content == "+1") | .user.login'
  8. sylvestre commented on Sep 22, 2026

    @sylvestre
    SponsorContributor
  9. cakebaker commented on Sep 22, 2026

    @cakebaker
    Contributor

    It's fine for me.

  10. changed the title [-]Proposal: Dual-licensing under Apache 2.0 and MIT[/-] [+]Proposal: Dual-licensing under Apache 2.0 or MIT[/+] on Sep 26, 2026
  11. haroune-dev commented on Sep 27, 2026

    @haroune-dev
    Contributor

    Yes, I'm okay with this.

  12. sylvestre commented on Sep 27, 2026

    @sylvestre
    SponsorContributor

    @chadbrewbaker @krakow10 you are the two last :)

  13. krakow10 commented on Sep 27, 2026

    @krakow10
    Contributor

    I am onboard with this change. You may relicense my README.md typo fix as dual-licensed Apache 2.0 | MIT.

  14. xtqqczze commented on Oct 2, 2026

    @xtqqczze
    ContributorAuthor

    @sylvestre I think we have enough agreement to move forward with this.

    Given that @chadbrewbaker’s contribution appears to be relatively trivial from a copyright perspective:

    I think we can proceed with the dual-licensing change.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions