| 18 Jun 2024 |
 Jonas Chevalier | Access control mostly. The nix-community team would need to get access to the Equinix Metal account, that also hosts all of the Hydra builders, and that gives them access to the binary cache key. | 09:54:05 |
 @3650badcop:catgirl.cloud | In reply to @zimbatm:numtide.com
Yes, we should talk more about it because I think the community build boxes are really helping people debug things in nixpkgs. Imagine if you have a failed package on macOS but don't have a macOS box. Or if this is a very large build and you don't have a lot of compute or bandwidth available. let's go! community build boxes are fantastic!!! | 09:54:59 |
| @3650badcop:catgirl.cloud | sorry i get so excited seeing the success of foss projects | 09:55:16 |
 Gaétan Lepage | Having a beefy >24C/48T x86_64 builder would be the absolute dream. I personnaly fall back to my personal systems to build "heavy" packages (pytorch, JAX, their CUDA variants...) | 09:57:13 |
| Jonas Chevalier | In reply to @zimbatm:numtide.com
Access control mostly. The nix-community team would need to get access to the Equinix Metal account, that also hosts all of the Hydra builders, and that gives them access to the binary cache key. Actually correction: the real issue is that the aarch64 Equinix machine is also running ofborg, that is managed by the NixOS infra team. The mixed usage is actually what makes things complicated. | 10:05:31 |
| Jonas Chevalier | I would also love to see MIPS and other less common architectures in the mix | 10:06:36 |
| Jonas Chevalier | With 2k EUR we could also buy real hardware, and put it in a basement or something. | 10:08:12 |
