-
Notifications
You must be signed in to change notification settings - Fork 105
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
Propose License Change to LGPL/MIT #118
Comments
Hi @tinxx I would prefer it to go to MIT, but I would need buy off from the contributors. If you can take the time to get everyone on board, I am happy to change. |
@coelner How would you feel about a license change? |
@finitespace you have my permission to do anything you want with my insignificant contribution. |
@finitespace You have my permission to change the license as you see fit. |
I support the change to a less restrictive license (LGPL or other). While GPL is in general a good thing, delivering a library under GPL is quite restrictive as it is not compatible with most of the other open source licenses libraries you might want/need to include in your project. |
@finitespace I do not have any objection to changing the licence to any other type. |
I'm all for it, sure; feel free to license my one-word contribution under any license you wish, now and in the future. ;) |
I'm OK! LGPL might be more suitable for a lib in some cases, so be it :) |
This is OK for me too. |
I think the LGPL would be preferable to the GPL, but I think MIT or similar would be even better for a library. But regardless, I consent to this change. |
@finitespace, I don't have a problem with that. |
So far (myself included)
|
Fine by me! 👍 |
I don't mind. Feel free to do whatever you need with the licensing issue
|
Fine with me. |
Either LGPL or MIT are good with me. |
Hey folks, I initially proposed LGPL as the new license because the original license was GPL. Now there are some unclear and missing statements from contributors that I would like to get cleared up. Unclear ContributorsI would like to ask the following contributors to clarify their decisions:
Do you support either MIT, LGPL, both or basically any license?
OK Contributors (LGPL + MIT)The following contributors gave their OK for both LGPL and MIT licenses (or any license):
Other Contributors
@johanso-au, @yanbec, please tell us if you are OK with a license change to MIT and/or LGPL license? Sorry for the inconvenience! |
All licenses are fine for me! |
I am OK with any license. |
I'm also OK with any license. |
LGPL or MIT are fine. |
All licenses are fine for me. |
Alright, it looks like we have a quorum! I am going to assume anyone who has not already spoke up has abandoned their account - so speak up now or forever hold your silence. For the remaining unspoken - I will take your silence as consent Would someone volunteer to create a new merge request @coelner @tinxx? I would personally like to change it to MIT. |
Hi @finitespace, I have created a PR changing all license annotations to Cheers! |
Hey @finitespace, any news? |
Thank you, @tinxx. That was an excellent pull request, are you looking for work? ;) A few minor comments, let me know your thoughts, Kind regards, and sorry for the delay, |
Hey @finitespace, Thank you for the warm response. I have pushed the amendments according to your comments. I hope this is to your satisfaction ;) You can always contact me privately with a job offer ;) Cheers! |
Bump! Please re-visit the Merge Request! Thanks! |
Hello,
First-off let me say thanks for the work you put into creating this library.
I was looking through the libraries I include in my current project and had to realize that this library would force me to release my code under GPL, too. I don't say that GPL is a bad licence, actually I believe the opposite.
Anyhow, I suggest a license change to LGPL to make it easier for people to integrate the library into projects licensed differently.
Cheers,
tinxx
The text was updated successfully, but these errors were encountered: