You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GLWT license is released under the GLWT license, which means that anyone who wishes to use the license must abide by section 0 of the license, and make it untraceable to the original author. However, anybody could look up the license and trace it back, meaning that in using the license verbatim, you'd be violating the terms of the license.
The only "workaround" as of now is to sufficiently modify the license to the point where it's unrecognisable, however this effectively defeats the purpose of using this license as opposed to another or just writing one from scratch.
Could the license be released under another license, or a clause be implemented that excludes the license from being affected by itself? Alternatively, if the license isn't supposed to be released under itself, can the correct license be added to the repo?
The text was updated successfully, but these errors were encountered:
This is the exact reason why I've released this with GLWT license and I have no intention to spend my time discussing or change the license. Try to figure out how you can use it on your project. Or don't use it at all. I don't care. Good luck.
The GLWT license is released under the GLWT license, which means that anyone who wishes to use the license must abide by section 0 of the license, and make it untraceable to the original author. However, anybody could look up the license and trace it back, meaning that in using the license verbatim, you'd be violating the terms of the license.
The only "workaround" as of now is to sufficiently modify the license to the point where it's unrecognisable, however this effectively defeats the purpose of using this license as opposed to another or just writing one from scratch.
Could the license be released under another license, or a clause be implemented that excludes the license from being affected by itself? Alternatively, if the license isn't supposed to be released under itself, can the correct license be added to the repo?
The text was updated successfully, but these errors were encountered: