-
Notifications
You must be signed in to change notification settings - Fork 28
The license in use seems problematic for some groups of developers #10
Comments
Hi @toKrause, have you had some time to think about this? |
Hi, I'm not a lawyer and I really don't enjoy having to deal with license stuff. In the hope of making things easier for me and having less trouble in the future, I've changed the license to LGPL, so that this library and my S/MIME library would have the same license. Apparently I've made the wring call. I'm not sure if i can repair the "damage", but I'm going to look into. |
@toKrause, any update here? If you want I can provide a pull-request that switches the license file (with Apache v2). I think that is all that is needed if I'm not mistaken. |
@toKrause? Sorry for pestering you, but this should be a quick fix. Is there anything specific holding you back? Can I help? |
Nothing specific. I just have a lot going on in my life, so I have little time left to manage this project. I just released a new version under the original license. |
Understandable and thank you so much for changing the licence! |
Thanks for your patience. The new version number will be 1.1.12. It usually takes a few hours for new releases to be visible in Maven Central. |
Hi @toKrause,
Is there a specific reason for using the (L)GPL licence and are you open to changing it perhaps? Here's a problem we are running into with this:
Because of this, I noticed users forking Simple Java Mail only to remove all code regarding the DKIM library to avoid Copyleft issues.
Also, here's a SO answer giving some insight into the reasoning behind LGPL and Oracle's variation "GPL with classpath exception". One thing that immediately stands out is that (L)GPL was originally written for C/C++ applications.
If you compare LGPL with Apache v2, there is a lot of overlap (Apache V2 on the left):
The repo you forked from also used Apache v2, so I guess you had a specific reason for switching the L(GPL). Any thoughts on all this are very welcome.
The text was updated successfully, but these errors were encountered: