4 ms·

Myself and lots of other academics chose google code to host projects that are no longer actively contributed to but still used or of interest to the academic c

Myself and lots of other academics chose google code to host projects that are no longer actively contributed to but still used or of interest to the academic community as building blocks for future research. At the time it seemed like the safest place to leave something. I'll be moving my code and forking a few analytical projects I use appreciate but I hope they would leave the site up in read only or archive mode for longer then a year as i'm sure many authors have moved on and may not even be aware of this change.

BrainInAJar 12y ago
> At the time it seemed like the safest place to leave something. Google is never the safest place to store anything, unless it's your personal data. Google sunsets products constantly.
- jfoster 12y ago
  Correct. That's only become particularly relevant in the past few years, though. Sure, they retired projects before, but they are becoming increasingly ambitious with the retirements. By that I mean they are retiring things that lots of people still use (Reader), were not released that long beforehand (Helpouts), could be viable businesses with modifications (Wallet for Digital Goods), or contain large quantities of valuable content (Code). My point is that Code has been running for quite a while, and at one stage it probably did look like the safest way to keep a project online. Can't blame people for choosing it earlier on.
abvdasker 12y ago
Yes, this is also my biggest concern. I'm working in bioinformatics and smallish open-source repositories created by other bioinformaticians which haven't seen much maintenance but still get used a fair amount (like https://code.google.com/p/biopieces https://code.google.com/p/biopieces) will probably be the worst casualties from this transition. Guess we'll have to backup those dependencies somewhere else...

4 ms·

Myself and lots of other academics chose google code to host projects that are no longer actively contributed to but still used or of interest to the academic c

by micro_cam 12y ago

BrainInAJar 12y ago
> At the time it seemed like the safest place to leave something. Google is never the safest place to store anything, unless it's your personal data. Google sunsets products constantly.
- jfoster 12y ago
  Correct. That's only become particularly relevant in the past few years, though. Sure, they retired projects before, but they are becoming increasingly ambitious with the retirements. By that I mean they are retiring things that lots of people still use (Reader), were not released that long beforehand (Helpouts), could be viable businesses with modifications (Wallet for Digital Goods), or contain large quantities of valuable content (Code). My point is that Code has been running for quite a while, and at one stage it probably did look like the safest way to keep a project online. Can't blame people for choosing it earlier on.
abvdasker 12y ago
Yes, this is also my biggest concern. I'm working in bioinformatics and smallish open-source repositories created by other bioinformaticians which haven't seen much maintenance but still get used a fair amount (like https://code.google.com/p/biopieces https://code.google.com/p/biopieces) will probably be the worst casualties from this transition. Guess we'll have to backup those dependencies somewhere else...