Difference between revisions of "Google Code"
(Link to blog post announcing closure) |
(Link to migration tool) |
||
Line 14: | Line 14: | ||
== Vital signs == | == Vital signs == | ||
Closing on 25th January, 2016<ref>[http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html Bidding farewell to Google Code]. | Closing on 25th January, 2016<ref>[http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html Bidding farewell to Google Code]</ref>. | ||
== Archiving == | == Archiving == | ||
Line 20: | Line 20: | ||
Archiving bugtrackerss and the other stuff is a bit harder | Archiving bugtrackerss and the other stuff is a bit harder | ||
A tool to export a repository to GitHub is available<ref>[http://code.google.com/export-to-github Export to GitHub - Google Code]</ref>. | |||
== References == | == References == | ||
<references /> | <references /> |
Revision as of 16:34, 12 March 2015
Google Code | |
URL | Google Code[IA•Wcite•.today•MemWeb] |
Status | Closing |
Archiving status | Not saved yet |
Archiving type | Unknown |
IRC channel | #archiveteam-bs (on hackint) |
Google Code (AKA Project Hosting) is a software repository that is owned by Google. It hosts only open source software paired with an open source license.[1]
Google Code allows people to commit their code into either a Subversion (SVN), Git or Mercurial repository. It has a downloads section for people to upload their software packages (with a quota limit of 4GB, can be increased upon request) and also a wiki for projects to document their work at. There is also an issue tracker to track bugs in the project's software.
Vital signs
Closing on 25th January, 2016[2].
Archiving
By definition of a repository, archiving copies of the source code is rather easy (and incremental). Just clone the git/hg repository, or checkout SVN repo. For SVN, make sure that you checkout all branches, nut just trunk.
Archiving bugtrackerss and the other stuff is a bit harder
A tool to export a repository to GitHub is available[3].