RE: https://techhub.social/@ironicbadger/116301246624014978

I feel this, but I also fear 100s, 1000s, and 10ks of self-hosted servers with different rules and nuances just to figure out how to post an issue or fork a project, and I fear we are going to leave new contributors even further behind.

I struggle to say, let's all hop to https://codeberg.org or another platform, since that probably kicks the can down the road until it's too big and fights the same fight.

I host my own private Forgejo instance and I mirror some projects, and while it's free to use, it's not free to run/self-host and run at any scale. I thought it was a pain to set up (hello SSH keys with their Docker quickstart).

Overall, I think action over inaction is good, but let's be realistic about what a good newbie experience is, but that's the group we are going to pass our projects over to once the time has come. I just hope that's not a bill that only grows.

@webology I, too, run my own Forgejo instance, though I set it up manually rather than via docker.

I think the reality is that not all developers are sysadmins and vice versa, despite the "devops" claims.

I would personally favour, for projects/orgs that are large enough, separate people to handle infrastructure from the core dev team. Perhaps we need an OpenSysAdmin group that provide services to lots of smaller projects? I'm probably overthinking this, as usual.

@calum @webology the vast majority of packages, even critical one, run on 2h/month hobby time of a single person, shared between multiple projects.

Self hosting doesn't make sense