Spring RTS Engine

http://google-opensource.blogspot.co.uk ... -code.html

In short:

• March 12, 2015 - New project creation disabled.
• August 24, 2015 - The site goes read-only. You 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.

Which Spring projects need to move / need archiving on GitHub?


If https://springrts.com/wiki/Gamedev:PublicRepos then at least:

Air Raid, BOTA, CT, JW, Spring Tanks, Spring Tutorial Game & XTA

March 13th 2015: Google buys github, annouces plans to integrate with Google+

Doing a google search for "googlecode springrts" got a couple more, maybe abandoned:
https://code.google.com/p/crans-java-ai/
https://code.google.com/p/darius/

Fooo....

I had that nice Googlecode Account with 4 Gigs of Store... and now of all things Git.. with its tremendous joys..
I dont want to hear its feature rich.
Its bad to use. Especially for new users.
Even with Gui.


It also is not made for mixed (binary) and source projects.
So its goodbye Tortoise SVN..
Fooo..

Summer Concentration Camp of Code came early this year.

Same here, although git is nice for some projects, I also like subversion because of its central control.
There is of course also bitbicket and sourceforge, but I guess most of us will choose git. There is a button for that already.

I think i just move my dev svn into the release branch on bit-bucket.

agile developement: Nobody uses your product, so you can do whatever the hell you want until money runs out or the heat death of the unniverse

https://bitbucket.org/PicassoCT/journeywar

I think for spring that changes nothing, - except the wikki linking could be brokken.
And a lot more not working, shaddy jw releases are going to pop up in rapid

PicassoCT wrote: https://bitbucket.org/PicassoCT/journeywar

Why did you choose bitbucket over github for a git repository?

Does anyone have any best practises recommendation for those of us who are using tortoise svn and a subversion repo? I know it's easy to convert the repo to git, but making tortoise git work is *not* easy. I would like to not mess up my ssh keys if possible.

What about the option to use a mercurial repo?

I use the command line, it just works best for me and I don't have to relearn the GUI every time it changes.
I'm not sure what difficulties you have with tortoise git (I last tried it about a year ago and had no issues), but you may want to try Github for Windows -> I personally didn't like it, but iirc some people (FA) who used to dislike git did.

The choice is yours of course, but unless you have valid reasons, I find it odd to not use git and in particular github. This is what most open source/Spring devs use and the tendency everywhere is to move to it*.

Bitbucket/other alternatives make sense if you want to keep it closed sourced or something else, but that's unlikely here.

*This isn't just a popular opinion. For example: the only supported VCSs for rapid are SVN and Git. Github has excellent commuication tools, you can pretty much consider it the social network for programmers.

The problem with git is that we have an enterprise account there too, and I don't want to mess up the keys. I've tried with github for windows, git bash and tortoise git, and they use different ssh-standards and keys, and last time I tried to commit something related to spring it used my enterprise account keys.

For windows users averse to command-line I can't recommend SourceTree enough:

https://www.atlassian.com/software/sourcetree/

The only downside is lack of shell integration but you'll soon get over it.

It is much better than GitHub 4 Windows.

Using it - still not near as good as tortoiseSVN

Picasso, it's way better than svn. Just has a stupidly huge learning curve.

If any windows users would like an intro to using git on windows, I will do a livestream on twitch on it that will help you all out, as I had to more or less teach myself in a single day due to a new job (it was a really bad day lol).

But I learned a lot and I have some gorgeous dev environments set up for it that will make your life 505005005050x times easier.

Let me know if interested. This is one area where I can help out quite a lot as I was forced to approach it as all of you are having to do right now, and it sucked, but now that I understand it and know it, I love it.

PicassoCT wrote:Using it - still not near as good as tortoiseSVN

No mention here of tortoiseGIT?

I use that, in combination with commandline gitbash.

I use TortoiseGit.

But then again I also use an aftershave lotion called semprini!

A friendly reminder, all GitHub repos are SVN compatible, all this talk of TortoiseGit and switching to git is unnecessary, always has been

AF wrote:A friendly reminder, all GitHub repos are SVN compatible, all this talk of TortoiseGit and switching to git is unnecessary, always has been

wrong: the github svn "bridge" lacks some features. i.e. direct svn mirroring doesn't work, this is why it was a must to implement git support for rapid.

FLOZi wrote:For windows users averse to command-line I can't recommend SourceTree enough:

https://www.atlassian.com/software/sourcetree/

The only downside is lack of shell integration but you'll soon get over it.

It is much better than GitHub 4 Windows.

I wholeheartedly disagree, the best Git GUI is SmartGit

http://www.syntevo.com/smartgit/

Tbh you're far better off using a good command line console replacement for windows and using mysysgit and command line.



Much easier to use, the hard part is just understanding how git works compared to svn and other repo tools.

I figured that back in the MyUPB days we used cvs, so if I can figure out cvs and make it actually work, git should be easy lol (that said, i hated git for a full 24 hours while I was learning it... it is the most noob unfriendly versioning system in existence... but it also happens to be one of the coolest/most useful once you learn it).

Especially if you add aliases, so most commands become:
git ci, git co, git st.
Pretty neat and fast!

alias inflict="git push"