Closed DJMcNab closed 1 week ago
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I consider my past edit (on Readme.md) below the "Threshold of originality" (i.e. Public Domain), therefore:
I license past contributions under the CC0 license, which allows using my past contributions under both MIT aswell Apache-2.0.
I license future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
With MIT-License I mean any of the Version of "Expat License" or "X11 License" or the MIT-License on Github.
@JoKalliauer thanks for responding. Unfortunately, I'm not certain that the CC0 is compatible with the Apache 2.0; in particular, it has limitations around patent grants, which the Apache 2.0 license requires. It might be fine, but it makes things more complicated for us. You are of course free to license your past contribution under CC0, and thank you for doing so. However, I would also please ask you respond with the exactly requested text (without any links and outside a quote), which will make things easier for us.
Indeed, we are meaning the expat license here, with SPDX identifier MIT
.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
Same, my only commit (https://github.com/linebender/resvg/commit/8d363ef3ef451150e9bc5ab72e3d7ef4ba896584) is below the threshold of originality as well. In any case:
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
@chubei can you confirm whether @chubei-oppen was your account? If so, please read this issue and respond accordingly.
Hi @DJMcNab thank you for the ping. @chubei-oppen was my account and
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.
Thank you all for taking part in this! We have now completed this relicense, which was implemented in #844. See the Zulip thread for discussion of the people we were unable to reach.
For clarity, these were:
What
As part of the move into Linebender, we are planning on relicensing resvg under the MIT/Apache 2.0 licenses. These match the standard licenses used by Linebender, and it gives maximum compatibility with the rest of the Rust ecosystem.
If you are mentioned in this issue, we need your help to make this happen
To agree to this relicense, please read the details in this issue, then leave a comment with the following message:
This also follows a similar move done by wgpu. See their issue for their motivations, which broadly also apply to this project.
MPL 2.0
For clarity, we are planning to remove the MPL 2.0 license requirement for new contributions, and so will no longer be releasing new code under the MPL. This follows the precedent set by wgpu. This will allow using code released under the standard MIT/Apache 2.0 license in this project.
For existing users, the Apache license is documented as compatible with the MPL, so we expect that this change will only make resvg easier to use. Additionally, this change does not (and cannot) remove the licenses for previous releases and commits, and so you can continue to use release 0.44.0 and earlier under the MPL 2.0.
Contributor checklist
@ahaoboy
@akindle
@AnthonyMikh
@antmelnyk
@benoit-pierre
- reached by email by @DJMcNab@CGMossa
@chubei-oppen
@conorgolden1
@CosmicHorrorDev
@dabreegster
@dhardy
@e00E
@enkore
@EpicEricEE
@ferdnyc
@flxzt
@flying-sheep
@FylmTM
@growler
@harmic
@iamralpht
@JaFenix
@jc86035
@JoKalliauer
@jpap
@jrmuizel
@kneitinger
@legoktm
@lu-zero
@mattfbacon
@mike-marcacci
@missdeer
@mmoult
@niklasf
@nnabeyang
@notjosh
@Nukesor
@nyurik
@ocohen
@real-or-random
@reknih
@selaux
@Shnatsel
@shuding
@ssssota
@Stoeoef
@therealbnut
@Tibbel
@upsuper
@valpackett
@velyan
@wez
@yisibl
@Zodey-hub
We also need:
Rémi Lauzier
- https://github.com/linebender/resvg/commit/8a838f776aa0f1642a61d8becd802efffeb55b19. Reached through email by @DJMcNabIf you are aware of any contributors not listed in this checklist, please let us know.