Google to close Google Code open source project hosting

Google logoGoogle Code is to join the long list of Google projects that have been consigned to the dustbin of history. The open source project hosting service will no longer be accepting new project submissions as of today, will no longer be accepting updates to existing projects from August 24, and will be closed entirely on January 25, 2016.

A few recent actions by the company in the past months may have been harbingers of the closure. In December, Google moved its libphonenumber project for parsing phone numbers from Google Code to GitHub. Last month, the company released a new library for building distributed applications named grpc, and this too used GitHub, not Google Code.

For actively maintained projects, there should be ample time to migrate to alternative platforms. Exporting to GitHub is probably easiest, as Google has an export-to-GitHub tool. SourceForge has an import-from-Google Code feature, and there are also standalone tools for migrating to Bitbucket.

The bigger problem will be the projects that are in limbo. A common feature of all open source project platforms—SourceForge, GitHub, Bitbucket, Microsoft's CodePlex, Google Code, and every other—is that projects get abandoned. Developers get bored, busy, or feel that a piece of code is as good as it's ever going to be. The result is lots of projects that are no longer actively maintained. This, however, does not mean that those projects are no longer useful.

Google says that it will allow tarballs of projects (including source code, issues lists, and wiki pages) to be downloaded through the end of 2016. After that, however, it seems that the projects will be no more.

The company says that the closure is due to Google Code being inundated with spam and abuse and that these problems had come to dominate the workload of administering the service. When it was launched in 2006, there were fewer good project hosting options, but with services such as GitHub and Bitbucket now available, there's no great need for Google to have its own solution.

Source: Ars Technica

Tags: Google

Add comment

Your name:
Sign in with:
Your comment:

Enter code:

E-mail (not required)
E-mail will not be disclosed to the third party

Last news

Galaxy Note10 really is built around a 6.7-inch display
You may still be able to download your content
Facebook, Messenger and Instagram are all going away
Minimize apps to a floating, always-on-top bubble
Japan Display has been providing LCDs for the iPhone XR, the only LCD model in Apple’s 2018 line-up
The 2001 operating system has reached its lowest share level
The entire TSMC 5nm design infrastructure is available now from TSMC
The smartphone uses a Snapdragon 660 processor running Android 9 Pie
The Samsung Galaxy A5 (2017) Review
The evolution of the successful smartphone, now with a waterproof body and USB Type-C
February 7, 2017 / 2
Samsung Galaxy TabPro S - a tablet with the Windows-keyboard
The first Windows-tablet with the 12-inch display Super AMOLED
June 7, 2016 /
Keyboards for iOS
Ten iOS keyboards review
July 18, 2015 /
Samsung E1200 Mobile Phone Review
A cheap phone with a good screen
March 8, 2015 / 4
Creative Sound Blaster Z sound card review
Good sound for those who are not satisfied with the onboard solution
September 25, 2014 / 2
Samsung Galaxy Gear: Smartwatch at High Price
The first smartwatch from Samsung - almost a smartphone with a small body
December 19, 2013 /

News Archive



Do you use microSD card with your phone?
or leave your own version in comments (16)