- cross-posted to:
- opensource@programming.dev
- cross-posted to:
- opensource@programming.dev
Forgejo is changing its license to a Copyleft license. This blog post will try to bring clarity about the impact to you, explain the motivation behind this change and answer some questions you might have.
…
Developers who choose to publish their work under a copyleft license are excluded from participating in software that is published under a permissive license. That is at the opposite of the core values of the Forgejo project and in June 2023 it was decided to also accept copylefted contributions. A year later, in August 2024, the first pull request to take advantage of this opportunity was proposed and merged.
…
Forgejo versions starting from v9.0 are now released under the GPL v3+ and earlier Forgejo versions, including v8.0 and v7.0 patch releases remain under the MIT license.
AGPLv3 is not anti-business or anti-money. It’s saying if you want to use the code in a closed source project you need to pay the copyright holder
The copyright holder is the original author, not a maintainer or someone who forked a project and renamed it.
That’s why the #1 thing mentioned in copyleft licenses is you can’t alter the copyright notice and declare yourself the original author
AGPLv3 is a good license to choose. All the other licenses are naive and do not combat closed source projects and the slave worker that keeps our projects unfunded