On Mon, Oct 11, 2021 at 8:33 PM Adi Roiban <adiroiban@gmail.com> wrote:
On Mon, 4 Oct 2021 at 12:07, Jean-Paul Calderone <exarkun@twistedmatrix.com> wrote:
On Mon, Oct 4, 2021 at 5:39 AM Chris Withers <chris@withers.org> wrote:
On 04/10/2021 10:32, Adi Roiban wrote:
For me, the Trac migration was Plan B, and I would like to spend the available time looking at migrating Trac Tickets to GitHub Issues
That would certainly get my vote.
I wish I had spare cycles, but I'm already in three levels deep yack shaving that had me hit this...
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.
Regards
-- Adi Roiban _______________________________________________ Twisted mailing list -- twisted@python.org To unsubscribe send an email to twisted-leave@python.org https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/twisted@python.org/message/SVPIPR4GXP5... Code of Conduct: https://twisted.org/conduct