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
Consider releasing under the AGPL instead of GPL #2607
Comments
No, not really. I understand the loophole though. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@JC5 Could you maybe leave this issue open and consider it in a relaxed minute? I think this small detail is important for Firefly III to ensure users freedoms and to avoid that the next random company grabs the code base, and makes a closed business out of it. With the GPL, they could do this no issue. |
The fact that the issue is closed doesn't mean I stopped thinking about it :) |
I'm not sure if GitHub alerts you but please check out the commits above my reply on GitHub :) |
Hey @JC5 Thanks very much for considering and already changing 😃 I am not a lawyer and I was not sure about license compatibility and the need to ask contributors for their approval to this license change but with A note on the copyright note. You now use:
I think it is more common (also suggested here in https://www.gnu.org/licenses/gpl-howto.en.html, section The copyright notice), that you list the years or give a range of releases. Considering your releases (I looked at git tags), this would be appropriate:
It also matches the majority of Firefly III more closely ;-) Also, some more hints:
|
Thanks for the suggestions, I’ll pick it up! |
Description
Currently the GPL is used which has the application service provider loophole.
Solution
Have you considered the AGPL?
https://en.wikipedia.org/wiki/Affero_General_Public_License
https://stackoverflow.com/questions/2127246/difference-between-affero-gpl-and-gplv3
The text was updated successfully, but these errors were encountered: