I won’t ever write zig but respect to the maintainers for moving to codeberg and sticking to their principles. If the nixos foundation had any, they would move too (but I guess fighting in the forums is more fun than moving).
im not sure codeberg currently had the infrastructure to support day-to-day operation of nixpkgs development. I’m using codeberg daily for my own projects, and sometimes the diff for MR is broken or load for too long. Not mentioning stability issues.
Of course I wouldn’t complain of something thats maintained by volunteers. I’m just saying the traffic for nixpkgs are currently big and I’m pessimistic codeberg can handle it.
How are you going to handle issues, releases, artefacts, CI, pull requests, and so on. Please dont say mailing lists. That won’t make anybody but the minority of developers wet.
How are you going to handle issues, releases, artefacts, CI, pull requests, and so on. Please dont say mailing lists. That won’t make anybody but the minority of developers wet.
How are you going to handle issues, releases, artefacts, CI, pull requests, and so on. Please dont say mailing lists. That won’t make anybody but the minority of developers wet.
For git itself sure, but all the other things that come with a git forge, like issue management, are probably things that you don’t want spread out over multiple websites
I won’t ever write zig but respect to the maintainers for moving to codeberg and sticking to their principles. If the nixos foundation had any, they would move too (but I guess fighting in the forums is more fun than moving).
im not sure codeberg currently had the infrastructure to support day-to-day operation of nixpkgs development. I’m using codeberg daily for my own projects, and sometimes the diff for MR is broken or load for too long. Not mentioning stability issues.
Of course I wouldn’t complain of something thats maintained by volunteers. I’m just saying the traffic for nixpkgs are currently big and I’m pessimistic codeberg can handle it.
I feel like we should be treating git as more of a federated system. What rule is there against pushing to multiple remotes?
How are you going to handle issues, releases, artefacts, CI, pull requests, and so on. Please dont say mailing lists. That won’t make anybody but the minority of developers wet.
How are you going to handle issues, releases, artefacts, CI, pull requests, and so on. Please dont say mailing lists. That won’t make anybody but the minority of developers wet.
How are you going to handle issues, releases, artefacts, CI, pull requests, and so on. Please dont say mailing lists. That won’t make anybody but the minority of developers wet.
For git itself sure, but all the other things that come with a git forge, like issue management, are probably things that you don’t want spread out over multiple websites
We already have activitypub, and projects like Gitea are actively implementing it (at this time I don’t think it’s live enough yet)
deleted by creator