Skip to content
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

A more stable "LICENSE" #8

Open
cwebber opened this issue Aug 20, 2018 · 1 comment
Open

A more stable "LICENSE" #8

cwebber opened this issue Aug 20, 2018 · 1 comment

Comments

@cwebber
Copy link
Contributor

cwebber commented Aug 20, 2018

Oh here comes another annoying bug from @cwebber! I'm only filing these because I care ;)

The current LICENSE file is probably FOSS, but it's a bit goofy... it depends on a time-based relationship to whatever Racket's license is as at http://download.racket-lang.org/license.html

On the one hand, I appreciate this is a clever hack: Racket's license is changing soon, and this allows you to flow with when and where that decision / change has been made. However, I may be looking to get Lux pushed up to GNU/Linux distros such as Debian and Guix soon, and those places care more about what specific license choice has been made.

ISTM that Lux should simply choose one of the licenses on the table for Racket: LGPLv3+, as it is currently, or Expat or Apache v2... probably one of the latter two, since that's where Racket is going to go. Expat has the advantage of being popular and minimal, but Apache V2 has the advantage of having some patent mutually-assured-destruction features. You could dual license between the latter two as Racket looks like it will, though that might provide a loophole for the patent mutually assured destruction clause.

@cwebber
Copy link
Contributor Author

cwebber commented Aug 20, 2018

You have a few other Lux-related repos doing the same... I'd advocate that once you make a decision that you update all of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant