this post was submitted on 27 Nov 2025
204 points (99.5% liked)
Programming
23621 readers
134 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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?
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)
Sure, but my point is that you'll end up with one "main" remote where you have all git forge stuff even if you push to multiple remotes. By all means, don't make github the main one!
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.