-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relicense to MIT OR Apache-2.0 OR Zlib
#113
Conversation
I license past and future contributions under the triple |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
1 similar comment
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
I license past and future contributions under the triple |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. Thanks for the heads up, by the way! |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
1 similar comment
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
I license past and future contributions under the triple 🥳 |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
I license past and future contributions under the triple |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
1 similar comment
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to chose any one at their option. |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option. |
(I'm sorry for being so late to answer. I think I was notified when I was pinged when this PR was opened, but I didn't read enough to realize I was being asked to take action. Sorry about that! Good initiative!) |
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option. |
1 similar comment
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option. |
Thanks everyone! |
As per the discussion in #112, I am initiating the process to relicense this project to the
MIT OR Apache-2.0 OR Zlib
triple license.Rationale for Licensing
Currently
fontdue
is licensed solely underMIT
. In addition to not being as compatible as it could be with the rest of the ecosystem, most of which uses theMIT OR Apache-2.0
dual license,MIT
is also problematic in that in lacks a patent protection clause and an explicit contribution clause. In fact, Rust itself is only keeping aroundMIT
as a licensing option (instead of using justApache-2.0
) for GPLv2 compat.If this project were to be dual-licensed under
Apache-2.0
andMIT
, contributors would be providing theApache-2.0
patent grant, even though the project will still remain usable with theMIT
license. It will also be more compatible with the rest of the ecosystem. Adding a thirdZlib
licensing option then grants the additional flexibility of not needing to include attribution or license information in product distributions that do not include source code.This permissive, flexible, and compatible licensing would be ideal for a crate such as
fontdue
that is most likely to be used indirectly as dependencies of other crates in its users' dependency graphs.Contributor checkoff
Being a change in license, this requires all contributors who have made copyrightable changes to the
fontdue
repository to agree.For simplicity (and because IANAL), given below is a list of all contributors to the fontdue project. If you agree to relicensing, please comment verbatim:
If you have any concerns, please leave those in this issue thread as well so that they can be discussed.