Skip to content
This repository was archived by the owner on Jan 6, 2022. It is now read-only.
This repository was archived by the owner on Jan 6, 2022. It is now read-only.

The license in use seems problematic for some groups of developers #10

@bbottema

Description

@bbottema

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:

GPL is difficult with Android development - the license requirement that any user can swap LGPL'd dependencies out is (apparently) incompatible with android app bundling. I'm no lawyer, but lawyers I've spoken to seem to think so. For what it's worth, the various fora on the internet do too. Here, for example, is a blog post explaining the issue (as far as I understand it)
https://xebia.com/blog/the-lgpl-on-android/ .

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):
image

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions