Maintaining a mirror on Codeberg

[tarleb]

I had created a pandoc organization on Codeberg a while ago, primarily to reserve the name. The request in #11082 by @yaxu, suggesting to leave GitHub, makes me wonder whether we should advertise that place as an alternative way to participate in the development process.

I don't think a full switch would be desirable or feasible for a number of reasons, including the limited computational resources of the Woodpecker CI used by Codeberg, and the overall difficulty of moving projects around. With that said, I do believe that an alternative way to contribute, one that doesn't require to accept the GitHub ToS, could be a positive.

[jgm]

Given my brain's limited computational resources, I'd prefer not to have development split over two places.

I suppose we could have a GH action that detects when a new issue has been created on the codeberg mirror and creates an issue here linking to it. Not sure whether that would just be a mess or not.

[yaxu]

Here's some info advocating mirroring between github and codeberg:
https://codeberg.org/Recommendations/Mirror_to_Codeberg

It seems some are happily doing this, it does seem like it would be error-prone though.. It also seems a bit pointless if everything stays on github anyway. If the aim is to move away from github, in my view it's better to do it sooner rather than later.

I switched the tidal haskell project straight from github to codeberg. The move using codeberg's migration was easy and pretty much complete, apart from github actions. It was easy enough get automated builds running on self-hosted forgejo runners, but I only have linux builds running so far.