Google code shutting down

[FAST6191]

Wasn't quite sure where to post this but I did not think an off topic would be the place for it.

It was mentioned on IRC so I thought I would mention it here, mainly as quite a few ROM hacking tools and projects were hosted (source and binary), there is still a decent amount of time left to grab things but hey. I am unable to find out what goes with the google pages (various devs mixed and matched google code and google pages-- http://kiwi.ds.googlepages.com/nsbmd.html http://kiwi.ds.googlepages.com/sdat.html )
http://techcrunch.com/2015/03/13/google-kills-off-google-code/
http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html

I do not doubt many of us have witnessed this a few times now (be it free hosts, ISP locked hosting, geocities...) but I must confess I had not expected it from google just yet.

From my bookmarks related to hacking, I have not checked all of them yet

http://code.google.com/p/editor-arquivo-bmg/downloads/detail?name=EditorArquivoBMG%20r22.jar&can=2&q=
http://code.google.com/p/loveemu/downloads/list http://code.google.com/p/loveemu/downloads/list?can=2&q=label:GameSys-NDS (loveemu has done an awful lot of work with sound formats on all sorts of consoles, and is/was instrumental in a lot of GBA and DS sound work, including updating VGMtrans though that should now be on github)
http://code.google.com/p/tinke/ http://code.google.com/p/tinke/source/browse/trunk/Plugins/Fonts/Fonts/NFTR.cs?spec=svn119&r=119 (tinke is an all in one DS focused hacking program)
http://code.google.com/p/puyotools/
http://code.google.com/p/dsdecmp/ (nice compression tools for the GBA/DS, including java builds. Superseded by http://www.romhacking.net/utilities/826/ for most people but still a nice program)
http://code.google.com/p/pyretic/ (not really ROM hacking but hey)
http://code.google.com/p/rawar/
http://code.google.com/p/lazynds/downloads/list
http://nvwr.googlecode.com/svn/trunk/libs/formats/
http://code.google.com/p/ismart-kernel/source/browse/#svn%2Ftrunk%2FARM9%2Fsource%2Fprocbody%2Fproc_GBA (some code for various things to do with the DS ismart flash cart)
http://code.google.com/p/tiledggd/ (one of my favourite tile viewers, probably the most extensible that I know of)
http://code.google.com/p/teapot-viewer/ (a general 3d viewer but a nice one people can twist to some of the more custom stuff seen in compiled games)
http://woodrpg.googlecode.com/svn/trunk/ (wood was based on the open source code from the acekard team, it eventually did lots like the akaio, woodr4 and more though several of those were closed source, I should have a tarball somewhere if someone wants it), they also released various DS ROM dumping tools.

https://code.google.com/hosting/search?q=ROM+hacking&sa=Search brings up a few more things

A lot of those are some very nice tools and format specs coming out of Brazil based hacking sites.

[BlackDog61]

  Many swear words come to mind...
Let the resistance to Git be!!! 

[ze10]

Someone could upload the romhacking-related tools to this website, right?

[90s Retro Gamer]

Why is Google Code shutting down? What reason did Google give for doing this?

Someone could upload the romhacking-related tools to this website, right?

I hope someone will do this. By the way, this is exactly the reason why a few months ago I advocated a complete RHDN torrent with all the dox, utils, trans, hacks, and homebrew available via P2P file sharing.  I was accused of "promoting hoarding" when instead if we had an RHDN torrent and this website ever went offline for whatever reason, all that data would be distrubuted and preserved. The only legitimate objection to my proposal was that it would be very difficult to get permission from every single content-creator on this website to distribute their files.

[hugues]

Google and GitHub are providing a tool to easily migrate projects over to GitHub. It only took about 5 minutes to move all tools I've built. Many of the other tools have already made the switch but you don't have to be the owner of the project to clone it in GitHub (Google only accepted open source projects in the first place). In terms of preservation I think it's better to export the projects to GitHub because it's accessible to a wider audience than torrents & file-sharing sites. I assume most would prefer to browse and view the source in their browser rather than download a point-in-time archive and hope it has what they're looking for.

[Bisqwit]

It is sad that some of Google's own tools are only hosted on code.google.com, such as this: https://code.google.com/p/googlecl/

Incidentally, this tool also uses a now-deprecated YouTube API...

[Chpexo]

.

[90s Retro Gamer]

Personally, I like sourceforge.net, but if you plan on making your utility closed-source, I guess it's not an option (although remember there are open-source licenses other than GNU-license)