-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choose a License #21
Comments
I think we need some strong copyleft license , maybe AGPLv3 , once our software run as a server. |
I noticed that the library python-gnupg (https://github.com/jeffhsta/python-gnupg), present in the requirements.txt is distributed over a GPLv3 license, what are our implications? |
@leormarqs I agree in use GPLv3. @ruanLN @mateusriad @Dkmister What do you guys think about it? |
I no disagree, Em qui, 4 de ago de 2016 às 10:58, Jeff Stachelski [email protected]
|
@leormarqs the implication is that whenever you distribute, bundle or otherwise provide that package, you'll have to guarantee the rights expressed in GPL3. It doesn't demand anything else from the project which is using that package. As for the license being discussed here, the OP is talking about Affero GPL and not GPL. If the software in question is being distributed over the network or as a service, then I'd recommend Affero. If it's meant for desktop local distribution, then regular GPL would be my choice. |
I think that AGPL is suitable with the project. I was not thinking in this until @DeSci said. The point is that we will have a more collaborative work between ourselves. |
In response of what @DeSci said GPL is deprecated https://opensource.org/licenses/gpl-license About AGPL I think is not our scenario, since we are building an app that we are sharing just the code and not the service it self. The ideia of this project is not create a provider. So my opinion is GPLv3 |
We can consult some availables licenses on http://choosealicense.com/licenses/
The text was updated successfully, but these errors were encountered: