>> * Add ticket history > > Do we really need this? What about just linking to the original TT? > That seems like less work.
I already have a link in the GH issue back to the original Trac. However, if we rely on that, then you can't shut down the Trac instance. >> * Add ticket ownership > > Do we need this? Perhaps we should let this be a "reset" where people can > decide what tickets they want to assign themselves. That sounds entirely reasonable to me. Would also let me not worry about the issue of parsing through all the Trac cc:s, too. >> * Convert the ticket text to Markdown it renders correctly. > > If this is easy, then go for it. I think just stripping out some of > the basic Trac-isms would be enough. The big thing is to make the code markup be plain text so it doesn't get rendered as Markdown. POD especially makes Markdown crazy because, for example, "=pod" means "level 1 heading called 'pod'" in Markdown. >> * Add milestone > > Do we need this? As far as I know, we don't use milestones anymore, > and they were always kind of a big lie we told ourselves and others. I'll be glad to not convert those, too. So it sounds like you're suggesting the following: * Do NOT bring over any ticket ownership information from Trac. * Do NOT bring over milestones from Trac. Anyone else have thoughts? I'm glad to not bring over unused data, and I'll take silence as consent on those two bullets. xoxo, Andy -- Andy Lester => [email protected] => www.petdance.com => AIM:petdance
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
