I think we'll be trying to take as much of that as possible into account as we figure out what people want/need to work on, and what their schedules are. I expect there will be an occasional problem with something along these lines, but hopefully participants will have a good handle on how much time they realistically have available.

On the other paw, I don't want to see this be a 12 month project. I think we've picked a project that's not so expansive that people will lose interest, nor so short term that it'll be done in a week (hope not, anyway).

Remember, we're going to try to go through all the steps that real programmers hate: planning, writing a specification, scheduling, code reviews, etc. We may hate that part in real life, but it's something that's all part of delivering a real-world project.

Along these lines, I wonder if we need a "motto" that reinforces that project is not an end to the means, but the means to an end.

--Chris