ENIGMA License it's ambigous
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I am requesting clarification about the GPL exception used in ENIGMA.
The ENIGMA license page states that ENIGMA is GPLv3-or-later and that a special exemption allows the commercial selling of software made with ENIGMA without releasing the game’s source code. However, the wording is ambiguous. It is not clear whether the exported game is completely exempt from the GPL, or if only the viral clause of the GPL is removed.
I need to know whether the GPL applies in any form to the compiled game. Specifically:
Does the GPL apply only to ENIGMA itself, and not to the exported game at all?
Or does the GPL still apply to the exported game, but without the viral requirement to release the game’s source code?
In other words, is the exception removing the entire GPL from the final game, or only removing the copyleft propagation?
The license page says that you can sell software made with ENIGMA without releasing the source code, but it does not explicitly state whether the exported game is considered independent from ENIGMA for all GPL purposes.
I am requesting clarification on whether the exported game is fully outside the scope of the GPL, or if any part of the GPL still applies.
Additionally, I need to know whether the exported game must keep GPL copyright notices or include the GPL license text when distributed. If the GPL does not apply to the exported game at all, then no notices or license text should be required. If the GPL applies in any limited form, then I need to know exactly which obligations remain, including whether the distribution must include copyright notices or the full GPL license text.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the ENIGMA license page and the GPLv3-or-later exception wording. Determine whether the exported game remains subject to any GPL obligations, including copyright notices and license text, then update the license documentation to state the exact distribution requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100