Releasing Project Source Code Under MPL 2.0
I have a C++ Project that is generic in nature with "innovative" combination of unreal UI and Character Controllers that drives motivation of releasing it publicly under MPL 2.0 if it is possible at all. C++ project started as blank project, without any starter content, after much googling I still don't have clear picture on how to do it right.
It seems like Unreal EULA does not prohibit releasing my own code (references to Unreal classes, methods, class extensions/inheritance, function calls etc ...) on public repository with all required project folders such as Config, Content, Source, Plugins.
Is it acceptable to add MPL 2.0 license notice header to each project source file ?
Project Source File Example:
Do I need to add anything else to license notice header or any where else in project to make it happen ?
Hi there. It sounds like you are asking for advice on how to release your project under MPL 2.0. Unfortunately, Epic is isn't permitted to provide you legal advice like this. Please note that distribution of engine source is limited under the EULA and must be to other UE4 licensees through a fork of Epic's git only.
answered Feb 19 '19 at 06:08 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here