I wonder how Gitea will hold up to all the traffic? Even Gitea hosts their stuff on Github.
How many committees are there and how many people on each committee?
The reason to say it as a disclaimer is because we are going to have some bias.
https://docs.github.com/en/rest/migrations/orgs#start-an-org...
https://docs.github.com/en/rest/migrations/orgs#download-an-...
Using a Github App you get 15K requests per hour. Even with pagination(100 records per request) you should be able to get at all of this data within a couple of hours. I suspect you lack reliable transformation tools to take github metadata and convert it to gitea versus the limitations of GitHub.
Although as I have run the migration myself several times to attempt to debug issues, it takes over 24hours due to ratelimiting.
Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.
"Keep these ideas in mind when creating GitHub Apps:
- A user or organization can own up to 100 GitHub Apps."
Which is 1.5 million API requests per org per hour.
Mercurial was pretty damn nice.
Blender seems to have been ok manually migrating some things and abandoning other things, since they weren't likely to ever get a Phab->Gitea importer anyways.
Edit: i misread the parent comment. My bad.
Gitea performs alright. It can serve surprisingly-heavy traffic from a potato-tier VM with a SQLite backend (assuming the host network can keep up with it, anyway). Not Github-scale (but Github has... a lot of traffic, including a whole lot of write traffic) but quite a bit, and that's with basically the worst-possible hosting situation for handling high load.
Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.
If Gitea discovered some massive CVE, and volentarily went dark to fix it... They would want their code and fix hosted somewhere else.
Not dogfooding your own product seems like a huge red flag to me.
Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.
Github's scaling challenges have more to do with the write volume than the read volume. Even a project as big and active as Blender shouldn't make Gitea sweat too much on relatively modest hardware. Anonymous clones and such will surely be https, so, quite cache-friendly.
I wanna say Gitea has some config options for hosting static files (like releases) on s3-compatible storage then serving directly from there, so even that shouldn't be a problem. But I may be mis-remembering that part. And, again, a CDN or Varnish or whatever would be able to serve those files just as well from Gitea as from anywhere else.
If you are interested in some benchmarks that Blender did you can find them here: https://code.blender.org/2023/02/gitea-test-drive/
Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.