+1 (that´s what meant in the first place)

Git has support for tags directly, which should be used instead. Branches are better for extra features (eg the inventory system should happen in a secondary branch and be merged back into master once its done).

I would also like to see people to use their own forks and submit pull requests instead of giving them direct commit access, obviously that would also imply some kind of peer review by the project maintainer.

I think we are just a bunch of git newbies, so maybe you could write some kind of short tutorial here. Would be awesome!

It is funny: in the moment someone wants to build something code related, everyone gets uneasy about coding- and naming conventions.

My advice for you would be to take it easy and work in short, but intensive sprints. Everyone gets a task to write this and that in the next 2-4 weeks and then you invest one week into refactoring and making it pretty and stable. Then you release it.

There have been lots of great git tutorials that cover it much better than I could ever do. Give this one a shot, it covers the philosophy of git exceptionally well: http://www.jayway.com/2013/03/03/git-is-a-purely-functional-data-structure/

OT: I wonder if the decentralized structure is the only big "advantage" of git. If yes, I don't like it The idea of branching, merging and RCs is not new and for SVN management there exist better tools.

I uploaded a simple inventory and a logging library. Movement code is next!

No, but it's one of the key features that make it much more flexible than SVN. And you don't have to put advantage in quotes, it is a tremendous advantage over SVN

Quotes, that's my way of teasing people Maybe I'm already too old to willingly switch to new technologies...

Damn old people!

Hey, wasn't there a project called TUSC many years ago back in the A5/6 days??? I think it was The Ultimate Script Creator, or something if I'm not mistaken. This obviously just reminded me of that haha