Bob Proulx <b...@proulx.com> writes:
> I understand your reasoning. And if this were an infrastructure at, > say, Amazon AWS EC2, setup to be elastic and just scaled out then your > reasoning would be totally on target. Increased load would scale out > to more parallel resources. It is more typical to have a load > balancer in front of http/https protocol servers and so those can be > set up rather straight forward. And also load balancers could be set > up in front of git:// protocol server too. > > However the GNU Project is dedicated and directed to using only Free > Software. And is hosted in this goal by the FSF. Which means > everything is self-hosted. Funded by the annual fund raising from > donors just like all of us who donate funding. And resources are > limited. I want to just chime in and say that from my perspective, limited resources is the biggest issue. Please don't clone emacs from Savannah as part of an automated process that runs regularly. Setup a mirror or multiple mirrors that get incremental updates. Cloning emacs over and over leaves less room on our network for other uses. When you hit a rate limit, there's a decent chance it is degrading other people's use of the network too, and even if you stay within the limits it may cause us to have to make our limits lower and again affect other people. We do self host, running hardware similar to https://ryf.fsf.org/, and get bandwidth donated https://www.gnu.org/thankgnus/2020supporters.html#equipmentservices. That page will soon mention https://vikings.net/, as they run a machine for us and we will use for a few things like mirroring. We avoid many cost free resources that other software projects use due to our ethics. -- Ian Kelling | Senior Systems Administrator, Free Software Foundation GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF https://fsf.org | https://gnu.org
