Hi, On Thu, 11 Nov 2021 at 13:31, Jean-Paul Calderone <[email protected]> wrote: > > On Thu, Nov 11, 2021 at 4:19 AM Adi Roiban <[email protected]> wrote: >> >> Hi >> >> On Tue, 12 Oct 2021 at 01:42, Jean-Paul Calderone >> <[email protected]> wrote: >> > >> > On Mon, Oct 11, 2021 at 8:33 PM Adi Roiban <[email protected]> wrote: >> >> >> >> On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone >> >> <[email protected]> wrote: >> [snip] >> >> >> > I am working on migrating Tahoe-LAFS Trac to GitLab. If Twisted wants >> >> > to use GitLab instead, I'll probably eventually have a tool that makes >> >> > this an easy transition. If not, I'll at least have a tool that loads >> >> > everything from a trac project environment into an in-memory model >> >> > where it's easier to transform into something else. >> >> > >> >> > Jean-Paul >> >> >> >> I saw this project which does Trac to GitLab migration: >> >> https://github.com/tracboat/tracboat >> >> >> >> I didn't have time to check it out, but even when migrating to GitHub, >> >> I was thinking that some code can be reused from there. >> >> For example converting from TracWiki markup to Markdown. >> >> >> > >> > Yes, that project exists. It's not a good fit for the Tahoe-LAFS >> > migration. Maybe it will work for Twisted though. And as you point out, >> > maybe it has components that are helpful even if the tool as a whole isn't. >> > >> >> Jean Paul, have you managed to do the migration from Trac to GitLab >> for the Tahoe tickets? >> Was it a smooth migration ? > > > I haven't done this migration yet. It's sort of a mid-level priority for the > Tahoe project so it isn't moving along very quickly. > >> >> For my company we have migrated from Trac Tickets to GitHub (multi-repo). >> It was not a perfect migration ... but it was not that bad. >> With the bulk import API we managed to keep the creation date for each >> comment. > > > I'm curious if you wrote any software to produce a neutral-format > representation of Trac state as part of this migration effort or if you just > went straight from Trac to GitHub? (ie, I wonder if you made any tools I can > leverage for a different Trac migration)
Nothing generic yet. Very specific to GitHub API ... which is not the best. I hope GitLab has a better import API. And it's kind of specific to sqlite and converting from one Trac to multiple GitHub repos, with organization-wide projects. This might change when updating to handle Twisted. >> >> >> The Trac tickets that had the same ID as GitHub PR were migrated last. >> In this way we preserve the ID of most of the tickets >> >> Also, we plan to keep the legacy Trac instance in read only mode for >> the near future. >> >> The trac ticket have a reference like trac#1234 in the comments and >> with GitHub autolinks we automatically get a link >> >> Btw. This is already enabled on twisted/twisted >> trac#123 → https://twistedmatrix.com/trac/ticket/123 >> >> We also moved the wiki to GitHub Wiki .. we lost some nice features >> from Trac Wiki macros ...but that was not a big deal. >> >> The code is here >> https://github.com/chevah/trac-to-github/pull/13 > > > Ah - a quick skim of this code suggests the answer to my question above is > no. Okay. :) The code just gets the things done :) For ticket, the code only handles sqlite and Twisted has PostgreSQL Converting to PostgreSQL to do wiki migration was not that complicated https://github.com/chevah/trac-to-github/pull/12/files And I expect that converting the ticket migration from sqlite to psql will not be complicated. -- Adi Roiban _______________________________________________ Twisted mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/PUUYTQRUIW3REMUGJXBTTUSTSCRQMNXK/ Code of Conduct: https://twisted.org/conduct
