Consider relicensing under MIT/Apache-2.0

[Detegr]

Some time ago, there were requests that MIT or Apache-2.0 licensed Rust projects would be relicensed under MIT/Apache-2.0 dual license, see here.

Please consider if this would be acceptable for this project as well.

[sharkdp]

To be honest, I haven't fully understood dual licensing.

If I understand correctly, it means that users of the software can choose between the two licenses.

MIT is more permissive than Apache-2.0 (due to the absence of patent clauses), so will the software still be protected from patent litigations if it is dual licensed? If not, what is the advantage of dual-licensing with Apache-2.0?

[Detegr]

I am no means an expert when it comes to licenses and legal issues, but yes, as you stated it means that the users of the software can choose between the two licenses. If fd would be shipped within a project, the project could choose between MIT and Apache 2. This in turn gives more freedom to the user because it can be easier for the user to choose the more strict license (for example to omit copying the copyright statements that MIT requires).

Of course this change would require that every contributor of this project agrees that their contributions can be relicensed and that could be cumbersome.

[sharkdp]

Thank you for the clarification. In this case, I'm open to relicensing fd under MIT/Apache-2.0. Would you be willing to organize the necessary steps (have all contributors sign, add the new license, modify Cargo file, etc.)?

[mmstick]

I'll also add that I support the decision.

[Detegr]

Would you be willing to organize the necessary steps (have all contributors sign, add the new license, modify Cargo file, etc.)?

Absolutely.

Contributor checkoff

If you agree to relicense, please leave the following comment to this issue:

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

• @sharkdp
• @mmstick
• @Detegr
• @reima
• @iology
• @unsignedint
• @gsquire
• @jcpetkovich
• @olalonde
• @abaez
• @deg4uss3r
• @ImbaKnugel
• @Exitium
• @wezm
• @michaelmior
• @sebasv
• @pickfire
• @matematikaadit
• @goyox86
• @cassava
• @mehandes

[Detegr]

I think it's best to be explicit (even though I did check some checkboxes already), so here's mine:

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[wezm]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[jakwings]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Project: https://github.com/sharkdp/fd
Signer: J.W <jakwings@gmail.com>

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
-----BEGIN PGP SIGNATURE-----

iQJHBAEBCAAxFiEE/JKIN9OlzOWqfbOUZiMu3Yhz6ZgFAlnjE8QTHGpha3dpbmdz
QGdtYWlsLmNvbQAKCRBmIy7diHPpmOYVD/9sL/XK5RIqX3Nt8Cfy3CN+iTTYNXVa
vHJxjGpwSFhb0WhF1uamSA6geTpcJW9vjFK4tuQn1ZNEunJDQr/ZjAZWRxAw9CDa
Y2tYjvnOyfxREY+XyINM+SMmU0GihMFqJYzsFDdJLZTgcQcwTt5PO1tlUI1KgHMW
ogrE2B6skiSnYpWoAaheC41mdvjz41eR1JMLLnrJQ3Ty8wG2SywDdAPuLRZ5XHSn
K+s+dZEo5eW6kZQiCaVmI44VCxItJfzqfzDsAZ3sphNfSBbT4zzymXfG7NsiWKvm
5YK25u8ItA76Ev6tK46lPx1083yjjQ0Fo7rdT5WoNjr3dc/LmZo4VCot/EUzdqUe
zn3+SK1LO+JQOGKy1ioz3hHdbtnUsNruhW8j0JGT+sPMS65pa54Mj57VtIlJm0ws
Euw30lCYZWuqYheSbb1Dw5GlmJPrMNtb2EgVqyi0+xvqcOEPTJPYV9JJgmEapUJs
efWotsop5dUj2T4i8BkSxS1ZvLcx57XiR8Ac20E3QdiA8FDND0vffxyrwNxpjjPE
Sb6x/yFZGpb9GXMrf+hW9/kJBUYCR4dR6dBYj8nFpXfKyl0xpsZe6VQYQlzrwuUq
6i6gyGVgAlpVYXdmL0TWWvpKiqRSZWz24rQBFeXE/xh/KqcrzDv2at14ZuBrX8qv
QVixZJzDADAIPA==
=qqFf
-----END PGP SIGNATURE-----

[sharkdp]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[reima]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[michaelmior]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[ghost]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[abaez]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[gsquire]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[unsignedint]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[olalonde]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

68a85c7 🤣

[Knugel]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[sharkdp]

@jcpetkovich @deg4uss3r @sebasv @pickfire Could you please (also) sign this (if you agree)?

[jcpetkovich]

Sorry for the delay. I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

…

On Oct 19, 2017 2:35 PM, "David Peter" ***@***.***> wrote: @jcpetkovich <https://github.com/jcpetkovich> @deg4uss3r <https://github.com/deg4uss3r> @sebasv <https://github.com/sebasv> @pickfire <https://github.com/pickfire> Could you please (also) sign this (if you agree)? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#105 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJuGT79hC4LhlDcH5SPXTb9nzo5flUbks5st5ZZgaJpZM4P3_xr> .

[sebasv]

My apologies for the delayed response as well.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[matematikaadit]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[pickfire]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[deg4uss3r]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[sharkdp]

@Detegr All done 😄

[Detegr]

Great, I'll prepare a PR. We're missing @goyox86 though (and a couple of others that are mainly README fixes, so I'm not sure if those are important). I'll prepare the PR anyway so we can merge it quickly before other contributors join the project 😄.

[goyox86]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[Detegr]

PR is ready, agreement from @cassava and @mehandes (README changes for both of them) are missing.

@sharkdp I would suggest you won't merge any PR's before merging #143 unless the authors are aware of the ongoing relicensing effort.

[cassava]

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

[sskras]

ping @mehandes (for the sake of completeness:)