News for hackers. Stuff that matters.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by jarfil on Saturday June 16, 2018 @01:56AM (#17326100)
The problem lies in the comments and issue tracking, which are not stored in git. Sure, you can clone the repo, but you can only take the wiki with you, the rest would be lost.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by gpantazes on Saturday June 16, 2018 @02:35AM (#17326222)
So what I'm hearing is the solution to this migration problem is to also store the entire issue tracker as a git repo alongside the real repo and wiki repo? Git repos for all the things! (Seriously, I think this solution would fit right in along with the way Wikis are handled)
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by PretzelFisch on Saturday June 16, 2018 @10:34AM (#17327572)
How hard is it for some ont to use the GitHub api and port all of that over to a new system?
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by greenhatman on Sunday June 17, 2018 @05:52PM (#17334539)
GitLab already has an automated migrator you can use.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by manigandham on Saturday June 16, 2018 @01:13PM (#17328254)
Github has APIs to export all of this. Some services have importers to rebuild the issues but at the very least the data won't be lost.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by Fomite on Saturday June 16, 2018 @02:35AM (#17326221)
To my mind, the actual problem is neither one of those things, but if Github is wrapped up into some new project. Many of the citations for Github aren't for software, but as a stable, open store for data.

Which means if that URL changes, that link - in a physical paper - goes stale.

Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by masonicb00m on Saturday June 16, 2018 @03:39PM (#17328946)
If you need stable links then buy yourself a domain or use a URL shortener that you can update. Might be wise to also provide content hashes of the data you're referencing in your paper.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by Cyphase on Saturday June 16, 2018 @02:43AM (#17326243)
Even if it does get merged or renamed, I don't see why Microsoft wouldn't forward the URLs.

Link rot is a real issue in general though, I don't mean to minimize that.

Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by Fomite on Saturday June 16, 2018 @02:44AM (#17326246)
I agree - which is why I haven't moved my lab's accounts.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by kwhitefoot on Saturday June 16, 2018 @03:08AM (#17326316)
Surely it ought to be possible to store all that stuff in git as well.
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by moogly on Saturday June 16, 2018 @08:55AM (#17327207)
Won't GDPR legislation force GitHub to make that exportable?
Re:Microsoft’s purchase of GitHub leaves some scientists uneasy by detaro on Saturday June 16, 2018 @09:08AM (#17327246)
It's already exportable through the API, that's not the problem.