mrout wrote:radar37: You know the plan of action.
Really? I'm here every day and I don't.
mrout wrote:Prototypes. Milestone 1.
Prototypes of what? What is milestone 1 supposed to accomplish?
(OK, so milestone 1 consists of exactly one goal that can be done badly in an hour and could be done well in anything from a month to several years. Also why doesn't this forum support strikethrough?). I think you assume that a lot of the vision you have in your head or the shared knowledge gleaned by extensive reading and posting on these boards is more widespread than it is.
Also, are you trying to convey the idea that a bunch of prototypes add up to a milestone? Because they don't. Prototypes should be lightweight and implement just enough to demonstrate a given mechanic. They can be as simple as a pen and paper implementation of a game mechanic to see if it's fun / workable. A milestone, to me, is a functioning piece of software that hits at least a few of the major design goals.
mrout wrote:We should have been there within days of the start of the project.
If you're frustrated by lack of forward movement you need to start subdividing tasks into smaller ones that people are more likely to pick up. You also need some mechanism for people to find well defined tasks and report that they're working on them (see my other thread asking for a backlog and more distillation of tasks on the wiki). Right now there's not even a 'how can I start to contribute?' page. That's actually way more a part of a dev lead's job than writing actual code. This goes back to an earlier point I made about removing roadblocks in the way of developers. You're going to want an army of developers at all levels of skill and levels of interaction, not just 5 guys who spend all their time on the IRC channels and these forums.