Ole-Egil Hvitmyren wrote: [world time scheduling snipped]
In 5 hours I'll finalize the list, I have to be up at a bit before 6 so I won't be up after midnight ;-)
At the moment we have a couple of people who can join in at almost any time, I can join in during 5-6 periods, but not during office hours (I have a deadline looming. Eh, scratch that. I HAD a deadline looming. I'm already 11 days late. And counting ;-) ). We also have a couple of people who can only be there for 2-3 hours each evening (UTC). Since some of our offshorians don't have the same office hours as me, it doesn't like like there'll be more than at most 4 people in a session at ANY point during the 60 hours from wednesday evening UTC to saturday morning UTC.
This is BAD, people. If it doesn't improve, I'm not going to spend another minute trying to organise any of this crap.
Ok, this needs to be got out of the way. Doing virtually _anything_ on a '24 hour turnaround' involving a group of people spanning time-zones is rarely if ever a real possibility.
Adding to that, is personal email access from work- not all of us have it, and the occasional few that have a life as well ;-)
Any 'global' projects all have these same issues...accepting them now and extending anything you're 'like' to see happen in 24 hours to 72 hours generally improves everything, including responses.
Taken unfortunately, from prior first hand experience with a global dev team... :-(
Scott