News for hackers. Stuff that matters.
Re:Libtiff goes offline by Mizza on Monday September 12, 2016 @08:33PM (#12484871)
GitHub will rot some day as well. (I think we're already seeing it start to decline.)

This is simply a permanent problem. Archive.org and to a lesser extent IPFS are viable solutions for archiving, but _contingency_ plans are I think the missing component here. Pray for the best but prepare for the worst.

Re:Libtiff goes offline by bane on Monday September 12, 2016 @09:01PM (#12484964)
You know, come to think of it, Archive.org is sorta kinda the right place to store these things. If they offered source code control they would both get the source as well as the path to the latest version all at once, which could be an invaluable historic record.
Re:Libtiff goes offline by ajross on Monday September 12, 2016 @10:50PM (#12485306)
A git HTTP archive can be crawled and archived in principle. They might well be doing this already with github and elsewhere just through the normal course of their operation.
Re:Libtiff goes offline by toomuchtodo on Monday September 12, 2016 @11:00PM (#12485360)
Re:Libtiff goes offline by ashitlerferad on Monday September 12, 2016 @11:02PM (#12485374)
Re:Libtiff goes offline by toomuchtodo on Monday September 12, 2016 @11:32PM (#12485456)
Pertains only to Issues, not the git repo itself.
Re:Libtiff goes offline by themartorana on Monday September 12, 2016 @09:11PM (#12484995)
I don't think we're seeing a Github decline. Yes they've had some internal strife not all that connected to business, but Google just moved a lot of its OSS there, Microsoft just moved a bunch of stuff there. Git repos take a single command line statement to move, but Github is only slowing if by the force of not having much left to hoover up.

Gitlab et al are growing, and now AWS has its own integrated solution, but I don't see Github going anywhere for a very, very long time. (Barring catastrophic happenings, of course.)

Re:Libtiff goes offline by jen20 on Monday September 12, 2016 @09:43PM (#12485084)
The issues and pull requests associated with a repository on GitHub (and often referenced in commit messages) do not move along with the code though.