Closed siwinski closed 5 years ago
The README file also references the "SIL license" twice in its' description. Is this repo licensed under a third license as well?
per this question: Did Red Hat legal review and approve both the licensing of this package and the format of the license file?
Yes. I did send them this PR though.
@starryeyez024 @siwinski This should be closed in favor of the in-progress #7 - the main difference is that this keeps the OFL|LGPL dual license (even though @siwinski rightly found that peculiar) and @davelab6 is right that, at least since we're trying to fix this up anyway, we shouldn't have an LGPL license option because it's just confusing at best and no real-world user will benefit from such an option.
Closing per last comment. Thanks @richardfontana !
Thanks!
I am not a lawyer or a member of Red Hat's legal team, but I noticed that the license information in this package is off. This pull request is an attempt to help clean that up based on my knowledge of other open source packages.
Changes:
OFL.md
toLICENSE.md
because this package is dual-licensed (not just OFL) and this is the standard license file name to usepackage.json
license valueQuestions I still have about this package:
@starryeyez024 @rethomps @castastrophe