-
Notifications
You must be signed in to change notification settings - Fork 17
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
Consider standard Haskell license, or document the reasons for divergence #45
Comments
There was an earlier discussion about the license in dhall-lang/dhall-haskell#1248 (comment). HVR's relevant comments are dhall-lang/dhall-haskell#1248 (comment) and dhall-lang/dhall-haskell#1248 (comment). In the Dhall project we ended up maintaining some YAML conversion logic in two packages: I wonder how this can be achieved though if HVR doesn't agree to relicense the existing code. I suspect it would require an entire rewrite?! At 3019 LOC this should be feasible I guess. FWIW, I'm completely unfamiliar with the topic of license changes and any pitfalls that would need to be avoided. |
Maybe Herbert would be willing to relicense? Has he made a statement about this? |
In dhall-lang/dhall-haskell#1248 (comment) he said:
@hvr, could you possibly provide some context or reasons why you can't relicense this project? Any other advice on navigating this issue would also be welcome! :) |
I think Herbert is not following githib notifications. Email could be more lucky. It's a while I phoned him. I can try to remember to bring it up next time. |
HsYAML is particularly interesting to me, as it compiles with GHCJS, while the normal yaml does not. That would be useful in HLint, for a web version. However, I strive to avoid GPL dependencies where possible, since in my experience they reduce adoption and don't increase contributions. My current thought is to have an explicit GHSJS Cabal flag + preprocessor flag, and do a compile-time switch on YAML library. That's a bit grim, and I hate writing grim code for legal reasons.
If you would consider moving to the more usual Haskell licenses of BSD/MIT/Apache that would be great - but it's your code, so entirely your choice. If not, perhaps put in the README that the project is deliberately GPL (including the reason, if you feel comfortable sharing) so that people know not to ask?
The text was updated successfully, but these errors were encountered: