Google Code already has an option to flag a project as moved. From your project: Administer > Advanced > Project Moved
For an example of what this looks like: http://code.google.com/p/iosched
That's great, until code.google.com no longer resolves, at which point it won't help :( Would be nice if they used that info to automatically redirect to the new site.
They said they would on the blog post
I work on Google Code, and we will be putting a service in place to redirect
deep links to project homepages, issues, etc. to their new locations.
Projects on Google Code will need to set the "project moved" flag, under the
advanced tab of the project. But once set, things should work like you
expect.
Re:Bidding farewell to Google Code
by Someone1234 on Thursday March 12, 2015 @02:02PM
(#9192552)
They also should be returning a 301 and the new URL so crawlers can follow it and delete the old site from their records...
Re:Bidding farewell to Google Code
by AnAccountNow on Friday March 13, 2015 @12:49AM
(#9195716)
Why would they make it easier for someone else to properly index the web? They've got that covered.
Re:Bidding farewell to Google Code
by rogerbinns on Thursday March 12, 2015 @01:51PM
(#9192491)
Thanks - I never knew that existed. The admin ui and result aren't particularly nice sadly.
> Github for example only lets you have one source repository per project, and as a result the wikis and issues are useless since they are almost always filed against the wrong sub-project.
You can disable the wiki and issues pages on a repository-by-repository basis. If you're looking to solve the issue of issues being filed in the wrong place, you could try to pick the component that is the most central or most front-facing and only leave that wiki or issue tracker enabled. Then you'd just add a simple note in the README of the other repos about where to go to report issues or read documentation. It's definitely not the same, but it is a somewhat elegant workaround.
Re:Bidding farewell to Google Code
by rogerbinns on Friday March 13, 2015 @12:23PM
(#9197977)
This doesn't help for the issues. With commit messages you can reference or close tickets (eg "fixes #73"), but that won't be available if committing, unless in the one repo that does have issues enabled.
https://code.google.com/p/apsw/
Google Code did one thing very well - each project could have one wiki and issue tracker, but any number of source code repos. This is fantastic for projects where there are multiple parts - eg an Android client, an iOS client, multiple server parts etc. Github for example only lets you have one source repository per project, and as a result the wikis and issues are useless since they are almost always filed against the wrong sub-project.
Every startup I have been involved in over the last many years used Google for business (users, groups, office stuff etc), but then for code hosting we were forced to go elsewhere, needing yet another set of user accounts, groups, admin, billing etc. There was a ticket begging to let folks pay for google code, but it never came to pass. All the startups would have gladly paid, especially to avoid dealing with multiple accounts, sites and admin. Some features like the issue tracker were quite good. Heck you could even prioritise issues - something github still didn't have the last time I looked.