License and copyright considerations

[trigger-segfault]

TODO

• Determine the -best license to use for the project.
• Determine how to handle the copyright note present in Gods98 source files.

Considerations

MIT pros

• For other LRR fan projects, MIT would make it easier to reference decompiled code/behavior for use in their own game.

GPL pros

• GPL will open up more external frameworks that are placed under less permissive copyleft licenses.

[trigger-segfault]

Going forward, I think the best course of action is to use the following:

• GPL-3.0 for the project exterior, code that handles OpenLRR-specific functionality.

• MIT for all researched / decompiled LRR core game code. The internals of the game must always remain publicly available without any need to consider the consequences of its usage.

The goal is to open up more opportunities to use existing code and libraries to help OpenLRR advance. GPL restrictions would be placed on the code designed to run OpenLRR the project, but not LRR the core game. In practice, this may not be as simple as it sounds (especially when modifying the LRR engine code), issues can be addressed if/when it gets to that point.

If at some point, a game module must become dependent on GPL licensed code, then the module must first be fully decompiled and made available as MIT before the transition. This can be done by creating a new branch tag describing that final point for the particular module.