There is one issue I still fear may be a bit of a bikeshed.
What to name the game, repository, project...?

My best idea so far, according to myself, is Cumulate.

Nice suggestion. But I'll go with Cumulate for now.

I have created a repository now.
http://github.com/trezker/Cumulate

I've just put in the minimum code to create a window and close down on the display close event.

So, if you're interested in adding your own feature.

• Fork the repository and make sure you can build and run it.

• Send me a message. (github inbox preferably)

• Wait for me to tell you it's your turn.

Any feedback on how I have organised this thing is welcome.

The repository has been up for almost a day now, no one has reported their interest in taking a turn yet. I'm feeling antsy.

I've thought about starting a new thread for discussing the project itself rather than its format. But there's not much to discuss before it has at least one feature in place.

So step up and make the first feature! You have the chance to make a big impact on what direction this project will go.

Just send me a message saying you'd like to add something to the Cumulate project.

Ouch! Haven't touched A5 yet. Anyway, would be fun to join, but at the moment I have absolutely no time.

It died, and the SVN repo is used for the A5 version of MaSKING.

Good practice for your imagination then.

But it is true that given complete freedom and being asked to choose just one feature to implement is too open.

I think you should just imagine a full game you'd like to make, then pick the first feature that should be implemented for that game. The game you imagine probably wont be the end result of the project, it's just a helper to get it started.

Roll some Speedhack rules if your brain fails.

Would it be against the forum rules to have that here? Most of the people here are quite eloquent and intelligent(for internet standards ). It would be an awesome story with romance, action, orcs, Dr.Who, Linus Torvald, captain Piccard, time-travel... NVM
I think the 'finish-the-game-together' game would work best if there was a grid set-up beforehand f.i.

Assignment     | Assigned to
Splash screen    n/a
Level structure  n/a
* level 1        n/a
* level 2        n/a
World structure  n/a
Extra feature 1  n/a
etc.

This is mainly because IMHO a bunch of text written is always a readable story, but a game needs a lot of writing before it is playable... Just a suggestion though. But pinning down the complete game beforehand is just no fun at all IMHO.

Well... oh well.:)

So, I have Code::Blocks installed, I have installed the correct a5 binary (4.9.21), installed git and premake4. I have retrieved the repository, created my cb project files. When I go to compile it, it attempts to link to -lalleg, which isn't quite right, but nothing to worry about.

Is there anything else I need to know/setup before I get started? or am I good to just wait for my turn?

(I will worry about learning to commit when I come to that.)

I thought of finally take a look at A5. I guess A4 won't interfere, if I only keep them separated. But I don't really know what I should install. Any external libs I should install before even trying out anything, in general and for this Cumulate project in particular? Yeah yeah, just friendly google it! But the first I run into is this:

Well, I'm not planning on helping with development of A5. Simply because I lack skills and knowledge.

I have Dev-Cpp on my machine and it works very well. I dont use it on a level, where its crappiness would disturb me.

They're listed in the documentation.

It's fine. That's an old statement, I think.

Yes.

To make your build system robust and portable, you should always link to allegro-main. Won't do anything on Windows or Linux, but it's needed on OS X and iPhone.

Yeah, I think the people here are broken

I've been thinking about putting in the first feature myself. I wanted to give others a chance to do it since I already took the liberty of deciding to go with A5 and which build system to use. Not to mention the game rules and version control system.

But now that it's taking so long for anyone to volunteer, I'm more likely to go ahead and implement a feature myself.

Some people have expressed that they would like a starting point with more substance, something to build onto rather than conjure something from the void.