▲ 209 ▼ Zig: Migrating from GitHub to Codeberg (ziglang.org) submitted 9 months ago by rwnobrega@lemmy.world to c/programming@programming.dev 34 comments fedilink hide all child comments
[–] onlinepersona@programming.dev 16 points 9 months ago (2 children) 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). permalink fedilink source hideshow 4 child comments replies: [–] danhab99@programming.dev 1 point 9 months ago (5 children) I feel like we should be treating git as more of a federated system. What rule is there against pushing to multiple remotes? permalink fedilink source parent hideshow 10 child comments replies: [–] zygo_histo_morpheus@programming.dev 5 points 9 months ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] danhab99@programming.dev 1 point 9 months ago (1 child) We already have activitypub, and projects like Gitea are actively implementing it (at this time I don't think it's live enough yet) permalink fedilink source parent hideshow 2 child comments replies: [–] zygo_histo_morpheus@programming.dev 1 point 9 months ago 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! permalink fedilink source parent [+] onlinepersona@programming.dev 0 points 9 months ago [removed by mod] permalink fedilink source parent [+] onlinepersona@programming.dev 0 points 9 months ago [removed by mod] permalink fedilink source parent [+] zygo_histo_morpheus@programming.dev 0 points 9 months ago [deleted] permalink fedilink source parent [–] onlinepersona@programming.dev 0 points 9 months ago 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. permalink fedilink source parent [–] tengkuizdihar@programming.dev 1 point 9 months ago 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. permalink fedilink source parent
[–] danhab99@programming.dev 1 point 9 months ago (5 children) I feel like we should be treating git as more of a federated system. What rule is there against pushing to multiple remotes? permalink fedilink source parent hideshow 10 child comments replies: [–] zygo_histo_morpheus@programming.dev 5 points 9 months ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] danhab99@programming.dev 1 point 9 months ago (1 child) We already have activitypub, and projects like Gitea are actively implementing it (at this time I don't think it's live enough yet) permalink fedilink source parent hideshow 2 child comments replies: [–] zygo_histo_morpheus@programming.dev 1 point 9 months ago 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! permalink fedilink source parent [+] onlinepersona@programming.dev 0 points 9 months ago [removed by mod] permalink fedilink source parent [+] onlinepersona@programming.dev 0 points 9 months ago [removed by mod] permalink fedilink source parent [+] zygo_histo_morpheus@programming.dev 0 points 9 months ago [deleted] permalink fedilink source parent [–] onlinepersona@programming.dev 0 points 9 months ago 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. permalink fedilink source parent
[–] zygo_histo_morpheus@programming.dev 5 points 9 months ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] danhab99@programming.dev 1 point 9 months ago (1 child) We already have activitypub, and projects like Gitea are actively implementing it (at this time I don't think it's live enough yet) permalink fedilink source parent hideshow 2 child comments replies: [–] zygo_histo_morpheus@programming.dev 1 point 9 months ago 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! permalink fedilink source parent
[–] danhab99@programming.dev 1 point 9 months ago (1 child) We already have activitypub, and projects like Gitea are actively implementing it (at this time I don't think it's live enough yet) permalink fedilink source parent hideshow 2 child comments replies: [–] zygo_histo_morpheus@programming.dev 1 point 9 months ago 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! permalink fedilink source parent
[–] zygo_histo_morpheus@programming.dev 1 point 9 months ago 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! permalink fedilink source parent
[+] onlinepersona@programming.dev 0 points 9 months ago [removed by mod] permalink fedilink source parent
[+] onlinepersona@programming.dev 0 points 9 months ago [removed by mod] permalink fedilink source parent
[+] zygo_histo_morpheus@programming.dev 0 points 9 months ago [deleted] permalink fedilink source parent
[–] onlinepersona@programming.dev 0 points 9 months ago 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. permalink fedilink source parent
[–] tengkuizdihar@programming.dev 1 point 9 months ago 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. permalink fedilink source parent