Minecraftforge: Relicensing Forge to LGPL 2.1

Created on 28 Apr 2016 · 97Comments · Source: MinecraftForge/MinecraftForge

Forge is currently a mishmash of several different licenses. They are probably all FOSS, however, the primary initial license was not clearly FOSS and had several probable loopholes.

Additionally, the patches directory needs to be licensed separately, as that is mostly generated code, and it's impossible to properly attribute any form of ownership beyond the project.

The new license text is found at "LICENSE-new.txt" in the root of the project (1.9 branch) here: https://github.com/MinecraftForge/MinecraftForge/blob/1.9/LICENSE-new.txt

This issue is to track the consent of all contributors to the Forge project who have code active at this time.

The below authors list was generated from the 1.9 branch on the 28th April 2016 and represents every line of java code present in Forge today, and it's attribution. Note that many are trivial attributions (changing whitespace or comment boilerplate) and as such we will mark them as accepted since they are non-functional.

However, others are more substantial and we would like a reply to this issue from each author below consenting to the relicensing of your contribution to the LGPL as detailed above.

Sample consent message:

I github user listed above as email address consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

The relicense should happen between 1.9.3 and the next release of Minecraft. It has no impact on any mods and their licensing.

Trivial Contributions

Some members of this list are authors of what is considered Trivial Contributions. This is a contribution that is to trivial to be copyrightable.
Mostly this includes <5 line bug fix, or whitespace changes.
Any person listed here as a Trivial Contribution should respond by June 28th 2016 if they have any objections and their contributions can be removed.

Contributors

| Accepted | Lines of code | Email address | Comment |
| --- | --- | --- | --- |
|

| 26 | [email protected] | |
|

| 19 | [email protected] | |
|

| 1 | [email protected] | Trivial Contribution |

RFC

Source

cpw

👍22 🎉11 😄1 👎1

Most helpful comment

And we are done! Thank you ALL for your help. https://github.com/MinecraftForge/MinecraftForge/commit/c8d775c865bc6fba204072c2ac18cd64d787112f

cpw on 23 Jun 2016

🎉31

All 97 comments

I @cpw listed above as [email protected] and [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

cpw on 28 Apr 2016

🎉2 👍1

I @matthewprenger listed above as both [email protected] and [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

matthewprenger on 28 Apr 2016

👍2

I @LexManos listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

LexManos on 28 Apr 2016

👍2

I @heldplayer listed above as mitchel.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

heldplayer on 28 Apr 2016

👍2

I @Emberwalker listed above as [email protected] / [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Emberwalker on 28 Apr 2016

👍2

I @RainWarrior listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

RainWarrior on 28 Apr 2016

👍2

I @kashike listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

kashike on 28 Apr 2016

👍2

I @lumien231 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

lumien231 on 28 Apr 2016

👍2

I @maruohon listed above as matti.j.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

maruohon on 28 Apr 2016

👍2

I @simon816 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

simon816 on 28 Apr 2016

👍2

I @iTitus listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

iTitus on 28 Apr 2016

👍2

I @diesieben07 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

diesieben07 on 28 Apr 2016

👍2

I @Lunatrius listed above as jadran.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Lunatrius on 28 Apr 2016

👍2

I @bloodmc listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

bloodmc on 28 Apr 2016

👍2

I @bspkrs listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

Also, I think that the LGPL 2.1 is a pretty good license... for me to POOP on!

You all need public profiles, too: #redacted

bspkrs on 28 Apr 2016

👍4 ❤1 😕1 🎉1 😄1

I @LepkoQQ listed above as lepko.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

LepkoQQ on 28 Apr 2016

👍2

I @williewillus listed above as vincent.[email protected] (and perhaps as [email protected] on older patches which might not be present anymore in 1.9) consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

williewillus on 28 Apr 2016

👍2

I @fnuecke listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

fnuecke on 28 Apr 2016

👍2

I @Choonster listed above as Choonster.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Choonster on 28 Apr 2016

👍2

My contributions ([email protected]) may be used under the terms of the LGPL license, v2.1, v3 or later.

sfPlayer1 on 28 Apr 2016

👍2

I @Glassmaker listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Glassmaker on 28 Apr 2016

👍2

I @rwtema listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

rwtema on 28 Apr 2016

👍2

I @Vorquel listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Vorquel on 28 Apr 2016

👍2

I @SpaceToad listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

SpaceToad on 28 Apr 2016

👍2

I @gigaherz listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

gigaherz on 29 Apr 2016

👍1

I @luacs1998 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

yuuka-miya on 29 Apr 2016

👍1

I @me4502 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

me4502 on 29 Apr 2016

👍1

I @AbrarSyed listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

AbrarSyed on 29 Apr 2016

👍1

I @liach listed above as [email protected] and [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

liach on 29 Apr 2016

👍1

I @amaranth listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

amaranth on 29 Apr 2016

👍1

I @ganymedes01 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

ganymedes01 on 29 Apr 2016

👍1

I @HoBoS-TaCo listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

HoBoS-TaCo on 29 Apr 2016

👍1

I @mezz listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

mezz on 29 Apr 2016

👍1

I @iChun listed above as ohai.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

iChun on 29 Apr 2016

👍1

I @iLexiconn listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

iLexiconn on 29 Apr 2016

👍3

I @Adubbz listed above as a.[email protected] / [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Adubbz on 29 Apr 2016

👍1

I @Geforce132 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

Geforce132 on 29 Apr 2016

👍1

I @boq listed above as bartek.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

boq on 29 Apr 2016

👍1

I @Mumfrey listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

Mumfrey on 30 Apr 2016

😄1 👍1

Even though I don't show up I contributed a few lines of code a few years ago originally in RendererEntityPlayer and lex moved it to RendererEntityLiving https://github.com/MinecraftForge/MinecraftForge/blob/master/patches/minecraft/net/minecraft/client/renderer/entity/RendererLivingEntity.java.patch#L7

I @darkguardsman, not listed, consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

DarkGuardsman on 30 Apr 2016

👍1

I @tterrag1098 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

tterrag1098 on 30 Apr 2016

👍1

I @bonii-xx listed above as bernhard.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

bonii-xx on 30 Apr 2016

👍1

Ping these people. The others don't have their email publicly attached to their profile.
@Minecrell [email protected]
@VikeStep [email protected]
@Abastro [email protected]
@darkevilmac [email protected]
@DemoXinMC [email protected]
@CovertJaguar [email protected]
@jeffreykog [email protected]
@MrIbby [email protected]
@JamiesWhiteShirt [email protected]

matthewprenger on 30 Apr 2016

👍1

I @VikeStep listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

VikeStep on 30 Apr 2016

👍1

Ping these people. The others don't have their email publicly attached to their profile.

Have had my email listed for about a week now but whatever, feel free to relicense as you please now and in the future. I only added an event anyways.

I @darkevilmac consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

darkevilmac on 30 Apr 2016

👍1

I @jk-5 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

jeffreykog on 30 Apr 2016

👍1

Actually i am a subaccount of @jk-5, used only for school/study use. I previously used this account to make a contribution.

I @jeffreykog consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

ghost on 30 Apr 2016

👍1

Um, what? Do a little research and you'll quickly find:

"The problem is, if you sub-class a class which is subject to the LGPL license in your own code, then your work becomes a work based on the library, rather than a work which uses the library which means that your code is a derivative work that is covered under section 2 (LGPL v2.1) rather than one covered under section 6 (LGPL v2.1). I.e. it becomes subject to the LGPL!"

HenryLoenwind on 30 Apr 2016

👎1

That is heavily taken out of context, read the rest of the comments on that stackoverflow post

williewillus on 30 Apr 2016

For others: http://programmers.stackexchange.com/questions/136702/does-the-lgpl-allow-me-to-do-this

williewillus on 30 Apr 2016

I @JamiesWhiteShirt listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

JamiesWhiteShirt on 30 Apr 2016

👍1

I @Minecrell listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Minecrell on 30 Apr 2016

😄1 👍1

I @CovertJaguar listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt on 4-30-2016.

CovertJaguar on 30 Apr 2016

😄1 👍1

I @Chicken-Bones listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Chicken-Bones on 1 May 2016

😄1 👍1

I @pau101 listed above as paul.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

pau101 on 1 May 2016

👍2 😄1

I @XCompWiz listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

XCompWiz on 2 May 2016

🎉2 👍1

I @KingLemming listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt on 05-02-2016.

KingLemming on 2 May 2016

🎉2 👍1

I @Cojomax99 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Cojomax99 on 2 May 2016

👍1

I @Zaggy1024 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

Zaggy1024 on 2 May 2016

👍1

I @MrIbby listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

ghost on 3 May 2016

👍1

I @superckl listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

superckl on 3 May 2016

👍1

I @shadekiller666 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

shadekiller666 on 4 May 2016

👍1

I @DemoXinMC listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

DemoXinMC on 4 May 2016

👍1

I wrote this, but I think because lex edited it later, it didn't get processed. https://git.io/vw7lD

I @killjoy1221 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

killjoy1221 on 4 May 2016

👍1

I @TheTemportalist listed above as the.country.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

TheTemportalist on 9 May 2016

👍1

I @ScottKillen listed above at [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

ScottKillen on 9 May 2016

👍1

I @Ghostrec35 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Ghostrec35 on 10 May 2016

👍1

People who have not replied as of https://github.com/MinecraftForge/MinecraftForge/issues/2789#issuecomment-222357939+ commits by them in HEAD:

| Email | Username | Commits | PRs (if any) |
| --- | --- | --- | --- |
| [email protected] | @OniBait | 296a484f 79e01653 e47a6402 eb594066 | #852 |
| ~~[email protected]~~ | ~~@Zarathul~~ | ~~7a1de8c1~~ | |
| ~~[email protected]~~ | ~~@Zot201~~ | ~~ccffcf60~~ | |
| ~~claire.[email protected]~~ | ~~@MachineMuse~~ | ~~0e3037e8 e3e3ea54 ee0cb128~~ | |
| ~~[email protected]~~ | ~~@Abastro~~ | ~~c4ca8270 f590ce86~~ | |
| ~~tommy.[email protected]~~ | ~~@tommy1019~~ | ~~077e05e0 9e732ee9 efb27ed1~~ | |
| ~~[email protected]~~ | ~~@EnderShadow~~ | ~~bf8f5aa3~~ | |
| ~~[email protected]~~ | ~~@Mithion~~ | ~~2a76f774 4de9793e e13dff30 ee6dce23~~ | |
| [email protected] | @Eurymachus | 8d0b58ee | #792 |
| [email protected] | @Crudedragos | 9b58fb93 aa202878 | #467 |
| [email protected] | @agaricusb | 03bc9cf0 | |
| xxt1g3lxx.[email protected] | @t1g3l | 6a299a48 fe327fbd | #1878,#1882 |
| ~~[email protected]~~ | ~~@irtimaled~~ | ~~1eb535f1~~ | |
| ~~[email protected]~~ | ~~@Parker8283~~ | ~~ff36d4f1~~ | |
| [email protected] | @jamioflan | 306af4fe | #1858 |
| ~~[email protected]~~ | ~~@Draake~~ | ~~ddd406ba~~ | |
| ~~[email protected]~~ | ~~@ShadwDrgn~~ | ~~24cec145 77bd22d3~~ | |

Edit: added PR links for remaining people.

RainWarrior on 13 May 2016

👍4

I @Mithion listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Mithion on 13 May 2016

👍1

I @EnderShadow listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

EnderShadow on 13 May 2016

👍1

I @irtimaled listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

irtimaled on 13 May 2016

👍1

I @draake listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Draake on 13 May 2016

👍1

I @tommy1019 listed above as tommy.[email protected] to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

tommy1019 on 13 May 2016

👍1

I @Zarathul listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Zarathul on 13 May 2016

👍1

My contributions (CENSORED) may be used under the terms of the LGPL license, v2.1, v3 or later.

ShadwDrgn on 13 May 2016

👍1

yes me too LGPL is fine

MachineMuse on 13 May 2016

My contributions ([email protected]) may be used under the terms of the LGPL license, v2.1 or any other license as long as it doesn't make it possible for somebody to sue me for using them elsewhere

MachineMuse on 13 May 2016

👍1

I @nekosune, give all rights for any contributions I have made, to the MinecraftForge project, for use as they see fit.

nekosune on 14 May 2016

👍1

I @Parker8283 consent to the relicensing of my contributions to the Forge
project under the license as stated in LICENSE-new.txt

[Edit: 05/29/2016 Lex] For clarity, he is listed as [email protected]

On May 13, 2016 6:38 PM, "Katrina Swales" [email protected] wrote:

I @nekosune https://github.com/nekosune, give all rights for any
contributions I have made, to the MinecraftForge project, for use as they
see fit.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/MinecraftForge/MinecraftForge/issues/2789#issuecomment-219175900

Parker8283 on 14 May 2016

👍1

I @Abastro listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Abastro on 20 May 2016

👍2

List is getting short :)

gigaherz on 20 May 2016

@williewillus added labels [RFC]

Actuarius on 29 May 2016

Updated main list, we are currently at 7 people:

Contributors

| Accepted | Lines of code | Email address | Comment |
| --- | --- | --- | --- |
|

| 10 | [email protected] | Attrib |

About 1/2 of them I would consider trivial contributions. But i'll deal with that later.

LexManos on 29 May 2016

👍2

I @Zot201 listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Zot201 on 29 May 2016

👍1

OK, so at present we have 5 authors who need to consent to the license change. Paging @OniBait @Eurymachus @Crudedragos @t1g3l @jamioflan please consent to the above license change or respond with your objections below.

cpw on 19 Jun 2016

OniBait idling at IRC, channel #cauldron

ghost on 19 Jun 2016

I @jamioflan listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt.

jamioflan on 19 Jun 2016

👍5

I @Crudedragos listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

Crudedragos on 19 Jun 2016

👍6

I @onibait listed above as [email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

OniBait on 20 Jun 2016

🎉11 👍5

Updated the Main list. The last hold outs are:

Contributors

| Accepted | Lines of code | Email address | Comment |
| --- | --- | --- | --- |
|

| 19 | xxt1g3lxx.[email protected] | Attrib |

Lets see if we can get these guys in here!

LexManos on 20 Jun 2016

For Eury, a mutual friend of mine will reach out to him if he sees him online on Steam (he was last online within the last day, but he only comes on during his free time)

smbarbour on 21 Jun 2016

👍2

And we are done! Thank you ALL for your help. https://github.com/MinecraftForge/MinecraftForge/commit/c8d775c865bc6fba204072c2ac18cd64d787112f

cpw on 23 Jun 2016

🎉31

YAYAYAYAYAYAYAYAY

ghost on 23 Jun 2016

I @t1g3l listed above as xxt1g3lxx.[email protected] consent to the relicensing of my contributions to the Forge project under the license as stated in LICENSE-new.txt

ghost on 3 Jul 2016

now that this is long closed can we remove this giant spammers dream list of emails please?

ShadwDrgn on 18 Apr 2020

😕2

Without removing documentation, no.
Everyone's emails are public on github.
It's a simple task to scrape everyone's email from every account/git on the site.

LexManos on 18 Apr 2020

👍1

Yep, these emails are actually all grabbed from forge's commit history. As long as the commit history is not edited to remove the emails (which probably won't happen here), your email will be up here. Removing this issue doesn't solve the problem.

And afaik some researcher from like canada has obtained all these email from scanning commit log and sent emails for research on contributors to forge a while ago.

liach on 18 Apr 2020

Was this page helpful?

0 / 5 - 0 ratings

Related issues

[1.13.2] Options in a generated config.toml have the wrong order

Ruuubi · 3Comments

[1.13.2] BlockEvent.PlaceEvent not getting fired

MJRLegends · 3Comments

[META] Require companion ReadTheDocs PR for all new feature PR's

williewillus · 3Comments

The method register(K) from the type GameRegistry is not visible

ErikBigDev · 3Comments

Mod List scales incorrectly on HiDPI Setups

juliand665 · 3Comments