Consider not self-hosting this repo

[silverwind]

I can't comment on #1029 as it's locked even to maintainers, but I'd like to raise concern that self-hosting will be detrimental to future contributions.

I would prefer these efforts to be stopped. GitHub is a low barrier of entry for many people and by self-hosting, we are essentially raising the barrier of entry to contributions to a level that I think will considerably reduce contributions as well as discoverability of the project.

gitea.com is especially painful for western users because of its hosting location in China. For me it's just not fun to work on because of the ~250ms latency that the service has because of location. GitHub for comparison has 20ms latency for me, it's definitely more fun to work with.

[delvh]

Well, what we could of course do is a bidirectional way: We still allow PRs from GitHub, but mirror them (somehow, perhaps manually) to Gitea.
Would be a bit more work, but might include the best of both worlds.

---

However, I do agree that using gitea.com in Europe is really painful from time to time.

[lunny]

I think we can have a new architecture that all contributors of the world could visit it fast. That will resolve most of the problem.
Some people think I cannot believe you if you cannot host yourself.

[jolheiser]

The Go project itself also does something similar, albeit for different reasons.
They import PRs as patchsets into Gerrit for review, and once merged they close the PR and push the changes to the GH mirror.

Honestly I think something like the above would be a good feature regardless of the main repo, as I agree that GH has far better discoverability, it's nearly ubiquitous with "git".

---

A service to do a more complete sync would be beneficial to anyone who wants to keep their codebase on a server they control, but also leverage the discoverability of GH.

[delvh]

@jolheiser what you effectively propose is #2280.

[McSinyx]

For me it's just not fun to work on because of the ~250ms latency that the service has because of location. GitHub for comparison has 20ms latency for me

Maybe it's because I lived my entire life with shitty connection, but for web browsing anything under 1000 ms of latency for complete rendering can be consider good enough.

Moreover, by principle, most self-hosted instances (with single physical location) will suffer higher latency in the majority of the world, and submitting to that means the entire point of Gitea development is meaningless for the public Internet, and everyone should just use GitHub instead.

I think we can have a new architecture that all contributors of the world could visit it fast.

How far is Gitea federation away from production use?

[earl-warren]

A software forge that does not host its own development is not what I would expect, which is essentially what @lunny says: it is a matter of credibility. Running Gitea.com on a more powerful machine with better connectivity is very easy and cheap.

I would also like to highlight that the GitHub terms of service, which exclude people from certain countries, should not be mandatory for people who want to participate in the development of Gitea.

For these two reason alone I think it would not be a good idea to keep hosting Gitea on GitHub.