Slashdot Mirror
Google Code Disables New Project Creation, Will Shut Down On January 25, 2016
An anonymous reader writes GitHub has officially won. Google has announced that Google Code project creation has been disabled today, with the ultimate plan to kill off the service next year. On August 24, 2015, the project hosting service will be set to read-only. This means you will still be able to checkout/view project source, issues, and wikis, but nobody will be able to make changes or new commits. On January 25, 2016, Google Code will be shut down. Google says you will be able to download tarballs of project source, issues, and wikis "throughout the rest of 2016." After that, Google Code will be gone for good.
It is nothing but an adware site if you try to download on windows now. Completely irresponsible management of what is little more than a husk.
If you have code in Google Code, read through the comments in the first link - there is some important Q&A going on there, including a flag you can set in advanced project settings when you've migrated off Google Code, that will forward on links looking at Google Code to the new home...
I didn't see it stated explicitly but I'm thinking they are only supporting migration to GitHub for forwarding compatibility? I don't have a Google Code account so I can't check what the setting says it does.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
The "D" is for Distributed. Git doesn't require you to use a single server; it's pretty much trivial to move your project history from Github to a competing service, since you're copying the entire project history every time you clone your repo anyway. So even if Github instantly vanished tomorrow, all the project authors would easily be able to re-clone their repos on a different service. That's the advantage of DVCS.
There's Google's own 'google code project' for that .....nice.
Sourceforge already has one, FYI.
Open Source Network Inventory for the masses! Kuwaiba