Import tickets from Core trac

[iandunn]

Since the Meta trac is the canonical location for tickets related to the WordPress.org website now, should we
import ​the WordPress.org tickets from the Core trac and then close them over there?

[devinreams]

There are some tools I'll dump here and start to look into:

• ​http://trac-hacks.org/wiki/DatamoverPlugin (deprecated)
• ​http://trac-hacks.org/wiki/TracMigratePlugin (moves entire trac, not sub-selection?)
• ​http://trac-hacks.org/wiki/TicketMoverPlugin (requires being in same environment directory)
• ​https://github.com/UnwashedMeme/TicketMoverPlugin (forked version of above)
• ​http://trac-hacks.org/wiki/TracSqlHelperScript

Some tools to move from trac to github which may be good starting points:

• ​http://stackoverflow.com/a/10395164/16248
• ​https://github.com/trustmaster/trac2github
• ​https://pypi.python.org/pypi/tratihubis/

Trac import can import from CSV:

• ​Export exiting tickets to CSV (only includes description column added with &col, not comments
• ​http://trac.edgewall.org/wiki/TracImport
• ​http://trac-hacks.org/wiki/TicketImportPlugin

[Otto42]

I don't think that it's worth adding a bunch of effort to just straight move them over, however if any of them are relevant, perhaps making a new ticket for them here and cross-linking them from there (and closing them there) would be reasonable.

Certainly, any problems still listed in the core trac that still are outstanding for the .org site should get new tickets made here for them.

[iandunn]

Sounds good to me.