Hot take: @nixos_org should move to @Codeberg
@britter not even a hot take, the current dependency on US infrastructure is a liability
@nixos_org @Codeberg @britter even GitHub has & had scaling issues with the size of nixpkgs and codebergs CI infra is regularly overwhelmed with the existing load.
I say this as both a codeberg e.V member and as someone strongly agreeing that nixpkgs should move away from GitHub. I just think a dedicated instance might be a better idea, to have it scale (or not) on its own without straining shared resources to much
@nixos_org @Codeberg @phaer forgejo.nix.org! Love the idea!
@britter
Now we just need the funds & the labor :-P Not just for running it, but also for a giant migration and possibly for patching forgejo & act to handle the size :-P
@phaer I would be happy to work on it. The funds are a different problem 😅
Wonder if @nixos_org could evolve into a non-profit with member fees lke @Codeberg where being a paying member grants you some influence.
@nixos_org @Codeberg @msgilligan being dependent on US infrastructure has become a liability in recent times 🤷♂️
@britter @nixos_org @Codeberg I understand. In general it’s good to not be too dependent on a big, centralized infrastructure provider. Codeberg and Forgejo are both cool. Are there any examples of smaller Nix projects with significant CI infrastructure using Forgejo?
@nixos_org @Codeberg @msgilligan my impression is that some individuals from the nix community are moving to Codeberg but none of the major projects has thus far.
Some non-nix projects:
- https://codeberg.org/ziglang
- https://codeberg.org/librewolf