4 ms·
Please can you add a way for projects on google code to do a redirect to wherever they have gone. I moved all my projects late 2013, put notices on all pages I
by rogerbinns 12y ago
Please can you add a way for projects on google code to do a redirect to wherever they have gone. I moved all my projects late 2013, put notices on all pages I could etc, but still searching for the project often shows the google code site first.
https://code.google.com/p/apsw/ 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.
- tjohns 12y agoGoogle 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 http://code.google.com/p/iosched
- rossj 12y agoThat'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.
- Someone1234 12y agoThey also should be returning a 301 and the new URL so crawlers can follow it and delete the old site from their records...
- qnaal 12y agohttp status codes are so web 1.1
- AnAccountNow 12y agoWhy would they make it easier for someone else to properly index the web? They've got that covered.
- arcatek 12y agoThey 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.
- rogerbinns 12y agoThanks - I never knew that existed. The admin ui and result aren't particularly nice sadly.
- z1mm32m4n 12y ago> 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.
- rogerbinns 12y agoThis 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.
- abraham 12y agoYou can reference issues in any repo with "ref username/repo#73"