@zkat @xyhhx @janl @anildash Right, and that makes sense. Solving this would be an astronomical problem because the only solution we’ve really figured out before is “infinity dollars from magic money” shaped. Or closed compute under a nonprofit funding structure.
Getting the latter setup is not trivial and many projects simply can’t afford it. Which sucks, but I don’t think a straightforward solution exists
@hazelweakly @xyhhx @janl @anildash I mean.
You can just pay for things.
I'm ok paying for things.
Tons of open source devs can scrape together a few greenbacks to pay for CI.
I think it's important to renormalize paying for shit that's worth money, rather than expecting everything to be free. lol
@zkat @xyhhx @janl @anildash Oh for sure, I’m not against that at all. Things should cost money and magic externalities don’t work.
But I don’t think a lot of projects are prepared for the sticker shock of finding out how much their free GitHub CI compute costs. Also much of our CI and build systems infrastructure over the last decade have optimized for stateless computational waste because it was all free. Fixing that isn’t trivial and the ripple effects might be fairly large. We’ll see!
But yes, I’m okay with paying for things. I just think a lot of people are gonna have sticker shock when they see the price tag of that :)
@anildash the "at scale" part is the problem. people got spoiled with github marketplace (which, frankly, is a supply chain security nightmare)
m gonna say it again: people can run their own runners on a community instance for like <$10/mo - or hell, use sourcehut at $2/mo. the vast majority of what people are doing can be achieved with a few shell scripts
@zkat you can have org-wide or project-wide runners as well for those too. setting up a runner is exceedingly easy, honestly
and even codeberg's instance runners are enough more often than not
the real thing forgejo lacks imo is job summaries. you could probably try to work around this with a bot account but then you really start broaching on "you should consider hosting your own instance"
@anildash I've been thinking of moving over to Codeberg for my personal projects. At work we're a bit entrenched in the Github CI system (as I'm sure was their plan all along) so it'll be ... a bigger project.
I saw somebody else mention Fossil, and it's certainly crossed my field of vision before. It looks kinda rad, and I also might just get weird with it and try using that because while git gets the job done it's ... so very very git.
@anildash I really hoped that the federated code collaboration stuff GitTea / @forgejo have been working on for years would be more widespread by now. Or even the Nostr stuff so we wouldn't need to tie identity to servers. https://nostrgit.org/
I'm personally working on migrating to https://radicle.xyz/
@anildash Can you elaborate on
> “pull requests” are not actually an open standard and throwing code over the wall at others is not actually social coding
given `git am`? I know you know this stuff, but I don't follow. Is there a meaningful difference between pull requests and sending git patches to mailing lists?
@anildash but there are plenty of decentralized communities with semiprivate @gitea instances…that’s what I mostly utilize. I’ve also heard of “fossil” but haven’t researched too much into it.
https://dev.to/schollz/self-hosting-with-fossil-an-alternative-to-git-33bk
@anildash Git doesn't need Github.
If you want something to share code outside your circle of trust, Codeberg and Forgejo are places to start.
At this point, it is time to start self- hosting IP and not give your stuff away to sketchy corporations that have PROVEN themselves untrustworthy.
git as it was intended, no need for a huge code forge to push everything through. Use email to share patches around. The tools still exist to have a good, decentralized experience.