Czarek wrote:Google Code developers didn't think it thorough. The "Export to Github" button is available for any visitor and with two clicks anyone can duplicate all project content including all issues and wikis (it's a lot more than just clone). There will be so much duplicated content on the net. And you can't disable this button, just great.
Yeah, it's not great, but I can understand Google's motivation. It seems that there are quite a few projects on Google Code that have been abandoned and this is an easy mechanism for people to make a copy of that project's content before it disappears.
For CEF/JCEF this is what I'm doing to document the project's move to a new "official" location:
1. Project main page -- Add a message explaining that the project is moving with a link to this forum post and the new host location.
2. Source -- Create a "Source" Wiki page that links to the new host location and use it to replace the default tab destination via Administer > Tabs.
2. Issue Tracker -- (a) For each open issue add a comment linking to the same issue in the new issue tracker with instructions to Watch that issue for further updates; and (b) Create an "Issues" Wiki page that links to the new host location and use it to replace the default tab destination via Administer > Tabs.
4. Wiki -- (a) For each document replace the content with a link to the new Wiki document location; and (b) Create a "Wiki" Wiki page that links to the new host location and use it to replace the default tab destination via Administer > Tabs.
5. Project main page -- After everything else has moved replace the main page content with a short description of the project (for search engines) and a link to the new host location.
If someone uses the "Export to Github" button after the above process is complete they'll get content which is mostly just links to the new host location.