[ahacker15]

We can for sure understand that one is not available all time. Everyone has a life, and sometimes need many weeks away, etc.

This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going.

Before the first time he went AFK, he even removed write access from the 2 or 3 other people that had it.

[sangnoir]

> This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going

Others don't need write access "to keep the project going" unless they intend to ship releases without him/her- they can make PRs and the maintainer will merge them when they are back. Perhaps the Gitea committers want a more predictable release cadence?

I agree that a fork is probably the best solution here, due to the impedance mismatch, the forkers don't seem to be fans of the BDFL model. Additionally, "community" is a much wider term than how you used it, it's not just other contributors but also includes users and bug reporters. I wish Gitea the best of luck, but I'll remain a Gogs user.