Google Code transition:

• Google Code will close, with enough time to migrate projects.
• GitHub sounds like a logical choice.
• Price model is based on number of private repos, with unlimited collaborators.
• BitBucket is the other choice.
• Part of the Atlassian group.
• Private repos are unlimited even in the free plan.
• Price model is based on the number of users, with unlimited repos.
• A users is "someone with r/w access to your private repositories"
• Free model is up to 5 users.

Pros/cons:

• GitHub is more suited for high visibility + trivial project cloning.
• BitBucket is better for my personal stuff -- I want low visibility including private repos which I do not have right now.
• I don't need users (just me, maybe an rdrrlabs repo)
• With BitBucket, I might want to try to mirror my home repos as backups.

List of Google Code repos and migration path:

• Most of my GC repos are here to "reserve" a namespace and project name.
• Most of my GC repos are here to serve as an online backup. Many of them I do not wish to expose so I jungle around to only publish "public" stuff in them.
• This isn't needed in the GH or BB model since each project is under the user's namespace.
• I'd suggest going with BB because I mostly want private repos.
• Most repos would go into private mode for pure archival purposes, no activity.
• Check whether a repo can be changed from private to public at any time or is fixed.
• Only expose a minimal set of "useful" repos.