Relicense resvg under dual MIT/Apache-2.0

DJMcNab commented 3 weeks ago

[!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

[x] @RazrFalcon
[x] @LaurenzV
[x] @gentoo90
[x] @laurmaedje
[x] @ahaoboy
[x] @akindle
[x] @AnthonyMikh
[x] @antmelnyk
[x] @benoit-pierre - reached by email by @DJMcNab
[x] @CGMossa
[x] @chubei-oppen
[x] @conorgolden1
[x] @CosmicHorrorDev
[x] @dabreegster
[x] @dhardy
[x] @e00E
[x] @enkore
[x] @EpicEricEE
[ ] @ferdnyc
[x] @flxzt
[x] @flying-sheep
[x] @FylmTM
[x] @growler
[x] @harmic
[x] @iamralpht
[x] @JaFenix
[ ] @jc86035
[x] @JoKalliauer
[x] @jpap
[x] @jrmuizel
[x] @kneitinger
[x] @legoktm
[x] @lu-zero
[x] @mattfbacon
[x] @mike-marcacci
[x] @missdeer
[x] @mmoult
[x] @niklasf
[x] @nnabeyang
[x] @notjosh
[x] @Nukesor
[x] @nyurik
[x] @ocohen
[x] @real-or-random
[x] @reknih
[x] @selaux
[x] @Shnatsel
[x] @shuding
[x] @ssssota
[x] @Stoeoef
[x] @therealbnut
[ ] @Tibbel
[x] @upsuper
[x] @valpackett
[ ] @velyan
[x] @wez
[x] @yisibl
[x] @Zodey-hub

We also need:

[x] Rémi Lauzier - https://github.com/linebender/resvg/commit/8a838f776aa0f1642a61d8becd802efffeb55b19. Reached through email by @DJMcNab

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

RazrFalcon commented 3 weeks ago

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

laurmaedje commented 3 weeks ago

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

LaurenzV commented 3 weeks ago

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

DJMcNab commented 3 weeks ago

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!

@ahaoboy
@akindle
@AnthonyMikh
@antmelnyk
@benoit-pierre
@CGMossa
@chubei-oppen
@conorgolden1
@CosmicHorrorDev
@dabreegster
@dhardy
@e00E
@enkore
@EpicEricEE
@ferdnyc
@flxzt
@flying-sheep
@FylmTM
@growler
@harmic
@iamralpht
@JaFenix
@jc86035
@JoKalliauer
@jpap

DJMcNab commented 3 weeks ago

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!

@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

CosmicHorrorDev commented 3 weeks ago

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 commented 3 weeks ago

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

growler commented 3 weeks ago

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

Zodey-hub commented 3 weeks ago

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

ssssota commented 3 weeks ago

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

upsuper commented 3 weeks ago

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

FylmTM commented 3 weeks ago

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

kneitinger commented 3 weeks ago

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

flying-sheep commented 3 weeks ago

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

CGMossa commented 3 weeks ago

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

dabreegster commented 3 weeks ago

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

Shnatsel commented 3 weeks ago

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

e00E commented 3 weeks ago

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

missdeer commented 3 weeks ago

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

EpicEricEE commented 3 weeks ago

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

ahaoboy commented 3 weeks ago

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

harmic commented 3 weeks ago

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

notjosh commented 3 weeks ago

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 commented 3 weeks ago

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

shuding commented 3 weeks ago

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

reknih commented 3 weeks ago

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

nnabeyang commented 3 weeks ago

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

Nukesor commented 3 weeks ago

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

mattfbacon commented 3 weeks ago

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

selaux commented 3 weeks ago

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

lu-zero commented 3 weeks ago

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

JaFenix commented 3 weeks ago

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

ocohen commented 3 weeks ago

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

On Wed, Oct 30, 2024, 7:33 a.m. JaFenix @.***> wrote:

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

— Reply to this email directly, view it on GitHub https://github.com/linebender/resvg/issues/838#issuecomment-2447178725, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAATPILTEKWA3KKCTK5GS4TZ6DN4BAVCNFSM6AAAAABQ2LFKBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBXGE3TQNZSGU . You are receiving this because you were mentioned.Message ID: @.***>

real-or-random commented 3 weeks ago

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

real-or-random commented 3 weeks ago

nit: I'm happy to make that statement (as I've done in the previous comment), but I think technically it'll be more correct to restrict it to past contributions:

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

It's hard to predict what will happen in the future, so I'm not sure if everyone is comfortable making a statement about the future. But future contributions will, of course, be anyway covered by the "inbound=outbound" rule, which is also made explicit in the GitHub ToS.

Or if you're worried about currently open PRs etc., perhaps this:

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

Feel free to ignore me. As I said, I'm fine with the statement, I just want to help.

iamralpht commented 3 weeks ago

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

ferdnyc commented 3 weeks ago

Because the statement is in a text block and not wrapped, I can't read the whole thing in the Android app. Put me down for don't care / do whatever

jrmuizel commented 3 weeks ago

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

nyurik commented 3 weeks ago

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

yisibl commented 3 weeks ago

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

DJMcNab commented 3 weeks ago

@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 commented 3 weeks ago

@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 commented 3 weeks ago

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

AnthonyMikh commented 3 weeks ago

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 commented 3 weeks ago

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

niklasf commented 3 weeks ago

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

dhardy commented 3 weeks ago

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

Stoeoef commented 3 weeks ago

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

valpackett commented 3 weeks ago

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

antmelnyk commented 3 weeks ago

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

linebender / resvg