upvote
Replace a whole 24/7 team of devops people with myself?

As much as I'd like to believe that I'm worthy, I'm not.

reply
It's the devops team can manage a measly 87% uptime [1] you're talking about, you can do a lot better on your homeserver.

[1]: https://mrshu.github.io/github-statuses/

reply
If the primary forge's only job is to host the actual Git infrastructure (the code, the MRs, the issues, maybe a wiki), it's a lot more simple than GitHub, and probably more within the scope of what people can reasonably administer themselves.
reply
I hosted the first "java.apache.org". I was an early employee at CollabNet, and in the first discussions around starting subversion. I worked on Cloud Foundry.

This stuff isn't easy and I'm more than happy letting someone else do it at the expense of some downtime.

reply
24/7 devops team for a forgejo instance? Come on mate...
reply
24/7 devops team for github? Come on mate...
reply
Is running a small forgejo instance for a team the same as running GitHub?
reply
Will I have to patch machines, keep packages updated, deal with SSL certs, maintain action runner infra, deal with billing for the machines, add monitoring, alerts, logging, etc

No, I don't want to be in the business of running my own Github clone. That's what I pay Github for.

Why do you pay salary to employees to buy food when you can just run a farm next to the office and save money by operating the farm and giving the employees food directly? You'd save money by not having to pay as high of salaries, and farms don't even need 24/7 devops teams.

reply
Don't you think the farm example was a bit too extreme for it to make sense? A tech company probably does not have expertise in farming but devOps is something they already know how to do and can easily manage it in-house. Also how fast do you think farms produce food that you can drip feed it to employees constantly
reply
> solely to take advantage of its free CI, while that lasts

Eh, if you want to be able to continue working, deploy and what not as normal during weekdays, I'd suggest also moving to Forgejo Actions if you're moving anyways. Not 100% compatible, but more or less the same, and even paying the same but with dedicated hardware you'd get way faster runners.

reply
For companies with resources for infrastructure, sure.

For OSS, the unlimited free minutes of multiplatform CI offered by GitHub are literally impossible to replace. Maintaining runners yourself to do the same things would be somewhere between a part- and full-time job.

reply
> For OSS, the unlimited free minutes of multiplatform CI offered by GitHub are literally impossible to replace.

Yeah, how you think the ecosystem got by before GitHub even had actions? Y'all don't remember Travis CI et al anymore?

There are more CI services than what Microsoft offers the world, sometimes it's worth looking around a bit.

reply
> https://docs.codeberg.org/ci/

"Codeberg is a non-profit, community-led effort that provides services to free and open-source projects, such as Git hosting (using Forgejo), Pages, CI/CD and a Weblate instance."

Never say impossible.

Github is still "new" to a lot of us. OSS existed well before it, and will continue to exist well after.

reply
If Codeberg starts offering Mac and Windows runners alongside their Linux ones for free (or at an achievable price point) for a modest OSS project I'll certainly look at it very closely. If all I needed was a Linux runner, I'd probably be on there already.

And yes, if we make OSS just about hosting the code, things are much simpler. If you're a piece of desktop software though, and you have users, they'll typically (and reasonably) want auditable signed binaries on all the platforms you support, which requires multiplatform CI.

reply