We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is GPL-3.0 appropriate? I've seen people want to link this to decomps, and those aren't GPL-3.0.
By including this and linking it into any source decompilation project or binary ROM hack it would have some pretty severe implications.
Have you considered dual licensing this under MIT or zlib? It's effectively unusable in serious projects in this state, AFAIK. IANAL.
AFAIK there are no FOSS, clean-room reimplementations of sappy.
The text was updated successfully, but these errors were encountered:
Huh, that's kind of true actually. @easyaspi314 Would you be fine with changing the license?
Sorry, something went wrong.
I'm currently considering the following: Either MIT or MPL 2.0, what would be the preferred option for you?
MIT is well vetted and seems the best to me
No branches or pull requests
Is GPL-3.0 appropriate? I've seen people want to link this to decomps, and those aren't GPL-3.0.
By including this and linking it into any source decompilation project or binary ROM hack it would have some pretty severe implications.
Have you considered dual licensing this under MIT or zlib? It's effectively unusable in serious projects in this state, AFAIK. IANAL.
AFAIK there are no FOSS, clean-room reimplementations of sappy.
The text was updated successfully, but these errors were encountered: