On Apr 2, 2011, at 6:53 AM, Jeremiah Foster wrote: > On Fri, Apr 1, 2011 at 8:31 PM, Foster, Dawn M <[email protected]> > wrote: >> I wanted to let everyone know that we have a new time for our Technical >> Steering Group meetings. While the 20:00 UTC meetings were convenient for >> the Americas and Europe, it was very difficult for people in Asia to >> participate. > > Can you explain the decision making process behind this decision?
Here's the logic ... Needless to say, scheduling global meetings is challenging, and the time will be inconvenient for some set of people in order to be able able to include a majority of time zones. Clearly, our previous TSG meeting time, 20:00 UTC, Noon Pacific and 2:00 / 3:00 am in eastern Asia was making it nearly impossible for people from Asia to attend, and the TSG had been receiving requests to move the meeting to a time that was more Asia-friendly. I sat down with a spreadsheet marked with times for US west coast, western Europe and eastern Asia, which seems to be where most of the people working on MeeGo are located, so I tried to optimize for these 3 locations. I put standard working hours in green, yellow for times 2 hours outside of working times and red for everything else. Since we've (U.S. west coast) had the meeting in the middle of our workday up to now, we thought it was only fair to give us the red time (now 11PM), western Europe was yellow / green (6am / 8am for most people) and green for Asia (2pm / 3pm for most). The other time we considered, based on the red / yellow / green chart, was 6am pacific, 2pm / 4pm western Europe and 9pm / 10pm in eastern Asia. In this scenario, Asia would again get the most inconvenient time, which did not seem fair to me. I see this not as something that gets decided once and never changed. I expect these meetings to move around in time to share the burden of early / late meetings and to adapt to locations where we have people working on MeeGo. > > Naturally MeeGo needs to have times that are friendly to all regions > but this decision seems to have been made without any consultation > whatsoever with MeeGo developers. > In all fairness, I did post this new time to the mailing lists almost 2 weeks in advance of the first meeting to give people time to ask questions or voice objections. If you have a better time that works for more people than the current time, I encourage you to propose it. Regards, Dawn _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
