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
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.
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)
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.