That's the script I found, too. But it's not very nice in terms of viewability. It must be changed to have a good looking imported issue list. I will do that.
And yes, the more issues we can close before importing, the better. I will start to review the issues I mentioned (maybe some more) and put a "works for me" under them, if that's the case. So keep an eye on the list. I also would plea to not import closed issues, to give you something to think about. But that's something I will bring up separately when actually working on the import and script. Stadtpirat ----- Original Message ----- From: Stefan de Konink <[email protected]> To: [email protected] Cc: Sent: Sunday, December 16, 2012 11:49 PM Subject: Re: [Cherokee] Issue List On 12/16/12 23:49, Daniel Lo Nigro wrote: > There are several scripts to migrate issues from Google Code to Github > automatically, one of which is > here: https://github.com/arthur-debert/google-code-issues-migrator > > I once did a migration from Trac to Github and that went pretty werll. > There are some issues with it, but it works well enough. I think we should first asses everything that has a patch/diff inside it. Stefan _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
