-
Notifications
You must be signed in to change notification settings - Fork 3
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 a different license #3
Comments
Thank you for your interest and kind words. I want to make sure this software and derivative works are free to be studied by anyone. Respectfully, there is a good reason for choosing to license primarily under GPL and not any other license. |
hey @wykwit, that's totally fair, but are you aware that the GPL license essentially restricts it to only be used in projects that also use the GPL license? I would love to use this on an MIT licensed project, but just cannot due to your library being GPL licensed. You're right that it is technically possible that if you license with MIT that your library would be used in projects that do not share their code, but the real risk there and why GPL is a thing is your code itself being further developed and your hard work being used to make money off of. With due respect given the scope of this library that doesn't seem much of a risk as it is a doing one very specific thing, there's not much room for growth in the library itself, and its functionality can easily be replicated with other tooling, so it's not enabling anyone to make money off of your hard work. The value it has to me, and the reason I am trying to respectfully convince you to relax its license, is that it allows developers to consolidate their technologies and improve maintainability of their codebase. Right now we are using OLE to provide the same functionality, which works but isn't ideal. Appreciate your time and consideration, I won't press any further, just want to make sure you understand the limitations GPL is imposing on your code. |
Hi there,
Really appreciate the work you did here, this looks amazing considering all other solutions right now are either use powershell/vbs or use OLE, either of which have significant issues.
Sadly we can't use it due to the license though. Would you consider instead licensing under MIT or something more permissive? I appreciate the GPL-3 license, but it doesn't seem to make much sense for a library like this. Not like someone could make product entirely based on this library, so exploitation seems unlikely, and other licenses can still provide you with credit.
Appreciate your time and consideration, thank you!
The text was updated successfully, but these errors were encountered: