-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Update license to MIT. #659
Conversation
We still need a few approvals, right ? |
Yes, just preparing the PR ahead of time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved by all contributors: #623
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to change the license in composer.json as well.
should we merge this in 1.x as well, so that both maintained branch are under the same license ? this would simplify the maintenance, as we would not need to accept LGPL contributions to 1.X and then asking contributors to accept moving them to MIT when applying the same fix in 2.0. |
Yes |
Update license to MIT. Conflicts: composer.json
Fixes #623