Should I put the MIT license in my game created with godot?

system · October 8, 2016, 1:40pm


	Attention	Topic was automatically imported from the old Question2Answer platform.
	Asked By	Hormoz
	Old Version	Published before Godot 3 was released.

Hello.
Someone on this topic:

github.com/godotengine/godot

Wiki: licensing FAQ

opened 07:19PM - 05 Apr 15 UTC

closed 10:53AM - 09 May 18 UTC

Calinou

discussion documentation

In order to help against legal uncertainty when making games (and other stuff), …I've written a licensing FAQ page (attribution is appreciated but not required). I am pretty sure (but not 100 % sure) the content is valid. (Note that I'm not a lawyer professionally, I'm just someone who studies copyright as an hobby.) Could you add this to the wiki, please? This uses Markdown formatting. ``` Markdown **DISCLAIMER: this is not legal advice.** This page lists common questions about the licensing of Godot and possible uses. Q: Can I use Godot in my FLOSS project? ============================================ A: **Of course!** This is encouraged so that people can learn about Godot and study how it works. Q: Can I use Godot in my commercial project? ================================================= A: **Yes, you can.** Anyone is free to use Godot for both commercial and non-commercial purposes. There are no royalties to pay. Q: Can I use Godot in my proprietary project? ================================================== A: **Yes, you can.** You are not required to release the source code or the assets of your project. Q: Do I have to release my changes to the source code? ====================================================== A: **You don't have to release your changes**. This means you don't *have* to contribute to Godot upstream, although your help is appreciated. Q: Which licenses can I use for my code? ======================================== A: **In case you release the source code, almost any software license is valid.** It is recommended to use the MIT license or CC0 (public domain waiver) as it allows us to benefit from your changes and additions (ie. merge them upstream), but you can also use Apache, BSD, GPL or LGPL (any version) if you desire. Note that Creative Commons licenses (other than CC0) are **not recommended** for software. Please refrain from using them on code, however you can use them on assets just fine. Q: Which licenses can I use for my assets? ========================================== A: **Any license can be used for your assets**, including but not limited to: * Creative Commons licenses, * Public domain waivers (CC0, Unlicense, …), * The MIT license (of course), * Your own custom, proprietary license, * … Q: Am I allowed to remove the Godot splash screen? In other words, do I have to provide prominent attribution? ============================================================================================================== A: **Yes.** The splash screen is not required. No *prominent* attribution is required, however a mention of Godot engine in your project's credits and/or website is appreciated. Q: Do I grant a license to Godot developers over my project? ========================================================= A: **No, your project stays yours.** ``` Feel free to correct me, or to suggest new questions to add. You can paste the Markdown code [here](http://markdownlivepreview.com/) for a preview of how it would look on the wiki.

Said this:

“I’m not a lawyer either but here’s the thing… MIT license states “The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.” and because there is no definition of “software” it can be misinterpreted. Software can be defined as a set of machine instructions (which is binary file) meaning you’re legally obligated to put a MIT copyright somewhere in the executable file. So mentioning of godot is not required, but copyright notice must be included somehow (not necessarily has to be rendered to the screen). But to play it safe - just include it in the credits and be done with it.”

I made some part of it bold.
Is this true if it isn’t true why isn’t it true can you explain about it?

system · October 8, 2016, 3:40pm


	Reply From:	Calinou

Technically, you should include a copyright notice file in the games you distribute, regardless of their license (LICENSE.md being readable somewhere in your game is ideal, such as in an “About” menu). Large companies are very wary of this, and for example, iOS includes hundreds of open source license notices (even the GPL and LGPL).

However, Godot developers have stated they don’t mind people not putting copyright notices in their released game binaries. So, even if you don’t put any notice/credit about Godot, you should be fine.

(I am not a lawyer, this is not legal advice.)

Edit: See also Complying with Licenses in the documentation.

system · June 13, 2017, 7:48pm


	Reply From:	Cameron Kilgore

First off: This is not legal advice. I’ve danced around OSS matters in retail projects before, but I am not a lawyer. Don’t treat this as actual legal advice.

I’m not clear on the legal precedence in the US at least, but after the ProCD v. Zeidenberg ruling, a lot of US companies either included a shrink wrapped EULA or a paper notice indicating that the EULA license present with the software was legally binding once installed.

By that ruling, the clause in the MIT License that says “The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.” means you must include the license. It doesn’t mean you have to bundle the source code, but you must include Godot’s original license, even if you sublicense.

I believe that simply having LICENSE.md will be enough to address this for Godot. There are also other components subject to other licenses that aren’t necessarily bundled with a built Godot game such as FreeType, libopus, and ENet. I’m not sure how you should cover this but in many retail games, this is part of the End Credits or is part of the About/Extras screen.

The answer is: I don’t know. I’ve assumed based on the legal precedent set that it needs to be present and visible at least. To that end, i’ve already built a .tscn that throws all the know 2.1 licenses into TextAreas and paginates them (these are populated by hand). I have no qualms with making this scene available for public use, watch this space and i’ll gist it ASAP.

The questions about your legal obligations are best answered by a lawyer.

Having it on the assetlib could be useful for the community

eons | 2017-06-13 21:33

I agree with eons, having such resource on the assetlib would be great

Akien | 2017-06-16 08:38