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.

  • @ulternoEnglish
    -1•20 days ago

    Or it could just be laziness.

    In case you don’t want to put the effort into making a system into your organisation, to update code in a public-facing versioning system hosted setup, just tell someone to zip whatever you compiled and package it along with the rest of the stuff.

    • Packaging the whole .git directory would make it significantly larger
    • This method is bankruptcy-safe, as compared to hosting on the internet.
      • Ideally, I would like there to be both, a zip (in case I don’t have an internet atm) and a link to the vcs
    • Yes, the companies mostly don’t care enough and people doing it won’t think of it as being hostile, just as putting the least effort.