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.

you are viewing a single comment's thread
view the rest of the comments

[–] lambda@programming.dev 15 points 4 months ago (1 children)

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 points 4 months ago (1 children)

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

[–] Opisek@lemmy.world 2 points 4 months ago (1 children)

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 points 4 months ago

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