Migration from Trac to GitHub issues

[ajj]

Make and execute plan to move from using trac to using GitHub? issues to better integrate tickets with commits and reviews.

[ajj]

Notes from Jeff K:

I've had the same thought recently. So much so, that I went searching for utilities and info on how to do it.

Github recently released an API for this express purpose. ​https://gist.github.com/jonmagic/5282384165e0f86ef105 - The API allows for

Otherwise, there are other utilities available:
​https://github.com/robertoschwald/migrate-trac-issues-to-github - This is a simple, scripted migration tool. Pros: simple to use, direct conversion. Cons: No linking trac login names to github login names, emails are sent for every issue (ugh).
​https://github.com/XhmikosR/migrate-trac-issues-to-github - Forked from the same source as the first option, but allows for config files for user names.
​https://github.com/tfoote/github-migrate-trac-tickets - One more forked from the same originator, probably the most configurable.
​https://github.com/mavam/trac-hub - Uses the GitHub? API, but streamlines the process. Pros: Configurable, including custom label mapping, linking trac to github users, etc. No emails sent. Infinitely configurable. Atomic, so no possibility of exterior interruptions. Cons: A bit slower than the above because the API sets purposeful speed limits on issue migration. Infinitely configurable.

Of the options I've found, The last one in my list (mavam/trac-hub) seems like the best option, mostly because it uses the pre-existing API set by GitHub?, so emails aren't sent on ticket creation, and linking trac→github is much more configurable, not only for user names, but also for milestones, work packages, and priority.

[ricardo]

I'm playing with this and the github part is OK. However the Trac part using `xmlrpc` is not. It looks like RPC uses port 135 which is blocked for us at the ILL… more news soon.