Email or username:

Password:

Forgot your password?
bouncepaw 🍄

Still thinking about how they named it Forgejo, and not Forĝejo, just to confuse everyone.

3 comments

@bouncepaw If we had named it Forĝejo everyone would have called it Forgejo anyways, just like a lot of people call GitHub "Github".

I'm not a fan of the name (we already have ForgeFed, Forgefriends, ForgeFlux...) but at the end of the day, it doesn't really matter. Once Forgejo finally gets federation support, people are going to use it no matter what its name is.

bouncepaw 🍄

@a Will the original Gitea get federation though? I suppose you are not working on Gitea anymore? But will they join afterwards?


@bouncepaw I'm not sure. I'm indeed not working on Gitea anymore, but I also did not intentionally make it difficult for Gitea to use my code.

For instance, the federation code is still licensed as MIT instead of switching to AGPL, and Forgejo is currently almost the exact same codebase, so it shouldn't be hard to port the federation code to Gitea.

Basically, whether Gitea gets federation depends on whether Gitea Ltd does anything dumb and if Gitea wants federation support.

Go Up