3 ms·

Lucky for us GitHub unlike Facebook don't rely on selling advertisments to make revenue. Plus git is decentralised. You can migrate your entire code anywhere yo

Lucky for us GitHub unlike Facebook don't rely on selling advertisments to make revenue. Plus git is decentralised. You can migrate your entire code anywhere you want. As far as issues are concerned I am pretty sure competitors like GitLab supports exporting them via GitHubs awesome API. It's not as bad as make you sound it. Things could have been much more worse.

rrix2 7y ago
I can migrate my code, but not all my consumers which use "github.com/my/package" as the import qualifiers all over the place.
- blocked_again 7y ago
  Doesn't setting up a mirror solve the issue ? https://help.github.com/en/articles/about-github-mirrors https://help.github.com/en/articles/about-github-mirrors
- brodock 7y ago
  GitHub doesn't provide you with any standard way to migrate the related metadata, but unlike Atlassian's Bitbucket, which doesn't make everything accessible with their APIs, it's possible to get all the data with GitHub's API (as of today). If you use GitLab importer tool, we migrate everything from your old project. All issues, all pull requests, and we even migrate inline comments inside a pull request. All it takes is one OAuth authorization and the pressing of a button. When inside GitLab, we even give you an Export zip file, that you can import in your hosted version of GitLab (or use any alternative, that can read our export file format).
- ChickeNES 7y ago
  I assume that's a reference to Golang? I gave up Go after one too many times dealing with its terrible package management
- int_19h 7y ago
  That's exactly why any package versioning that hardcodes URLs to packages is broken by design. URL is where. A package is a what.
jeena 7y ago
Facebook had awesome APIs too, I wrote a Facebook App (FBML anyone?) where you could book a table at a restaurant and automatically create a event and invite your friends, until they didn't. Not sure it makes sense to point out that things could have been much more worse, that is basically always the case, independent of how bad it is.
int_19h 7y ago
What I'd really love is for federated project hosting. Consider: why does a GitHub pull request have to be from one GH repo to another? So long as it has read access for the source repo, it shouldn't matter where it is. Now, it also keeps track of changes in the source, so that it can update PRs etc. But surely distributed notifications are also a solved problem? Ideally, I should be able to do PRs and link to bugs and commits in comments etc, and it's all federated and "just works".
- jeena 7y ago
  ActivityPub is the distributed notification system you talk about and yes it's a solved problem. It's already used for Twitter and Instagram like content, see Mastodon and Pixelfed.

rrix2 7y ago

I can migrate my code, but not all my consumers which use "github.com/my/package" as the import qualifiers all over the place.

blocked_again 7y ago
Doesn't setting up a mirror solve the issue ? https://help.github.com/en/articles/about-github-mirrors https://help.github.com/en/articles/about-github-mirrors
brodock 7y ago
GitHub doesn't provide you with any standard way to migrate the related metadata, but unlike Atlassian's Bitbucket, which doesn't make everything accessible with their APIs, it's possible to get all the data with GitHub's API (as of today). If you use GitLab importer tool, we migrate everything from your old project. All issues, all pull requests, and we even migrate inline comments inside a pull request. All it takes is one OAuth authorization and the pressing of a button. When inside GitLab, we even give you an Export zip file, that you can import in your hosted version of GitLab (or use any alternative, that can read our export file format).
ChickeNES 7y ago
I assume that's a reference to Golang? I gave up Go after one too many times dealing with its terrible package management
int_19h 7y ago
That's exactly why any package versioning that hardcodes URLs to packages is broken by design. URL is where. A package is a what.

jeena 7y ago

Facebook had awesome APIs too, I wrote a Facebook App (FBML anyone?) where you could book a table at a restaurant and automatically create a event and invite your friends, until they didn't. Not sure it makes sense to point out that things could have been much more worse, that is basically always the case, independent of how bad it is.

int_19h 7y ago

What I'd really love is for federated project hosting. Consider: why does a GitHub pull request have to be from one GH repo to another? So long as it has read access for the source repo, it shouldn't matter where it is. Now, it also keeps track of changes in the source, so that it can update PRs etc. But surely distributed notifications are also a solved problem? Ideally, I should be able to do PRs and link to bugs and commits in comments etc, and it's all federated and "just works".

jeena 7y ago
ActivityPub is the distributed notification system you talk about and yes it's a solved problem. It's already used for Twitter and Instagram like content, see Mastodon and Pixelfed.