cross-posted from: https://lemmy.ndlug.org/post/1019007
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.
I have a lot of respect for this project. I lurk on the discussion forum and issues and I’ve always seen mature discussion even though the project was born out of issues which could have been quite emotive.
It’s also a lot nicer to run than any other git forge that I’ve had experience with.
Is it still a drop in replacement for gitea, I’ve been meaning to switch
I switched last week and changing the image from gitea to forgjo just worked.
Given that I recently read the intro on Codeberg (which I think is the main public Forgejo instance) and it was very pro-copyleft, I’m surprised this wasn’t already the case! Good news, though.
The problem is that some people are “so copyleft”… that they fall into the MIT honeytrap.
I don’t quite understand what you meant. Can you expand?
Nice.
Does Forgejo support Git? I’m not familiar with Forgejo, and it’s not obvious in this announcement or their homepage.Forgejo does support Git, I didn’t read carefully enough.
Nice!
