The Subplot project announces the move from Gitlab to Radicle.
This move was precipitated in no small part by Gitlab Inc's hell-for-leather adoption of "AI" into their platform making it harder and harder to avoid the damaging effects of it on our project. In addition, the authors of Subplot firmly believe in the value of decentralised revision control, and forges such as Gitlab and Github (and to a much lesser extent Codeberg) foster a form of community which is shaped around a central hub.
After significant discussion, over the course of nearly a year, the decision was made that if we were to shift from Gitlab to Radicle then it would be before the next renewal cycle for our Gitlab open-source licence. When Gitlab sent their email about renewal the language in it was so dehumanising that it tipped the scales in favour of migration despite Radicle not yet being as featureful.
The migration began around three months ago, and helped in no small part by Lars working on CI for Radicle we made the shift before renewal was due. If you did nothing but consume Subplot via crates.io then nothing should change for you. If you consumed via Debian packages built by Lars then nothing should change for you. If you contributed to, or otherwise interacted with our Gitlab project then you will need to do so via Radicle instead. The Radicle team publish a comprehensive user guide and their Zulip is very friendly.
We remain, for now, on our Matrix channel (#subplot:matrix.org) and we welcome interaction there if you are interested in Subplot, regardless of whether or not you are able/willing to use Radicle. It will take us some time to get used to our new home, and we will inevitably hit roadblocks and changes in our processes as we settle.
If you are interested in Subplot and Radicle piques your interest then why not join in? We migrated issues from Gitlab to Radicle, and where we felt it appropriate we converted some issues into design notes in the repository instead, making it easier for anyone to submit a patch to proposed changes.
We apologise for any inconvenience caused by our move, but hope that over time you will come to agree with us that this was the right move for the project.
Thank you for your continued interest and support.