Blender moves from Phabricator to Gitea
11–20 of 58 posts
Re: Blender moves from Phabricator to Gitea
#12One note on Phabricator: "Effective June 1, 2021: Phabricator is no longer actively maintained"
Re: Blender moves from Phabricator to Gitea
#13I wonder how Gitea will hold up to all the traffic? Even Gitea hosts their stuff on Github.
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.
Re: Blender moves from Phabricator to Gitea
#14I wonder how Gitea will hold up to all the traffic? Even Gitea hosts their stuff on Github.
I don't believe Gitea is hosting on Github for traffic reasons but for feature completeness. Relevant issue is here[0]. [0] https://github.com/go-gitea/gitea/issues/1029
Re: Blender moves from Phabricator to Gitea
#15One note on Phabricator: "Effective June 1, 2021: Phabricator is no longer actively maintained"
Re: Blender moves from Phabricator to Gitea
#16I wonder how Gitea will hold up to all the traffic? Even Gitea hosts their stuff on Github.
Gitea does not use Github because the software can't handle their load requirements, but because they started using GH before Gitea had all the features they needed. They are actively working on hosting Gitea on Gitea, with the last piece being an importer to move over all their GH data. Blender seems to have been ok manually migrating some things and abandoning other things, since they weren't likely to ever get a P…
Edit: i misread the parent comment. My bad.
Re: Blender moves from Phabricator to Gitea
#17Earlier quoted context omitted.
That's not what parent means. Gitea is an alternative to GitHub, yet they use GitHub for hosting their code.
That kind of makes sense for disaster planning though. 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.
Re: Blender moves from Phabricator to Gitea
#18Earlier quoted context omitted.
I don't believe Gitea is hosting on Github for traffic reasons but for feature completeness. Relevant issue is here[0]. [0] https://github.com/go-gitea/gitea/issues/1029
That's a great ticket, & also links to a really nice & insightful comment from one of the Fog Creek folk https://lobste.rs/s/gokjbo/gitea_1_1_0_released#c_dg9pwe
Mercurial was pretty damn nice.
Re: Blender moves from Phabricator to Gitea
#19Earlier quoted context omitted.
That kind of makes sense for disaster planning though. If Gitea discovered some massive CVE, and volentarily went dark to fix it... They would want their code and fix hosted somewhere else.
Mirroring the code to github (or somewhere else) would solve that problem just as well. Not dogfooding your own product seems like a huge red flag to me.
Re: Blender moves from Phabricator to Gitea
#20I wonder whether this was part of discussion on the migrating within the Blender team or whether their migration just started before the Gitea org-change.
---
Off-topic but it's also funny that the Phabricator fork is Phorge & the Gitea fork is Forgejo...