You guys should make an SFML one after you finish this one, there aren't that many good (or at all really) examples and it would be a great example to learn from.
I'll try this.
Have somebody else ready in case something else comes up.
So... who starts?
I'd like to help out.
I think garry should start! (It was HIS idea)
Vote me in.. Requires me to learn LUA though, but should be possible :)
Count me in.
Make a game about punching faces.
(I know this post will cause a shit storm)
But. I've setup a svn on my own server just to keep versions even if that person does not want to use it. I'll add it in anyway.
fuck off you git
How about the old fashioned stick it all in a rar, dropbox/mediafire it and post it on the thread?
None of this version control shit.
I don't possibly see how we need a website, unless that's your contribution then if it is you're already off the list.
I say just create a local git repo in the root directory.
Anyone who thinks they're infallible can simply ignore it and the next person in the chain can commit their work.
So do we still need a team or are we just gonna start and see where it'll end?
This project shouldn't die.
I think that we should go without version control because everyone would probably want to use a different version control system anyway.
we need version control simply because someone might throw in some obscure bug and we want to see the exact changes made to the project
Well everybody is going to have one turn with the code right? So everyone that wants can just commit every turn in their favorite source control system so we have multiple source controlled backups.
That might work. Every turn could be uploaded as a zip file and then everyone could commit it locally to their favorite version control system.
If they want to use version control at all.
We could make a bitbucket repo and have the next person be added as a contributor and the previous person taken off every time. That way they could use svn/git/mercurial locally and then upload it to bitbucket when they're done (because bitbucket allows you to convert svn to mercurial or git).
A local git repo in the folder is the simplest solution. Solitary git repositories work just like SVN ones, and has the greatly added bonus that no user management is required - it uses the user info from each person's computer when they commit.
the fact that you guys are still even talking about whether or not you should use revision control shows how efficient this is running
It's all garry's fault why did he start this mess.
The second most important part in programming, after choosing version control, is choosing a license.
Once you've chosen both of those, you're 90% done. Then you choose which coding practices and comment formatting to use, and the project is totally done. It's time to release.