[enjo]

On what planet is shutting down a service, with months and months of notice, evil?

I get it, we all hate Google on HN (for reasons unclear to me) but this is ridiculous. If these projects are truly important than donate some time and move them over yourself. To demand that google invest time and resources into the migration of these migrations or to keeping this running forever is just silly.

Hell tools like https://code.google.com/export-to-github/ even exist.

[dchichkov]

Shutting down Google Code is equivalent to destroying a storage full of handwritten articles, some of which exist only in a single copy and some of which are incredibly valuable.

Why valuable? For example computer science researchers had been using Google Code to host supplement code for their research publications for years now. These repositories are not maintained by these researchers any more, yet the code some times is incredibly valuable, because it allows to reproduce research results. The reason why researchers were using Google Code, is because it was supposed to be as stable as the underlying company. Yet now, in 10 months, these repositories will be destroyed.

[NeutronBoy]

If the code is that valuable, then perhaps they should put some time into maintaining the code, moving it to another provider, or convincing somebody to pay for hosting.

[dchichkov]

Example. A cancer researcher, publishes a paper in Nature Genetics. Like this one: http://www.nature.com/ng/journal/v42/n3/abs/ng.522.html

In that paper she publishes a link to a Google Code repository as supplement materials. For example, in the aforementioned paper there is a link to the following repository: http://code.google.com/p/glu-genetics/

[NeutronBoy]

Given she published the paper and link, she should either a) take responsibility for the general availability of the materials, and b) make sure that if people email her for the materials (after finding that they're not available on Google Code) she shares them.

Don't get me wrong, I'm all for retaining the materials and knowledge, etc etc. I'm just having a hard time understanding why you expect Google to do the work and maintain it? What if she uploaded her materials to Megaupload, or any of the hundred other filesharing sites - would you hold them to the same standard? Why doesn't the journal that published the paper (which, has a revenue stream) host the material, given that it directly supports their work?

[jamiesonbecker]

Megaupload did not hold itself out as a repository for original work.

Megaupload is not run by Google, with the stated mission of organizing the world's information.

Megaupload is bankrupt. Google is one of the richest technology companies in history.

This is not Megaupload throwing away its hoard of 90's B movies. This is Google, knowingly and literally throwing away coding history. We don't even know what might be thrown away.

What if some currently unknown researcher wrote his first code and uploaded it to Google code and forgot about it, and turned out to be the next Zuckerberg or even Turing?

What if some valuable research that was entrusted to Google from a deceased researcher suddenly disappears?

There are likely many more unintended consequences stemming from such an act, and I don't think we should give Google a pass, especially since Google controls possibly the largest collection of computers on the planet. (besides, source code tends to compress pretty well!)

Seems like the least they could do is stick it in an 'unlimited' Google Drive and lock it as read only.

[DaveWalk]

Great example. In 2-10 years from now, someone will want to find that repository.

Does anyone know of an effort to maintain this, like is done with sequencing data at the NIH? Something like PubMed Central?

I have first hand experience with this on the biology side, looking for reagents or even protocols from a 10 year old paper...and coming up completely dry. It's kind of a travesty, but the world collectively shrugged.

[leni536]

Handling and archiving supplementary materials should be the responsibility of the journal (like distributing and archiving the article itself). They should discourage linking to 3rd party websites where the author published his/her work.

I'm pretty sure that Google Code had a TOS where they stated that they don't guarantee that your repository is safe there forever.

There could be several reasons for closing a repository including Google going bankrupt. The availability of a scientific article should be much longer (ideally infinity) than the lifetime of any company.

[jamiesonbecker]

It may not be valuable to the author. That does not mean it's not valuable to some future searcher.

[Turing_Machine]

Right.

Researchers would kill to have the balled-up scraps of paper that (e.g) Shakespeare threw in the trash.

[walterbell]

Are we supposed to believe that Google does not understand the value of CITATIONS and PERMALINKS?

[ocdtrekkie]

In actuality, I've found most HN users seem to love Google. To the extent that almost any criticism of Google gets downvoted to death.

[ocdtrekkie]

Case in point, this comment just dropped three points. ;)

[markcerqueira]

Don't sweat it. Don't let imaginary internet points make you feel bad... or good.

[bigiain]

FWIW, Google were happy for a lot of other people to invest time and resources into putting their projects there in the first place - you don't think there's some reasonable expectation that Google would expend some extremely minimal resources at their scale - to ensuring those peoples effort wasn't wasted/lost?

Having said that, I'm not part of any movement to "demand Google do something different", but I've been a longtime member of the "Warn friends/family/colleagues about the dangers of participating in Google services in any way that'll have any downside when they close it down, because they've got a strong track record of doing that" movement.

If _I_ were the person making this decision at Google, my announcement would have been more along the lines of "blah blah shutdown blah blah apologies/excuses blah blah, so we're going to donate enough to archive.org to ensure everything on code.google.com gets archived permanently, and automatically redirect all future code.google.com requests to that permanent archive".

[jayvanguard]

> On what planet is shutting down a service, with months and months of notice, evil?

The current planet? Open source projects have a lifetime of years so five months is not that long in the scheme of things. People put there code on there and participated (providing Google content that they were able to use and drive traffic) with the expectation that it would be there for the long term.

[oldmanjay]

This is a rather watery definition of evil. It is fairly close to saying a restaurant is evil for not keeping a menu item you like.

[walterbell]

Would it be ok for Google to delete Usenet archives?

Or a library to burn down its own buildings? Or Google to delete all scans of old books?

History matters, because citations to "old" research/code may become more valuable with new requirements and research. Surely a company that "organizes the world's information" needs no explanation of these topics.

[krapp]

>Would it be ok for Google to delete Usenet archives?

If it's their archives, yes.

And if those are the only archives of Usenet in existence, then it's not Google's fault no one else cared to back it up.

[bigiain]

Somebody else did have a usenet archive - Google bought them, mashed up a bunch of other nn-usenet Google stuff into it, then let it bitrot until it was effectively useless, and then removed the only search features that worked...

(Admittedly, if I recall correctly, Dejanews had already gone broke trying to maintain that archive before Google bought it, so arguably Google didn't kill it, they just bought the dying corpse and kept it animated in a zombie-like state for a decade or so past it's natural death...)

[krapp]

And in the intervening years, no one running a news server thought to back theirs up, no one crawled Google and made torrents?

This is software, not ancient manuscripts written by scribes on now crumbling vellum - there is no excuse for there to be one canonical copy of anything. Every pornographic movie ever made has multiple redundant backups on decentralized peer to peer networks and darknets.

I understand the importance of maintaining references, but realistically, expecting URLS to be permanent is shortsighted at best, unless you own that domain and the server it's on and expect to have the money to keep the rights to it in perpetuity. You can't expect a third party host to be willing to keep the servers on forever.

But as far as the historical record and the data itself - Google's given warning, people can move their data or lose it. Fork and move on.

[Angostura]

> It is fairly close to saying a restaurant is evil for not keeping a menu item you like.

Actually closer to saying they are evil for destroying humanity's only copy of the recipe.

[npizzolato]

After shouting loudly they are going to destroy it and waiting months for anyone to come copy the recipe.

[yellowapple]

It would be the open-source world's equivalent to Geocities shutting down. There are still times when I'm trying to search for something (usually some obscure programming or hardware hacking topic) and the only source of information was a Geocities site. I can't imagine how much of a royal pain in the ass it will be if Google Code experiences the same fate.

> I get it, we all hate Google on HN (for reasons unclear to me)

The reasons should be clear to anyone with historical context; this isn't the first time Google has spontaneously pulled the plug on some "non-core" project it decided wasn't making quite enough money, in complete disregard of said project's use by the real world. It's these sorts of things that make me very reluctant to invest heavily in Google's ecosystem; I've personally been burned in the past by these sorts of things.

A part of me wants XKCD #1361 to come true.

[asfaltboy]

I like how that project is hosted on Google code

[skj]

It's not a googlecode-hosted project: there is no /p/ in the middle, and you can't see its source (not that there'd be much to see). It's a tool made by the googlecode team to help migrate.