Skip to content
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.

AGPL licence warning? #4

Closed
andybak opened this issue Mar 21, 2020 · 1 comment
Closed

AGPL licence warning? #4

andybak opened this issue Mar 21, 2020 · 1 comment
Labels
question Further information is requested

Comments

@andybak
Copy link

andybak commented Mar 21, 2020

Unless I'm mistaken any project that uses this will also be under the AGPL - which is a pretty major fact for anyone using it to be aware of.

I nearly overlooked this as it's fairly unusual in Django world. It would have been very problematic as the rest of my code is MIT licensed.

Considering this is fairly out of the ordinary - would it be a good idea to put a much clearer warning higher up in the readme? Not everyone is a licence lawyer and many people will just think "oh cool. open source"

@kmmbvnr
Copy link
Collaborator

kmmbvnr commented Mar 23, 2020

Yep, the Readme file contains the section regarding the license. If you are using standard CPython distribution under common Linux distributive, you are already have components with APGL+Exceptions that allows linking but prevents selling modified libraries without code distribution.

@kmmbvnr kmmbvnr closed this as completed Mar 23, 2020
@kmmbvnr kmmbvnr added the question Further information is requested label Mar 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants