Re: [Manycouches] many-fine-dinners --- a view on how to organize virtual meetings

[Michael Richardson <[e-mail]>]

Michael Richardson <[e-mail]> wrote:
    md> 4. *More days*: This would increase the true cost to employers, compared to
    md> an in-person meeting, if it were any more than about 7 working days. I
    md> believe, without any evidence, that holding sessions over the weekend would
    md> be a non-starter for participation.

    > So I wrote "4-7 days", for two reasons:
    > 1) because we have 7 day physical meetings, and maybe someone wants to push.
    > 2) because we might want to pad the actual schedule so that people would
    > have some recovery time.  This is consistent with people claiming travel time.

So to followup to myself:   we recently declared that IETF started on
Saturday morning.
We did this, I think, so that people would more easily be able to justify
being at the Hackathon, Tools Sprint, IEPG, training sessions.

As I've written earlier in another thread, among the many other things the
in-person Hackathon does is serve as a bit of an immersive group forcing
function to get people into the right time zone.

I was mostly successful in managing my time zones, but I couldn't stay awake
past 1400UTC (9AM), having gotten up around 2000UTC (3PM) the previous day.
Friday, I knew I was going to be a write-off, and it was.
Maybe I should have found a hotel room.  Saturday was also mostly a write-off.

I'm sure that I'm not the only one who needed recovery time after this "travel"
The question is: how can we, when we write the schedule, make this really
clear to managers?  (many of whom probably didn't notice the "UTC" on the schedule)

--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide