In 4006bbc1bb17557654781e87ac7917ef770e0ac4 the LICENSE file was changed so now it seems to be AGPL instead of Apache. However setup.py still says "Apache" which seems to be an oversight as the readme says "license change. Please contact us for alternative licenses" as a "major change" in 3.0.
This is especially bad because PyPI will display the license as "Apache Software License (Apache)" - I guess is parsed from metadata generated from setup.py. (Besides from an armchair-lawyer perspective I'm not sure if the license change to AGPL was really in effect since the "LICENSE" file is never referenced by the code and there is a conflicting information given more prominently by setup.py.)
Also I think the readme should feature the AGPL more prominently as this is an important thing to know about the license. Right now the license is never referenced in the code so it is pretty easy to overlook. I came to like the short SPDX identifiers like they are using in the Linux kernel. Maybe you could add these as well to make users more aware of the license.
In 4006bbc1bb17557654781e87ac7917ef770e0ac4 the LICENSE file was changed so now it seems to be AGPL instead of Apache. However setup.py still says "Apache" which seems to be an oversight as the readme says "license change. Please contact us for alternative licenses" as a "major change" in 3.0.
This is especially bad because PyPI will display the license as "Apache Software License (Apache)" - I guess is parsed from metadata generated from setup.py. (Besides from an armchair-lawyer perspective I'm not sure if the license change to AGPL was really in effect since the "LICENSE" file is never referenced by the code and there is a conflicting information given more prominently by setup.py.)
Also I think the readme should feature the AGPL more prominently as this is an important thing to know about the license. Right now the license is never referenced in the code so it is pretty easy to overlook. I came to like the short SPDX identifiers like they are using in the Linux kernel. Maybe you could add these as well to make users more aware of the license.