Re:We are moving the Roslyn code to GitHub
by Joeboy on Sunday January 11, 2015 @05:23AM
(#8869603)
Microsoft or otherwise, I don't think the idea that GitHub is going to be run like a public utility forever is a smart bet.
[ Parent
| on HN ]
Re:We are moving the Roslyn code to GitHub
by davidgerard on Sunday January 11, 2015 @05:28AM
(#8869610)
It's reasonably easy to pick up your repo and leave.
How easy is it to pick up your bugs and leave?
Re:We are moving the Roslyn code to GitHub
by audreyt on Sunday January 11, 2015 @05:56AM
(#8869654)
Reasonably easy: https://github.com/gitlabhq/gitlab-recipes/blob/master/impor...
GitLab B.V. CEO here, on the 22th of this month (January) we'll come out with GitLab 7.7 that includes a GitHub.com importer for both repo's and issues. It will have a simple web interface where you can select the projects to import.
Re:We are moving the Roslyn code to GitHub
by josteink on Sunday January 11, 2015 @06:31AM
(#8869708)
It seems it's pretty easy with Github wikis too:
Private repos cost and there is, and will be, a sufficient demand for such a purpose. Between nuget for package mgmt and github (instead of TFS, etc) you are looking at having important, common pieces available. This makes it extremely comfortable to be in the MS dev camp and still feel that you can interface with others and be sharpening the sword in ways that enable you to build cross platform and potentially jump platforms as necessary.
People have seen experienced .net devs picking up in a wide assortment of communities. Some interpret this as mind flight, or it might just be that the .net ecosystem has made some wise choices that enable devs raised in the ecosystem to not feel their world has silo walls. It's less "no, this" and more "yes, and."