New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to another site like GitHub or SourceForge? #116
Comments
Original comment by
|
Original comment by
|
Should I start with a single project or do it all at once? |
feos here |
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'. |
Are you planning to copy uploads here? |
It would be desirable, yes, but I think only the more recent release of each would be the way to go. |
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. 😄 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 |
Yeah, binaries/releases/downloads/whatever. Wiki: don't overdo, just link http://tasvideos.org/EmulatorResources/Using.html :) |
@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 |
Thanks, accepted. |
@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. 😄 I am making and testing changes locally at the moment. |
Original issue reported on code.google.com by
vgturtle...@gmail.com
on 26 Mar 2015 at 11:08The text was updated successfully, but these errors were encountered: