{"id":2034,"date":"2013-03-29T18:39:52","date_gmt":"2013-03-29T17:39:52","guid":{"rendered":"http:\/\/planetozh.com\/blog\/?p=2034"},"modified":"2013-03-29T18:39:52","modified_gmt":"2013-03-29T17:39:52","slug":"checklist-for-moving-a-project-from-google-code-to-github","status":"publish","type":"post","link":"https:\/\/planetozh.com\/blog\/2013\/03\/checklist-for-moving-a-project-from-google-code-to-github\/","title":{"rendered":"Checklist for moving a project from Google Code to Github"},"content":{"rendered":"<p>As soon as YOURLS 1.6 ships, I&#39;ll move the project development from <a href=\"http:\/\/code.google.com\/p\/yourls\/\">Google<\/a> to <a href=\"https:\/\/github.com\/YOURLS\/YOURLS\">Github<\/a> (why? long story short: <a href=\"http:\/\/planetozh.com\/blog\/2012\/11\/so-ive-tried-git-and-its\/\">read this<\/a>). So, I wrote down a little todo list to make sure the transition is as smooth as possible for everyone, which is:<\/p>\n<h2>On Github<\/h2>\n<ul>\n<li>Move in <a href=\"http:\/\/code.google.com\/p\/yourls\/issues\/list\">issues and tickets<\/a> from Google. I wrote a <a href=\"http:\/\/planetozh.com\/blog\/my-projects\/google-issues-to-github-a-migration-script-in-php\/\">tool for this<\/a><\/li>\n<li>Move in <a href=\"http:\/\/code.google.com\/p\/yourls\/w\/list\">wiki documents<\/a> from Google. There are a few tools around, like <a href=\"https:\/\/github.com\/trentm\/googlecode2github\/blob\/master\/wikiconvert.py\">wikiconvert.py<\/a>, but in worst case scenario doing it by hand is an option.<\/li>\n<li>Neatly organize the wiki on Github with a home page, sidebar, header and footer. Everything is explained in <a href=\"http:\/\/blackbe.lt\/github-wiki-sidebar-table-contents-header-footer\/\">this article<\/a>.<\/li>\n<li>Make a custom <tt>CONTRIBUTING.md<\/tt> with a few guidelines (aka RTFM). <a href=\"https:\/\/github.com\/necolas\/issue-guidelines\/blob\/master\/CONTRIBUTING.md\">This one<\/a> is a very comprehensive start.<\/li>\n<li>Create labels for issues: I was thinking <tt>bug<\/tt>, <tt>enhancement<\/tt>, <tt>duplicate<\/tt>, <tt>invalid<\/tt>, <tt>wontfix<\/tt>, <tt>RTFM<\/tt>, <tt>PEBKAC<\/tt>, <tt>worksforme<\/tt>, <tt>possiblewithaplugin<\/tt>.<\/li>\n<li>Tag older commits in Git to recreate the same <a href=\"http:\/\/code.google.com\/p\/yourls\/downloads\/list\">download list<\/a> as in the original project<\/li>\n<li>Maybe clarify the dev and branch strategy, such as in <a href=\"https:\/\/github.com\/zenphoto\/zenphoto\/wiki\/Zenphoto-Development-Process\">Zenphoto-Development-Process<\/a><\/li>\n<\/ul>\n<h2>On Google<\/h2>\n<p>Simply mention that the project has moved: modify issues, frontpage and wiki with the adminTabs feature at http:\/\/code.google.com\/p\/YOUR-PROJECT\/adminTabs. <a href=\"http:\/\/code.google.com\/p\/beets\/wiki\/Wiki?tm=6\">Example<\/a>.<\/p>\n<h2>Misc downloads<\/h2>\n<p>The inability on Github to host files other than your source code bugs me. In YOURLS there are a couple <a href=\"http:\/\/code.google.com\/p\/yourls\/downloads\/list?can=1\">extra files<\/a> that are available for download, or images used in the wiki documents.<\/p>\n<p>So far the idea I&#39;ve come up with is: create a branch named <tt>downloads<\/tt> and commit those little files there.<\/p>\n<h2>And?<\/h2>\n<p>Am I missing something? Any idea welcome :)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As soon as YOURLS 1.6 ships, I&#39;ll move the project development from Google to Github (why? long story short: read this). So, I wrote down a little todo list to make sure the transition is as smooth as possible for everyone, which is: On Github Move in issues and tickets from Google. I wrote a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[402,397,42,359],"class_list":["post-2034","post","type-post","status-publish","format-standard","hentry","category-published","tag-checklist","tag-github","tag-google","tag-yourls"],"_links":{"self":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/2034","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/comments?post=2034"}],"version-history":[{"count":3,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/2034\/revisions"}],"predecessor-version":[{"id":2037,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/2034\/revisions\/2037"}],"wp:attachment":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/media?parent=2034"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/categories?post=2034"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/tags?post=2034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}