Move to GitHub (and transition to a Git repository)
Opened this issue · 4 comments
GoogleCodeExporter commented
Collaboration features provided by GitHub appear to be better than Google
Project Hosting.
Required tasks:
* Migrate the repository from Mercurial to Git.
* Move the source code hosting to GitHub
Considerations:
* Changing the POM's "scm" location to GitHub
* This may be best performed when moving to 0.5.0, and perhaps changing the artifactId to 'net.coobird.thumbnailator'
* What to do about Issues?
* Migrate to GitHub? Keep them on Google Project Hosting?
Original issue reported on code.google.com by coobird...@gmail.com on 8 Sep 2013 at 5:24
GoogleCodeExporter commented
Move to GitHub. Best repository.
Original comment by rajku...@vivareal.com on 24 Oct 2013 at 9:57
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
Any plan to move to Github. In my opinion it's much better in collaboration.
Original comment by sachinwa...@gmail.com on 18 Jun 2014 at 9:06
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
Move to GitHub asap
Original comment by pba...@gmail.com on 14 Jan 2015 at 9:26
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
Google Project Hosting will close, going read-only in August 2015.
http://google-opensource.blogspot.jp/2015/03/farewell-to-google-code.html
Extremely critical to move to a new provider, with GitHub being the most likely
candidate.
The export tool (http://code.google.com/export-to-github) provided by Google
will allow migration of issues as well, so that should be fairly simple.
Original comment by coobird...@gmail.com on 13 Mar 2015 at 11:29
- Changed state: Accepted
- Added labels: Priority-Critical
- Removed labels: Priority-Low