We have now been thinking about dropping the GitLab merge request workflow in favour of something far less standardized but at the same time giving much more freedom to the potential contributors: - Host your fork anywhere (including on our GitLab instance for now); - Work however you wish; - Send us an e-mail or a message on IRC, or even a message here on the Fediverse, asking us to integrate the changes from your fork.
The main downside would be the loss of the public discussions on merge request diffs, but it is not like these usually involve more than two persons (so could have been done by e-mail just as well).
Your comments on this suggested workflow are welcome, whether or not you are already a ./play.it contributor, and whether or not you were planning to become one in the future. Nothing has been really decided yet, so all feedback can help us going choosing the best way to handle contributions.
These will not become the canonical repositories, but their purpose is to provide new contributors a way to use some interface they are already used to, so they can send patches our way until they gain enough trust to get a direct access to the canonical repositories served directly from our server.
As a reminder, the canonical repositories that are replacing the forge.dotslashplay.it ones are the read-only repositories we self-host using cgit: https://git.dotslashplay.it/
The ReadMe files are not updated to reflect that yet, but this will be done, alongside the addition of a contribution guide, shortly after the release of the incoming 2.28.0 feature update. From this moment, the repositories hosted on forge.dotslashplay.it will probably be slowly phased out in favour of an e-mail based workflow.
Bugs and requests tracking are going to stay on forge.dotslashplay.it for now, but will probably be migrated to another system too at some point in the future. For that we still need to find a good bugs tracker (must be a bugs tracker only, with no support for extra things) that can be easily installed on Debian.