https://bugs.kde.org/show_bug.cgi?id=402789
--- Comment #15 from Claudius Ellsel <claudius.ell...@live.de> --- (In reply to Nate Graham from comment #13) > I hear you, Claudius. I don't like mailing lists either, and I agree that > Bugzilla is clunky and antiquated. I'm very much in favor of migrating > everything to GitLab issues. However our sysadmins are already at 100% > capacity with migrating to the GitLab CI, and then after that, migrating > Phabricator Tasks to GitLab. Only after those are done can we begin the move > from Bugzilla to GitLab Issues. > > The best way to make that happen faster would be to volunteer to help the > sysadmin team with the technical work required, if you have any kind of > sysadmin or devops background. Alright, thanks for the input about what is currently the "bottleneck". I have no background in sysadmin or devops, but might be able to help with some stuff. Regarding migrating Phabricator tasks the problem is probably that it is not really supported out of the box by GitLab (https://docs.gitlab.com/ee/user/project/import/phabricator.html), correct? I read on https://gitlab.com/gitlab-org/gitlab-foss/-/issues/26850 that it should be possible with a script GNOME created, but am not really up to speed with the current state of the migration. At least it seems to be pretty much possible to achieve with existing tools. Also, I thought about maybe asking GitLab for help with some of the migration stuff. At least there is an issue for migration there: https://gitlab.com/gitlab-org/gitlab/-/issues/24900 -- You are receiving this mail because: You are watching all bug changes.
