Relicensing (bits of) CC: Tweaked

Question

Relicensing (bits of) CC: Tweaked

SquidDev opened this issue 2 years ago · 120 comments

I've been wanting to do this for years, and seriously considering it for about 4 months now, so might as well get the ball rolling somehow!

The Problem

When ComputerCraft was originally open sourced, it was released under the CCPL (ComputerCraft Public License), a derivative of the MMPL (Minecraft Mod Public License). Unfortunately, both the MMPL and CCPL have a couple of issues, which range from irritating to gaping holes:

It's not a standard OSI-approved license. While in some sense this is purely a cosmetic issue, it has stopped several people contributing, and also blocks us from participating in some initiatives such as Modtoberfest.
Code licensed under the CCPL can only be used in other Minecraft mods, and that code must be licensed under the CCPL. This means that any usage of the code in a non-mod project (including emulators or CC programs) violates the license.

This is an incredibly restrictive clause, to the point that it's counterproductive. I can think of half a dozen (well meaning and useful!) projects off the top of my head which violate this clause.
All dependencies of ComputerCraft must be licensed under conditions comparable to the CCPL. We inherit this condition from the MMPL, and it's definitely a problematic one. While I do not believe it's the intention, the practical outcome is that all dependencies must be licensed under the CCPL. While there are exceptions for Minecraft and the mod loader (Forge/Fabric), there aren't any exceptions for other dependencies, such as the Java Standard Library or Netty.

This suggests that even ComputerCraft itself violates its own license, a position which is clearly untenable!

The difficulty of relicensing

Given CC/CC:T's license is somewhere between awkward and untenable, I would like to relicense CC: Tweaked under something more standard and permissive.

Relicensing a project requires getting every single previous contributor to sign off on the new license. This is incredibly hard for a couple of reasons:

Firstly, CC: Tweaked has had 98 people contribute to it. While 20-30 of these people have only committed trivial changes, which don't require permission, this is still a lot of people and will be a slow process. I remember Forge's relicensing process took months, and I don't think BuildCraft ever managed to complete theirs!

Secondly, and perhaps more seriously, this list of people includes Dan. I have raised relicensing CC with Dan in the past, and while he's been receptive, as of writing nothing concrete has happened. I think we should assume that we will NOT be able to get Dan's permission to relicense his code.

Alternatives

While we cannot change the whole mod, I do think we should aim to relicense as much code as possible under something more permissive.

I'm proposing using the Mozilla Public License 2.0 (MPL 2.0) as the license of choice here. This is a weak copyleft license, which means that changes to the original code must be released (more or less forcing forks of the mod to remain open source) but unlike the GPL (or derivatives) is not viral, meaning it can be used in more permissively licenced projects.

In terms of actually handling the relicensing, I believe our best route here is to adapt the REUSE project's conventions: tracking copyright and licensing on a file-by-file basis, rather than a blanket license for the whole project.

I'm not entirely sure this is Correct(TM): if anyone in the UK knows a good source of legal advice for OS software licensing please do get in touch. However, I think it's a Best Effort given the current mess we're in.

In closing

I don't know if any of the above sounds remotely sensible. Would appreciate any and all feedback here!

I'm probably going to let this issue sit for a few weeks to gather some feedback, then will update this issue on whether I want to go ahead with this or not.

Answer 1 · 2023-02-18T05:00:22.000Z

a side note if you want to port the whole project to kotlin should allow you relicense with out needing to get permission

Answer 2 · 2023-02-18T08:18:18.000Z

While a rewrite would be possible (either to Kotlin or staying in Java), it's an incredibly large task. I don't have exact numbers here, but I'd estimate there's about 25k lines of Java and 10k lines of Lua¹ where Dan still retains the copyright. While these things have been done in the past, I just don't think we've got enough people to do it!

Tokei reports 32k lines of Java and 13k lines of Lua, in projects/*/src/main (excluding comments and whitespace). I honestly don't know how much entirely new code has been added. ↩

Answer 3 · 2023-02-18T09:32:51.000Z

i use the word port not rewrite as jet-brains has tools that automates the process to go from java to kotlin that would just leave the lua code

Answer 4 · 2023-02-18T09:46:27.000Z

Converting code to another language doesn't change the copyright. It's a bit like translating a book to another language - the original author still retains ownership!

Answer 5 · 2023-02-18T09:53:45.000Z

well i know that the Australian government begs to differ im guessing others do to

Answer 6 · 2023-03-01T02:10:32.000Z

For the record, I approve of any license changes to my contributions as long as the license is OSI-approved.

Answer 7 · 2023-03-29T09:28:18.000Z

The initial relicensing work is now complete and merged. I'm going to start the process of reaching out to people, requesting permission to relicense their contributions. I'm planning to do this in batches, just to make my life a bit easier.

If you're in the list of people below (or have contributed to CC:T in the past and feel like getting ahead of things), would you be able to comment with the following message:

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

If you're not happy to relicense your contributions, please also let me know, so I know not to poke you further!

User	Permission granted	Contributions
@bradyakent	✔️	`9ae0f4a`
@emmachase	✔️	Numerous
@JakobDev	✔️	Numerous
@Lemmmy	✔️	Numerous
@Lupus590	✔️	Numerous
@MAGGen-hub	✔️	#918
@MCJack123	✔️	Numerous
@Merith-TK	✔️	#817
@Naheulf	✔️	#488
@ouroborus	✔️	#1304
@plt-amy	✔️	Numerous
@powerboat9	✔️	#274, #276
@Ronan-H	✔️	#743, #740, #738
@SirEndii	✔️	#1083
@toad-dev	✔️	Numerous
@Wojbie	✔️	Numerous

Answer 8 · 2023-03-29T09:32:14.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my project contributions to the CC: Tweaked project.

I am really liking the direction this re-licensing takes project in.

Answer 9 · 2023-03-29T09:46:23.000Z

Is there an option to transfer whatever copyrights I may hold on my contributions to the project, or such, rather than just licensing them?

Answer 10 · 2023-03-29T10:02:03.000Z

Yep, I'm happy to do that, though I think in that case I'd probably rather both? The legal complexities of copyright assignment are a bit more messy, so I'd like to CYA as much as possible!

I don't know if the following sounds reasonable?

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my contributions to the CC: Tweaked project.

Answer 11 · 2023-03-29T10:05:21.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my contributions to the CC: Tweaked project

Answer 12 · 2023-03-29T10:13:30.000Z

Works for me. I consider my contribution to be a donation to the project. My continuing to hold whatever copyright I might have goes against my intent with regards to my contribution to this project.

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my CC: Tweaked project contributions to the CC: Tweaked project.

Answer 13 · 2023-03-29T11:46:58.000Z

You can changes / multi-license my past contributions in this project. As may times as you want as long as:

no one can claim ownership of that code
the code AND the changes MUST remain open sourced (Edit: to reuse the OSI definition: there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost)

Answer 14 · 2023-03-29T12:54:52.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my project contributions to the CC: Tweaked project.

Great to see this is finally happening, fantastic work on the relicensing effort so far!

Answer 15 · 2023-03-29T15:05:14.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 16 · 2023-03-29T15:11:11.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my project contributions to the CC: Tweaked project.

Answer 17 · 2023-03-29T15:14:09.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

I should note that there is at least one PR that has commits by me where I do not claim ownership of the code, instead, the code was copied from other changes that @SquidDev was making at the time. I will see if I can find the PR mentioned and link it.

Answer 18 · 2023-03-29T15:22:28.000Z

@Lupus590 Thank you! Is that #603, or is there another one?

Answer 19 · 2023-03-29T15:35:28.000Z

@Lupus590 Thank you! Is that #603, or is there another one?

Yeah, that's it.

Answer 20 · 2023-03-29T16:29:12.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my project contributions to the CC: Tweaked project.

Answer 21 · 2023-03-29T17:50:22.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

I kindly request that all of my past and future contributions made to the Computer Craft project be considered under the MPL-2.0 license, where applicable.

Answer 22 · 2023-03-29T17:56:57.000Z

What would happen to the code of people who do not agree?

And what will be the future license CC:T will use (did not saw it in the messages of squid)?

Answer 23 · 2023-03-29T18:09:01.000Z

@SirEndii

What would happen to the code of people who do not agree?

That code would remain under CCPL.

And what will be the future license CC:T will use (did not saw it in the messages of squid)?

MPL 2.0 is the goal, though it's highly likely that a portion is still CCPL, so it would be dual-license.

Answer 24 · 2023-03-29T18:12:52.000Z

What would happen to the code of people who do not agree?

Currently, nothing. That code will remain in the mod and licenced under the CCPL.

If Dan ever agrees to relicense the original ComputerCraft code, then I would probably start looking into rewriting or removing that code, but I think that's pretty unlikely.

And what will be the future license CC:T will use

The main description goes into this in a bit more detail, but the general gist is that we're handling licensing on a per-file basis rather than a blanket project-wide license. New code will be under the MPL 2.0.

I guess for some additional context here on the choice of MPL 2.0, both Dan and I would prefer that CC remains under a copyleft license. I personally don't think GPL and LGPL are a great choice here, as part of the relicensing is to make it easier to reuse components of the mod (especially the ROM) in other projects, hence MPL 2.0 instead.

Answer 25 · 2023-03-29T18:16:08.000Z

Personally I would say the ROM can remain under CCPL, since not much has needed to be changed on that front over the years.

However the mod code has been changed alot, to the point where in modern versions I doubt much of the original code even exists outside of references to dan200 java classes.

Answer 26 · 2023-03-29T18:21:28.000Z

Thank you for everyone who has agreed so far! Just adding a couple of extra people that I'm afraid my script missed the first time round:

If you're in the list of people below, would you be able to comment with the following message:

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

If you're not happy to relicense your contributions, please also let me know, so I know not to poke you further!

User	Permission granted	Contributions
@Gegy	✔️	dan200/ComputerCraft#237
@heap-underflow		#1131
@itisluiz	✔️	#1127
@Lignum	✔️	Numerous
@lilyzeiset	✔️	#749
@Restioson	✔️	dan200/ComputerCraft#237

Answer 27 · 2023-03-29T18:24:53.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my contributions to the CC: Tweaked project.

Answer 28 · 2023-03-29T18:42:10.000Z

However the mod code has been changed a lot, to the point where in modern versions I doubt much of the original code even exists outside of references to dan200 java classes.

It's honestly still 50/50 Dan code (or at least something close enough to Dan's code) vs new code. I've got a script which plots a sunburst graph of file licenses, where red is CCPL and blue is MPL 2.0:

Bits like the turtle and peripheral code have changed a lot due to Minecraft updates, but still retain almost all original logic.

Answer 29 · 2023-03-29T18:44:29.000Z

Could I ask you how you made that graph?

Answer 30 · 2023-03-29T18:46:23.000Z

My guess is the script looks at the current code and git blame output, while checking an list of users that he inputs as MPL2

Answer 31 · 2023-03-29T18:59:54.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 32 · 2023-03-29T19:14:48.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 33 · 2023-03-29T19:50:58.000Z

Could I ask you how you made that graph?

@SirEndii

The actual data is taken from the license headers: the reuse CLI spits out a machine readable file which is fairly easy to consume in Python.
Plotting is done via plotly's sunburst charts.

Answer 34 · 2023-03-29T21:04:46.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Looks like I'm still one of the top contributors even after all this time. The Project has changed a lot since then and it's nice to see it's still maintained by you. Maybe a could take a look at CC again.

Where did you know which one contributed which code? I had take a look at a few files and it looks like the files where moved so often, that even git is confused.

Answer 35 · 2023-03-29T21:17:28.000Z

Amazing, thank you so much @JakobDev! You've made a lot of key contributions over the years, so great to have you on board!

Where did you know which one contributed which code? I had take a look at a few files and it looks like the files where moved so often, that even git is confused.

If you pass --follow to git log, it's a bit better at tracking renames. I'm using that to get an overview of who has contributed watch to each file, and then digging into individual commits when things are a bit more fuzzy (for instance Peripherals only has me in the git log, but the original code was written by Dan and then split out into a separate file).

Answer 36 · 2023-03-30T12:32:08.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my project contributions to the CC: Tweaked project.

Answer 37 · 2023-03-30T12:59:41.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my project contributions to the CC: Tweaked project.

Answer 38 · 2023-03-30T17:57:50.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my contributions to the CC: Tweaked project.

Answer 39 · 2023-03-30T19:30:28.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 40 · 2023-03-30T20:28:55.000Z

I love to see how good this works

Answer 41 · 2023-04-13T00:05:48.000Z

This is amazing

Answer 42 · 2023-04-13T00:38:33.000Z

I'm very excited for this!
It would make me very happy if the mod that partly shaped me would finally get legally more accessable and under a OPL. It's amazing how far this already has come.

Answer 43 · 2023-05-19T20:43:19.000Z

Thank you for everyone who has agreed so far! I'm continuing with the everyone else now, in (roughly) alphabetical order.

If you're in the list of people below, would you be able to comment with the following message:

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

If you're not happy to relicense your contributions, please also let me know, so I know not to poke you further!

User	Permission granted
@absolument	✔️
@Ale32bit	✔️
@Angalexik
@AxelFontarive	✔️
@baebz	✔️
@bclindner	✔️
@BlackDragon-B	✔️
@Bluenaxela	✔️
@BombBloke	✔️
@boq	✔️
@chesiren	✔️
@ChickChicky
@ChristianLW	✔️
@coolsa	✔️
@CrazedProgrammer	✔️
@Cruor	✔️
@daelvn	✔️
@dmarcuse	✔️
@emiliskiskis
@Granddave	✔️
@LelouBil	✔️
@mindy15963
@signalhunter	✔️
@SirEdvin	✔️
@xAnavrins	✔️

Answer 44 · 2023-05-19T20:46:03.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 45 · 2023-05-19T20:49:31.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 46 · 2023-05-19T21:08:09.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my past contributions to the CC: Tweaked project.

I'm glad you're trying to solve this issue and that so many are happy to give the green light!

Answer 47 · 2023-05-19T21:34:15.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

oh my god its been a long time hi squid
i had no idea that i actually had significant contributions to cc:t thats insane
good luck getting the relicense through!

Answer 48 · 2023-05-19T21:49:27.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 49 · 2023-05-19T21:52:31.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Gotta make sure that one liner I did is licensed correctly, lol.

Thank you for your endless work!

Answer 50 · 2023-05-19T22:05:37.000Z

Oh cool, I was kind of hoping for a more standardized license.

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Thanks folks!

Answer 51 · 2023-05-19T22:20:40.000Z

I have committed a couple things here, though I don't know if what I committed was already under a new license. In case they weren't though,

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 52 · 2023-05-20T08:10:00.000Z

I even doesn't knew, that I have commited something useful :)

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0. Additionally, I would like to assign copyright ownership of my past and any future contributions to the CC: Tweaked project to the CC: Tweaked project itself.

Thank you for your endless work!

Answer 53 · 2023-05-20T18:09:34.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 54 · 2023-05-20T19:17:37.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

(I'd forgotten I did a minor little pull request once upon a time, haha. Seems like a sensible relicense in any case)

Answer 55 · 2023-05-20T20:17:59.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Good luck with the relicensing!

Answer 56 · 2023-05-21T05:20:08.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 57 · 2023-05-21T06:04:19.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 58 · 2023-05-21T08:33:39.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 59 · 2023-05-21T08:37:16.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

It's been some time since I last logged in with this account, thanks for making CC:T more open!

Answer 60 · 2023-05-21T14:04:22.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Likewise for any other such changes SquidDev may wish to make in the future.

Answer 61 · 2023-05-21T17:27:29.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 62 · 2023-05-22T09:14:24.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 63 · 2023-05-24T08:07:08.000Z

Thank you for everyone who has agreed so far! We're over a third of the way there now!

If you're in the list of people below, would you be able to comment with the following message:

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

If you're not happy to relicense your contributions, please also let me know, so I know not to poke you further!

User	Permission granted
@exerro	✔️
@Hasaabitt	✔️
@hugeblank	✔️
@Iunius118	✔️
@IvoLeal72	✔️
@jakedacatman
@jaredallard	✔️
@JLLeitschuh	✔️
@JohnnyIrvin
@josephcsible	✔️
@Jummit	✔️
@khankul	✔️
@liquiad	✔️
@Luca0208	✔️
@magiczocker10	✔️
@Marco4413	✔️
@teteukt
@MineRobber9000	✔️
@MORIMORI0317	✔️
@neumond	✔️
@nothjarnan	✔️
@Ocawesome101	✔️
@RuiNtD	✔️
@Techman749	✔️
@zyxkad	✔️

Answer 64 · 2023-05-24T08:38:37.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 65 · 2023-05-24T08:49:30.000Z

You do know that you're subscribing everyone you mention to this issue, meaning they get an E-Mail for every reply? (On the same note: Hello to a lot of people) [Not that I'd know a better way to do this, just wanted to put out a quick word of warning that you're potentially spamming a lot of people]

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 66 · 2023-05-24T08:58:53.000Z

You do know that you're subscribing everyone you mention to this issue, meaning they get an E-Mail for every reply?

I am aware it's a problem, but as you say I'm not really sure there's a better way. I would recommend people hit the unsubscribe button on this issue once responding, as that should shut up this issue again. :)

Answer 67 · 2023-05-24T09:09:47.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 68 · 2023-05-24T11:52:54.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 69 · 2023-05-24T11:55:36.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

…

________________________________ From: Hasaabitt ***@***.***> Sent: Wednesday, May 24, 2023 1:53:07 PM To: cc-tweaked/CC-Tweaked ***@***.***> Cc: Linus Ramneborg ***@***.***>; Mention ***@***.***> Subject: Re: [cc-tweaked/CC-Tweaked] Relicensing (bits of) CC: Tweaked (Issue #1339) I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0. — Reply to this email directly, view it on GitHub<#1339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADXYWEZAEOUOTDGTTK2ZKB3XHXZCHANCNFSM6AAAAAAU6SUUXI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

Answer 70 · 2023-05-24T12:18:14.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

:)

Answer 71 · 2023-05-24T12:45:49.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Let's got this done!

Answer 72 · 2023-05-24T13:52:17.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 73 · 2023-05-24T14:17:24.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 74 · 2023-05-24T14:18:09.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 75 · 2023-05-24T14:47:35.000Z

After getting 8+ emails about this, I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 76 · 2023-05-24T15:17:23.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Additionally, I assign copyright ownership of my contributions to the CC: Tweaked project.

i had no idea i'd made contributions that would qualify for something like this. neat.

Answer 77 · 2023-05-24T16:14:25.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 78 · 2023-05-24T16:17:53.000Z

I would like to softly note that I prefer GPL-3.0-or-later, but I am much more for uniformity. Also, my change was very very small (on another note, hi again @SquidDev! 👋)

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 79 · 2023-05-24T16:51:24.000Z

I would like to softly note that I prefer GPL-3.0-or-later!

Hello 👋! Wow, it really has been an age. Hope you're doing well :).

I did consider GPL, however there are a couple of problems with it in the context of ComputerCraft:

It's not clear whether Minecraft counts as a system library or not - after all, it's not part of the operating system or core Java VM. Given Minecraft is proprietary, I'm not confident you can have GPL licenced mods.

The FSF does provide some advice and workarounds for this, so it's not insurmountable, but also defeats the point of using an entirely standard license.
Licensing CC's Lua code under the GPL is a no-go, as then all programs for CC:T would have to be distributed under the GPL. There's a bit of me which would approve of that, but also it's a can of worms I'd rather avoid opening.

We could probably use the LGPL here instead, but at that point I feel the MPL 2.0 does a better job of being a less-viral copyleft license.

According to my spreadsheet, we're half way there! Thank you everyone ❤️ 💖

Answer 80 · 2023-05-24T19:13:42.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 81 · 2023-05-25T19:52:14.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 82 · 2023-05-26T07:02:15.000Z

Thank you for everyone who has agreed so far! This should be everyone now!¹

If you're in the list of people below, would you be able to comment with the following message:

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

If you're not happy to relicense your contributions, please also let me know, so I know not to poke you further!

Apologies for the inevitable email spam here - I'd recommend hitting unsubscribe on the issue afterwards!

User	Permission granted
@9551-Dev	✔️
@dirthsj	✔️
@Gibbo3771
@livegamer999
@Luca-Ilari	✔️
@MrSvyatik
@ObloxCC
@osmarks	✔️
@parly	✔️
@Paspartout	✔️
@Possseidon	✔️
@Quezler	✔️
@R93950X	✔️
@ralphgod3	✔️
@roland-a
@RomanPlayer22	✔️
@SkyTheCodeMaster	✔️
@theoriginalbit	✔️
@TheWireLord	✔️
@timia2109	✔️
@Vexatos	✔️
@wackbyte	✔️
@Wendelstein7	✔️
@XuyuEre
@xXTurnerLP	✔️

Well, there's a couple of people no longer on GitHub. I'm going to contact them directly. ↩

Answer 83 · 2023-05-26T07:04:16.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Good luck with the rest.

Answer 84 · 2023-05-26T07:08:07.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 85 · 2023-05-26T07:11:07.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 86 · 2023-05-26T07:56:32.000Z

I permit the license of my (small) contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Cheers

Answer 87 · 2023-05-26T08:14:29.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

hopefully everyone agrees :)

Answer 88 · 2023-05-26T08:14:58.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 89 · 2023-05-26T10:00:31.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 90 · 2023-05-26T10:05:51.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 91 · 2023-05-26T11:38:25.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 92 · 2023-05-26T11:40:16.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 93 · 2023-05-26T14:59:51.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

PS: I really like the dual Apache/MIT approach the Rust community uses. Not that it's worth anything this late in the process...

Answer 94 · 2023-05-26T15:31:24.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 95 · 2023-05-27T10:10:22.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 96 · 2023-05-27T13:18:22.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 97 · 2023-05-27T15:07:11.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 98 · 2023-05-27T16:55:24.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 99 · 2023-05-27T18:08:20.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

Answer 100 · 2023-05-29T15:04:06.000Z

I permit the license of my contributions to the CC: Tweaked project to be changed to the Mozilla Public License, v. 2.0.

The Problem

The difficulty of relicensing

Alternatives

In closing

Footnotes

Footnotes