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.

  • solrize@lemmy.world
    21·
    3 months ago

    Forgejo appears to be a self hostable code sharing web platform like gitea or GitHub. I’ve used gitea for this. Is Forgejo better or what? There is also Gitlab which is way bloated.

    • λλλ@programming.dev
      14·
      3 months ago

      Its a fork of gitea. It formed when gitea did something that the community didn’t like. I don’t remember the reasoning. But, I remember someone sending me a bunch of info about it in the past and it was enough for me to switch.

      • solrize@lemmy.world
        5·
        3 months ago

        Thanks, I didn’t know about that. Gitea itself is a fork of Gogs though. Wheel of karma?

        • Opisek@lemmy.world
          1·
          3 months ago

          You can actually (for now) just replace gitea with forgejo while keeping all the files in place and it just works. Really easy then using docker, cause all it takes is changing the container image.

          • solrize@lemmy.world
            1·
            3 months ago

            Thanks. I’ve run gitea without docker and it was fine. I’ll have to figure out docker someday though.