You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: Dual-licensing under Apache 2.0 or MIT #53
Activity
oech3 commentedon Feb 19, 2026
Why? It is already compat license with MIT.
xtqqczze commentedon Feb 19, 2026
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.
oech3 commentedon Feb 19, 2026
needs agreements of all contributors. I think contributors from uutils would say OK, but there are some other contributors.
xtqqczze commentedon Feb 19, 2026
Do you agree to relicense your contributions under MIT OR Apache-2.0 (dual license)?
robinhundt commentedon Feb 19, 2026
Yes, I agree.
oech3 commentedon Jul 25, 2026
Any progress? 2 people left.
xtqqczze commentedon Jul 25, 2026
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'sylvestre commentedon Sep 22, 2026
@cakebaker @chadbrewbaker ping ? :)
cakebaker commentedon Sep 22, 2026
It's fine for me.
[-]Proposal: Dual-licensing under Apache 2.0 and MIT[/-][+]Proposal: Dual-licensing under Apache 2.0 or MIT[/+]haroune-dev commentedon Sep 27, 2026
Yes, I'm okay with this.
sylvestre commentedon Sep 27, 2026
@chadbrewbaker @krakow10 you are the two last :)
krakow10 commentedon Sep 27, 2026
I am onboard with this change. You may relicense my README.md typo fix as dual-licensed Apache 2.0 | MIT.
xtqqczze commentedon Oct 2, 2026
@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.