django-admin-autocomplete-filter

django-admin-autocomplete-filter copied to clipboard

Any info on the LICENSE being GPL/LGPL?

Related: #7

I can't use LGPL / GPL with django on my projects, sorry about that, as it's out of my control. It's probably the same for many others.

I can use ISC/MIT/BSD/Apache.

The license is GPL3. Note that there's a distinct difference between the GPL and the AGPL. Typically companies that are fearful of using the GPL base this on an assumption that mere use of GPL code means that their code must be re-licensed under the GPL. This is not the case. Unless you're distributing your code (for example, installing it on a laptop for local use) you don't have to re-license the rest of your codebase.

I don't see what AGPL being different GPL has to do with it? I can't use the package since it has viral clauses, and just wanted to leave a note because others probably have the same issue.

I contribute to GPL projects, I'm not saying GPL is good or bad. I'm talking about what I can and cannot incorporate into my projects due to factors outside my control.

Regardless of it being AGPL, GPL, or LGPL, v2 or v3, there are complex implications in these licenses. They weren't created with scripting languages in mind, let alone django packages.

I ended up looking elsewhere, but I'd try this project if it were the same license as Django or similar.

@danielquinn but setup.py still contains LGPLv3...

The license is GPL3. Note that there's a distinct difference between the GPL and the AGPL. Typically companies that are fearful of using the GPL base this on an assumption that mere use of GPL code means that their code must be re-licensed under the GPL. This is not the case. Unless you're distributing your code (for example, installing it on a laptop for local use) you don't have to re-license the rest of your codebase.

Two points:

1. Whether your assertion is accurate or not is irrelevant for all the companies that will not allow the usage of GPL3 code.

2. IANAL, but I don't think the confidence of your assertion is warranted. GPL3 requires an "arms-length" separation between the client (in this case browser code), and the server (in this case Django code). It's not completely clear what this arms length distinction entails, but there are plausible and not-court-tested arguments that this separation is not "arms-length-enough".

I must no use GPL software. Thus I must not use this software and I won't provide improvements and bug fixes.

Here there is setup.py (and #7 ?) which states LGPL-3 while LICENCE states GPL-3.

Which one is the right one?

So, what is the license? GPLv3 or LGPLv3?

I concur. This package will be used a lot more if it used BSD 3 like Django (or any other permissive FOSS license for that matter).

Here there is setup.py (and #7 ?) which states LGPL-3 while LICENCE states GPL-3.

Which one is the right one?

@farhan0581 there still a discrepancy between the licenses, are you ok with a PR fixing this?