Move to another site like GitHub or SourceForge?

[GoogleCodeExporter]

I just realized that soon Google Code is being shut down. I didn't see anything 
about it anywhere on this Google Code page, so I thought I would mention it 
just in case. I really like this, and would like to contribute and stuff, but 
we should migrate to something else soon.

March 12, 2015 - New project creation disabled

August 24, 2015 - The site goes read-only, can still checkout/view project 
source, issues, and wikis.

January 25, 2016 - The project hosting service is closed. You will be able to 
download a tarball of project source, issues, and wikis. These tarballs will be 
available throughout the rest of 2016.

I just want to make sure the project doesn't just disappear one day, or that 
everything is lost.

Thanks and hope to hear from somebody soon.

Original issue reported on code.google.com by [email protected] on 26 Mar 2015 at 11:08

[GoogleCodeExporter]

adelikat approved of moving, but where should we move? I've never dealt with 
GitHub (and adelikat had problems with moving there), but I have successfully 
moved my own project to SF.

Original comment by feykomylce on 31 Mar 2015 at 6:34

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I have accounts on both, so either would be fine. I also had no issues 
migrating my projects to GitHub, but I didn't try moving them to Sourceforge. 
Whatever is chosen, switching to Git would be a huge plus.

I will try exporting to GitHub too just in case; if it fails, git-svn can be 
used to generate a Git repository, then it can be uploaded to GitHub by 
creating the project there, swapping the remote and pushing.

Original comment by [email protected] on 31 Mar 2015 at 6:44

• Added labels: ****
• Removed labels: ****

[DerekTurtleRoe]

Should I start with a single project or do it all at once?

[vadosnaprimer]

feos here whatsup

[marzojr]

Invited both of you; remeber to adjust your watchlists after accepting the invitation.

@vgturtle127 you can do whichever way you think will be easier; I imagine it would be 'all at once'.

[vadosnaprimer]

Are you planning to copy uploads here?

[marzojr]

It would be desirable, yes, but I think only the more recent release of each would be the way to go.

[DerekTurtleRoe]

When you say "uploads" you mean all the binaries in the Google Code downloads section right? Just making sure.

I will start forking the projects and making some changes ASAP. :smile:

By the way, we should see about creating a few Wiki pages for each repo that detail how to use the emulators for TAS/speedruns/recording/whatever and also maybe a compatibility list. I have every ROM for nearly every system and a few emulators per system, so I can try to do that in the future too, but of course I don't necessarily have every ROM, or every version of every emulator. So, you know, it would be nice if other people would test them too. :P

[vadosnaprimer]

Yeah, binaries/releases/downloads/whatever.

Wiki: don't overdo, just link http://tasvideos.org/EmulatorResources/Using.html :)

[marzojr]

@vadosnaprimer As I mentioned to adelikat, you need to accept the invitation before you are actually added; if you didn't receive the e-mail, then you can go here to accept it: https://github.com/TASVideos

[vadosnaprimer]

Thanks, accepted.

[DerekTurtleRoe]

@vadosnaprimer Those are fairly generalized instructions. I was thinking more like step by step instructions for each emulator, with images. But if you guys don't think that's necessary, then I will focus on everything else. Compatibility lists should still be maintained, that way if a game doesn't work, then we know what game, what problem, and we can fix it for better TASing and whatever else.

Or just so people can play games and record them for longplays or whatever. :smile:

I am making and testing changes locally at the moment.