On 9/12/14 6:34 PM, Pete Resnick wrote:
On 9/12/14 1:55 AM, Stephane Bortzmeyer wrote:
On Thu, Sep 11, 2014 at 05:17:57AM -0700,
IESG Secretary<iesg-secretary(_at_)ietf(_dot_)org> wrote
a message of 69 lines which said:
Topic: IESG Formal Telechat
Date: Thursday, September 18, 2014
Time: 8:30 am, PDT (San Francisco, GMT-07:00)
The IETF being supposed to be an international organization, and the
event having no physical location, times should be announced *only* in
UTC.
Let's be clear: The IESG telechat is always held on a Thursday at 8:30am
US Pacific Time. When it is summer in the US (more or less), that's
15:30 UTC. When it's winter in the US (more or less), that's 16:30 UTC.
And the time of the meeting completely depends on the the US Daylight
Saving Time rules in effect at the time. Announcing it in *only* UTC
loses information, because you wouldn't be aware that the time is based
on US Pacific Time (even though for any single meeting, UTC is enough
information to know when that meeting is scheduled). Adding UTC to the
announcement would be useful.
Now, we could change things and schedule it in UTC instead. That makes
it a moving target for everyone instead of just some. Maybe that's
reasonable. (And when the IESG finally has members from east Asia or
Oceania, which it surely will some day, the schedule will surely have to
be revisited.) But I think given the current schedule, announcing it
*only* in UTC is the wrong thing to do.
pr
How about listing it in Pacific Time, and list the UTC converted time
and including that as well?
tim