this post was submitted on 22 Aug 2024
48 points (98.0% liked)
Forgejo
137 readers
1 users here now
This is a community dedicated to Forgejo.
Useful links:
Rules:
- Posts must be relevant to Forgejo
- No NSFW content
- No hate speech, bigotry, etc
- Try to keep discussions on topic
- No spam of tools/companies/advertisements
- It’s ok to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You missed out this fairly important bit re go-git:
As far as being tied to git proper, that's because there is no drop-in alternative implementation that implements all the functionality that you need to run a Git server. Right now, Git proper is your only option. That might change as gitoxide matures, but that could take years.
Either way, even if they just stated that they just like the GPL, and want it to apply to their contributions towards federation and other improvements, I think that's a reasonable decision as long as their primary contributors agree with it too. I don't think a fork seems necessary unless the contributors want it to remain permissively licensed.
I did see that, I just didn't feel that it was relevant to my point
My point was that there could be (and the GPL even wants there to be). Also "Both Forgejo and Git must be used together" could be construed as Git itself requiring Forgejo, which isn't true either.
The fact that forgejo only calls an external git binary is what makes such tools compatible with non-GPL software as well... you just have to be able to substitute the binary for something else, it doesn't matter if that "something else" exists yet or not.
Maybe we just differ on our definitions of "requiring Git".