Skip to content
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

Merged
merged 1 commit into from
Sep 13, 2022

Conversation

lunabunn
Copy link
Contributor

@lunabunn lunabunn commented Jun 1, 2022

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 under MIT. In addition to not being as compatible as it could be with the rest of the ecosystem, most of which uses the MIT 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 around MIT as a licensing option (instead of using just Apache-2.0) for GPLv2 compat.

If this project were to be dual-licensed under Apache-2.0 and MIT, contributors would be providing the Apache-2.0 patent grant, even though the project will still remain usable with the MIT license. It will also be more compatible with the rest of the ecosystem. Adding a third Zlib 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:

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.

If you have any concerns, please leave those in this issue thread as well so that they can be discussed.

@maroider
Copy link
Contributor

maroider commented Jun 1, 2022

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.

@Riey
Copy link
Contributor

Riey commented Jun 2, 2022

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
@bschwind
Copy link
Contributor

bschwind commented Jun 2, 2022

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.

@weswigham
Copy link
Collaborator

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.

@deeprobin
Copy link
Contributor

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.

@BastiDood
Copy link
Contributor

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!

@tronical
Copy link
Contributor

tronical commented Jun 2, 2022

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
@avafloww
Copy link
Contributor

avafloww commented Jun 3, 2022

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.

@twitchyliquid64
Copy link
Contributor

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.

🥳

@robmcl4
Copy link
Contributor

robmcl4 commented Jun 6, 2022

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.

@ryan-scott-dev
Copy link
Contributor

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.

@MarimeGui
Copy link
Contributor

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
@Brooooooklyn
Copy link
Contributor

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.

@mooman219 mooman219 mentioned this pull request Jul 13, 2022
@cedric-h
Copy link
Contributor

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.

@avl
Copy link
Contributor

avl commented Aug 15, 2022

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.

@avl
Copy link
Contributor

avl commented Aug 15, 2022

(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!)

@deprilula28
Copy link
Contributor

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
@grovesNL
Copy link
Contributor

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.

@mooman219 mooman219 merged commit 828b4f4 into mooman219:master Sep 13, 2022
@mooman219
Copy link
Owner

Thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.