Paradox wrote:Actually, a release schedule might be good for getting people motivated (myself included).
Actually I already have a deadline for v1; it's january 2008!
Shall we aim to have a release (with wavesets!
) by the end of August? That gives people a chance to submit whatever they've got just before school starts back up.
Shells expire in November, so perhaps another release at the beginning of January (after the Christmas break) would be good?
As far as I am concerned I stopped believing long ago that deadlines could be set for personnal projects, especially when several people are involved. However I do believe in the help of the all-mighty todo lists.. Getting to know exactly what's left to be done, and writing it in a public place, is a good way to move forward and motivate oneself. (So that people can point fingers at you and throw stones at you -- at least it works pretty well for me
Also on such a large project it's almost mandatory to have some form of project/assets management tracking. I've had a number of those on paper for AP over the years. (paper
, I know; somehow I tend to work on AP a lot when I'm travelling and I didn't always have a laptop). Maybe it would be time to gather those and get them online..
Would it be useful if I put something together on the Wiki?
Deadlines only tend to really work when there's something
at the end of it (which is why the RAD contest worked so well). Right now if Cyan told us "we'll start integrating fan Ages in MOULa by [insert date]" I'd put all my other Ages and Huru works on hold and work all nights long on AP..
That being said it doesn't hurt to aim for some form of date.. And several of us will indeed have more free time in the summer..
Corvus wrote:I love deadlines. I like the whooshing sound they make as they fly by.
I will totally nod in agreement to this.