Seems like a step backwards to me. I'd rather allow people to collaborate on GitHub somehow.

I could mirror from Winehq GitLab to here if given appropriate permissions, or give someone permissions and instructions on Winehq GitLab to configure it, or I can set up a new organization/repo to hold the mirror.

@madewokherd Then what might be the steps forward?

1. Recent issues opened here weren’t followed up, like Off by 256 error in generated IL code for label.  #21799, which is idle for 4 months.
2. WineHQ development is on the GitLab side, so pull requests created here require a lengthy process to review and merge, like in Use -undefined dynamic_lookup in profiler LDFLAGS #21257 where you had to move the commits over.

I believe you will have to choose from either a clean reboot from WineHQ fork (what this pull request tries to enforce), or somehow (if possible) fully take over this repo and move development back here. (Which doesn't seem to be WineHQ practice.) Otherwise, end users of Mono have little idea how to interpret the announcement properly and where to get support. A GitHub mirror of your GitLab instance might not help much (OpenStack is an extremely terrible example, and their GitHub mirror isn't helpful).

Note that this change doesn’t affect existing issues or new pull requests, so people can still collaborate here if they want.

Oh, 21799 is on my todo list.

GitHub can redirect repositories. Although that might require you to transfer them.

It is not a solution :/