> People saying that it is easy to migrate don’t know what they are
> talking about. GitHub isn’t just Git hosting, but a social network
> of open source developers and projects. You can’t migrate stars,
> issues with comments and the history of PRs, all linked to the
> profiles of their authors.
Every single for-profit company works their ass off to build a "moat" around their business and to create switching costs, even if they boast that you can "just take your data and leave."It is not an accident that it is difficult for non-trivial projects to "just leave GitHub." That is by design, it is part of how it grew to become the 800 pound gorilla, and it is part of why Microsoft bought them.
It could be not trivial to map those data into the new destination, especially if they don't have an API too.
This is how to programmatically create a new issue on GitLab https://docs.gitlab.com/ee/api/issues.html#new-issue and in Bitbucket https://developer.atlassian.com/bitbucket/api/2/reference/re...
[0] I firmly believe in preparedness.
You're right in a lot of ways.
A personal detail is that I've developed a bad habit of searching "github <project name>" when I need to find something. As if any project worth its salt is on github.
I'm changing that habit, I even started sharing my projects between github and gitlab over a year ago.
People saying that it is easy to migrate don’t know what they are talking about. GitHub isn’t just Git hosting, but a social network of open source developers and projects. You can’t migrate stars, issues with comments and the history of PRs, all linked to the profiles of their authors.
And sure you can self-host GitLab, I pushed for it at my previous employer and works great for on premises deployments, but it’s not the same for OSS if the community you care about isn’t there.
That said I am glad to see Nat Friedman as the new CEO. This gives me some hope for its future.