In the blog post Microsoft practically admitted that they are not keeping up with GitHub which has become de-facto the repository for the open-source projects.
I have hosted the Google DataTable .NET Wrapper on CodePlex for years, and obviously I was invited also to migrate the code. Certainly, there are other online-repositories such as BitBucket, or others, but GitHub is quite appealing these days.
So, if you are to migrate your project from CodePlex to GitHub, or to some other repositories, for sure you would like to keep the whole history of changes. As my project is not that big, I could not really bother, but just wanted to have the challenge of doing it.
Microsoft and GitHub were kind enough to create a migration procedure described in this blog post, so that the procedure is quite painless. ¬†This is really great, as I was quickly searching in internet the various possibility for conversion from svn to git, but the process to me looked quite painful, so i simply skipped it and moved to the “official migration path”.
I faced few “issues” during the migration:
- Even though I followed the instructions , I get prompted for the user-name and password in GitHub in order to access the TFS source code. I was really insisting into placing my CodePlex username and password, but that was not the right user. ¬†What need to be inserted instead is the username suggested in the “Connect” option in CodePlex. Just copy that username and use your usual CodePlex password.
- This is not really an issue, but the trunk directory was copied “as-is”, and I kind of didn’t really like it on Git, so i had to manually intervene and “flatten” the repository by removing the trunk folder. As this was my first commit on Git, I forgot to configure Git with my GitHub username and email so I had to manually change the author on an already committed code. If you have the same situation then I advice you to read the following blog post Changing Author Info¬†which¬†helped me out big time.
However, it worked, the new home for the library can be found here.
Write back about your issues?