Relicense resvg under dual MIT/Apache-2.0 #838

DJMcNab · 2024-10-29T17:14:06Z

Note

resvg has recently moved into the Linebender organisation. See #834 for details.

We would also like to thank @RazrFalcon for all their previous work on resvg, and wish them luck in their future endeavours.

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:

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

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

We also need:

Rémi Lauzier - 8a838f7. Reached through email by @DJMcNab

If you are aware of any contributors not listed in this checklist, please let us know.

The text was updated successfully, but these errors were encountered:

RazrFalcon · 2024-10-29T17:51:12Z

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

laurmaedje · 2024-10-29T18:19:05Z

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

LaurenzV · 2024-10-29T18:34:03Z

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

DJMcNab · 2024-10-30T08:08:06Z

You are getting this message because you previously contributed to resvg - an svg rendering library in Rust.
We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

DJMcNab · 2024-10-30T08:08:20Z

You are getting this message because you previously contributed to resvg - an svg rendering library in Rust.
We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

CosmicHorrorDev · 2024-10-30T08:10:56Z

Thanks for the ping!

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

therealbnut · 2024-10-30T08:11:10Z

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

growler · 2024-10-30T08:11:27Z

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

Zodey-hub · 2024-10-30T08:14:36Z

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

ssssota · 2024-10-30T08:18:01Z

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

upsuper · 2024-10-30T08:25:13Z

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

FylmTM · 2024-10-30T08:30:47Z

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

kneitinger · 2024-10-30T08:40:35Z

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

flying-sheep · 2024-10-30T08:51:20Z

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

CGMossa · 2024-10-30T08:52:18Z

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

dabreegster · 2024-10-30T08:57:24Z

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

Shnatsel · 2024-10-30T08:57:54Z

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

e00E · 2024-10-30T09:02:52Z

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

missdeer · 2024-10-30T09:10:18Z

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

EpicEricEE · 2024-10-30T09:12:01Z

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

ahaoboy · 2024-10-30T09:15:42Z

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

harmic · 2024-10-30T09:27:44Z

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

notjosh · 2024-10-30T09:44:52Z

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

glad to see resvg live on <3 thank you @RazrFalcon for all your work on this

flxzt · 2024-10-30T10:06:42Z

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

shuding · 2024-10-30T10:17:03Z

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

reknih · 2024-10-30T10:17:52Z

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

nnabeyang · 2024-10-30T10:56:37Z

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

Nukesor · 2024-10-30T11:47:18Z

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

mattfbacon · 2024-10-30T12:03:36Z

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

selaux · 2024-10-30T12:12:54Z

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

nyurik · 2024-10-30T15:02:29Z

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

yisibl · 2024-10-30T15:07:07Z

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

DJMcNab · 2024-10-30T15:10:52Z

@ferdnyc we would greatly prefer you to use the wording, so that we can follow the precedent of wording set by wgpu.
It's a shame that the Android app doesn't let you copy it easily within there.

The full text is as in most of the other comments:

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

DJMcNab · 2024-10-30T15:14:25Z

@real-or-random thanks for the input. I think just using the wording that wgpu used is easier for us, and minimises the risk of getting things wrong.

Fwiw, no-one had an issue with the wording for either Bevy or wgpu, so I don't think it's likely to be an issue.

conorgolden1 · 2024-10-30T16:27:24Z

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

AnthonyMikh · 2024-10-30T16:27:57Z

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

it is not like I feel that my single typo fix is that significant in grand scheme of things but oh well

akindle · 2024-10-30T16:29:31Z

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

niklasf · 2024-10-30T17:21:12Z

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

dhardy · 2024-10-30T17:30:44Z

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

Stoeoef · 2024-10-30T17:35:30Z

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

valpackett · 2024-10-30T18:23:25Z

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

antmelnyk · 2024-10-30T18:49:07Z

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

gentoo90 · 2024-10-30T21:03:37Z

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

jpap · 2024-10-30T21:45:37Z

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

mike-marcacci · 2024-10-31T01:40:01Z

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

wez · 2024-10-31T04:01:51Z

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

JoKalliauer · 2024-10-31T14:03:30Z

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.

DJMcNab · 2024-10-31T14:20:58Z

@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.

JoKalliauer · 2024-10-31T16:36:07Z

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

mmoult · 2024-10-31T23:30:56Z

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

legoktm · 2024-11-03T02:40:47Z

Same, my only commit (8d363ef) 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.

DJMcNab · 2024-11-06T10:13:26Z

@chubei can you confirm whether @chubei-oppen was your account? If so, please read this issue and respond accordingly.

chubei · 2024-11-06T10:29:15Z

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.

enkore · 2024-11-06T12:09:14Z

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

sorairolake · 2024-11-08T10:49:47Z

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

DJMcNab · 2024-11-11T11:17:43Z

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:

@jc86035, who contributed Grammatical fixes for README.md #130. Those small grammar fixes are not copyrightable
@Tibbel, who contributed include extern "C" for C++ #163. That code is extremely standard boilerplate which is not copyrightable.
@velyan, who contributed Skia build for mac os #158; the Skia backend has been removed, alongside that README file.
@ferdnyc, who did agree to the relicense but used their own wording. We've decided that their wording is sufficiently clear in context for us to accept.

DJMcNab mentioned this issue Nov 8, 2024

Set rust-version for workspace members #842

Merged

DJMcNab mentioned this issue Nov 8, 2024

Dual MIT/Apache 2.0 License fschutt/fastblur#16

Closed

xStrom mentioned this issue Nov 8, 2024

Relicense under Apache-2.0 OR MIT. #844

Merged

DJMcNab closed this as completed Nov 11, 2024

Relicense resvg under dual MIT/Apache-2.0 #838

Relicense resvg under dual MIT/Apache-2.0 #838

Comments

DJMcNab commented Oct 29, 2024 • edited Loading

What

MPL 2.0

Contributor checklist

RazrFalcon commented Oct 29, 2024

laurmaedje commented Oct 29, 2024

LaurenzV commented Oct 29, 2024

DJMcNab commented Oct 30, 2024

DJMcNab commented Oct 30, 2024

CosmicHorrorDev commented Oct 30, 2024

therealbnut commented Oct 30, 2024

growler commented Oct 30, 2024

Zodey-hub commented Oct 30, 2024

ssssota commented Oct 30, 2024

upsuper commented Oct 30, 2024

FylmTM commented Oct 30, 2024

kneitinger commented Oct 30, 2024

flying-sheep commented Oct 30, 2024

CGMossa commented Oct 30, 2024

dabreegster commented Oct 30, 2024

Shnatsel commented Oct 30, 2024

e00E commented Oct 30, 2024

missdeer commented Oct 30, 2024

EpicEricEE commented Oct 30, 2024

ahaoboy commented Oct 30, 2024

harmic commented Oct 30, 2024

notjosh commented Oct 30, 2024

flxzt commented Oct 30, 2024

shuding commented Oct 30, 2024

reknih commented Oct 30, 2024

nnabeyang commented Oct 30, 2024

Nukesor commented Oct 30, 2024

mattfbacon commented Oct 30, 2024

selaux commented Oct 30, 2024

nyurik commented Oct 30, 2024

yisibl commented Oct 30, 2024

DJMcNab commented Oct 30, 2024

DJMcNab commented Oct 30, 2024 • edited Loading

conorgolden1 commented Oct 30, 2024

AnthonyMikh commented Oct 30, 2024

akindle commented Oct 30, 2024

niklasf commented Oct 30, 2024

dhardy commented Oct 30, 2024

Stoeoef commented Oct 30, 2024

valpackett commented Oct 30, 2024

antmelnyk commented Oct 30, 2024

gentoo90 commented Oct 30, 2024

jpap commented Oct 30, 2024

mike-marcacci commented Oct 31, 2024

wez commented Oct 31, 2024

JoKalliauer commented Oct 31, 2024

DJMcNab commented Oct 31, 2024

JoKalliauer commented Oct 31, 2024

mmoult commented Oct 31, 2024

legoktm commented Nov 3, 2024

DJMcNab commented Nov 6, 2024

chubei commented Nov 6, 2024

enkore commented Nov 6, 2024

sorairolake commented Nov 8, 2024

DJMcNab commented Nov 11, 2024

DJMcNab commented Oct 29, 2024 •

edited

Loading

DJMcNab commented Oct 30, 2024 •

edited

Loading