Something we haven't talked about in the migration yet is what to do with issues.
In a brief survey of other projects I've learned: - Launchpad Issue tracker has more features than Github (in 2011 anyway, has probably changed a little bit. See OpenStack migration plan<https://blueprints.launchpad.net/openstack-devel/+spec/move-to-github>, a good overview and evaluation of things to consider) + general consensus seems to be that in almost all respects GitHub is noticeably faster than Launchpad, something reflected in my personal experience, but perhaps not in China? c.f. ZoomQuiet in other thread. + there is an Launchpad to Github issue importer<https://github.com/johnf/github-issue-importer>, no idea how well it works. Hasn't had much commit activity, but that could because it solves the problem and then isn't used again. ~ issue migration is unecessary. Leave old stuff as old stuff and only create new bugs/requests as they arise, link backwards as needed. (Nunit<https://groups.google.com/d/topic/nunit-developer/m5IGh-u6cWI/discussion> ) ---- My personal opinion is that we should use all of GitHub's facilities: code, issues, wiki, and perhaps even github pages for leoeditor.com. Leo's internet presence is rather fractured and this is a good opportunity to pull everything together into a more cohesive and integrated whole. I'd give the github-issue-importer a trial run or two. If it works out of the box, great, otherwise proceed with "leave old stuff as old stuff". My 2c. -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
