I am trying to figure out if it is possible to migrate Tahoe-LAFS project to GitLab.com. Tahoe-LAFS currently uses GitHub for git hosting, PR reviews, CI, and the such. Wiki and tickets are in a Trac instance. There’s several years of worth of history in Trac (some of them predating GitHub and GitLab), which we would like to preserve. We’d like to move over everything we have in both GitHub and our Trac instance.
As an initial test, I am working on importing a smaller project. Tahoe-LAFs uses zfec, which has a Trac instance (smaller wiki, fewer tickets) and a GitHub presence (fewer number of commits, issues, and PRs). I am toying with Tracboat, but I am not sure if that is the right tool to migrate a Trac wiki and issues to GitLab.com. From Tracboat’s documentation I can’t quite figure out I can migrate a Trac project to GitLab.com, and not a self-hosted GitLab instance.
Does anyone have practical experience with something like this? What advice can you offer? Is there anything better than Tracboat out there?
Please correct me if I am wrong, but it doesn’t look like Tracboat can help with migrating tickets and wiki to GitLab.com. Tracboat can help with migration if I am self-hosting a GitLab instance – it needs database access.
Repository mirror would only take care of your git commited file, but even with gitlab-ce or free gitlab.com account, you can only push, but as you would want to pull from Tahoe, then it would require an EE capable account. But since you want issues, it’s not ideal either. Unfortunately I haven’t any other ideas to be honest, and without DB access it might not be possible to do everything without having your own gitlab instance. But maybe someone from the Gitlab team might be able to provide additional info.
Don’t worry, it was me that wrote the hard-to-parse wall of text!
I am thinking this route now: I can migrate tickets and wiki from Trac to a self-hosted GitLab instance, and then import the project from my self-hosted GitLab to gitlab.com. I am wondering if there’s a better way.
