Two things: * Development and maintenance of Phabricator has slowed down a lot. * People were claiming phabricator was old-fashioned and confusing and hoping

Two things: * Development and maintenance of Phabricator has slowed down a lot. * People were claiming phabricator was old-fashioned and confusing and hoping a merge-request based workflow would be more inviting I'm the maintainer of one of the test projects that moved to our gitlab instance, and it's mostly fine, we're missing things in the merge request workflow, but have papered around that with labels (https://invent.kde.org/kde/krita/merge_requests https://invent.kde.org/kde/krita/merge_requests), but we're still using phabricator for task management because it's so powerful for that that we cannot move that part of our workflow to gitlab yet.