New issue
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
License is proprietary - but most of it looks like BSD-3-Clause #3
Comments
I used the Haskell stack tool to generate this project, including its LICENSE. But I agree that the BSD 3-clause license would be a better choice, thanks. Fixed in e0970c0. |
Started a discussion about this on the Haskell Discourse. |
@glyn thanks a lot and your initiative already nicely teleported the information into places close to fixes: haskell/cabal#9812 |
@sthagen Looks like the stack templates are being fixed (which is what I used), as well as |
@sthagen I doubled back and checked. The Haskell stack tool has been updated and now generates the correct BSD license. |
@glyn thanks a lot for propagating the change into the wider ecosystem and following up. Much appreciated! |
I came here from an email of yours to the IETF jsonpath mailing list advertising the repository.
So, from the side lines - hopefully welcome feedback and not perceived as intrusive - a comment on the license:
I noticed the license was not detected as per an SPDX code and reading the license confused me.
Most of the license looks like BSD-3-Clause, but with four modifications:
copyright holder
has been replaced with the name of the copyright holder → no impact on license, but will trigger detection problems (as with GitHub not detecting BSD-3-Clause)COPYRIGHT HOLDER
has been replaced withCOPYRIGHT OWNER
. → I am no lawyer, but the introduction of such a variation (holder to owner) does not help assessing compliance when sharing.So, in case this is the license you want, all is good, and please close this issue as resolved.
In case the BSD-3-Clause license was intended, I suggest to instead use the following text:
The text was updated successfully, but these errors were encountered: