Re: WG meeting structure

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 May 2019 19:50 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C81312008A for <wgchairs@ietfa.amsl.com>; Wed, 15 May 2019 12:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xLK6P_R1Mky for <wgchairs@ietfa.amsl.com>; Wed, 15 May 2019 12:50:34 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8AD61200B1 for <wgchairs@ietf.org>; Wed, 15 May 2019 12:50:33 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 0F9A33826C; Wed, 15 May 2019 15:49:47 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id DED72E3B; Wed, 15 May 2019 15:50:31 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DC5F2A2; Wed, 15 May 2019 15:50:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
cc: Pete Resnick <resnick@episteme.net>, "STARK, BARBARA H" <bs7652@att.com>, IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: WG meeting structure
In-Reply-To: <CAHBDyN7jLAq-aSVUTN9iMw5xFp5VDyTY66y55KvX0eWG+CzKiA@mail.gmail.com>
References: <61D81D11-1BA0-4123-80C9-C7A97297ED5C@episteme.net> <BF668B4C-6D67-4D7D-A31F-C24523F04EB2@gmail.com> <c3469366-323a-4c15-a504-51e059660ac1@www.fastmail.com> <2D09D61DDFA73D4C884805CC7865E6114E18C7CF@GAALPA1MSGUSRBF.ITServices.sbc.com> <13571.1557928942@localhost> <2D09D61DDFA73D4C884805CC7865E6114E18CB6B@GAALPA1MSGUSRBF.ITServices.sbc.com> <B33D6B58-9C11-4ED9-8962-8DFFBC8D92EB@episteme.net> <CAHBDyN7jLAq-aSVUTN9iMw5xFp5VDyTY66y55KvX0eWG+CzKiA@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 15 May 2019 15:50:31 -0400
Message-ID: <8520.1557949831@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/v4NhZSLt3LlbRskMqDqRcWd_6CA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 19:50:37 -0000

Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
    > I think the suggestion to have more interims is a good one. The only
    > challenge there is time zone bias. For example, even if you do a Doodle poll,
    > the majority might be one timezone which disadvantages those in a completely
    > different timezone (e.g., North America vs Asia). One group I worked in had
    > the requirement that we rotate through time zones - we picked a time for each
    > major region. The downside of course is that if there's no one in the
    > timezone you're accommodating, then it's really, really annoying.

It would be interesting to have a survey of IETF contributors to understand
what time is best for them.  Despite time-zone issues there are some other
issues with AV online meetings:
  1) some have no microphones/headphones at work
  2) some have microphones at work, but no quiet space
  3) some have too many state firewalls to permit them to work at home,
     in the evening.
  4) differences in work week days

I wonder if we could add this to the next meeting survey?

    > Certainly, there are ways to improve meetings. I do think it starts with the
    > chairs, then participants and then meeting room setup (and don't forget
    > potential impacts of the HVAC system and staff working behind the meeting
    > rooms that can have a significant impact on audio quality). In my experience,
    > you need a chair that has a lot of experience chairing meetings with the
    > U-shape setup to be effective for both in room participants and remote -i.e.,
    > zero tolerance for cross talk. I will also add that some folks have more
    > difficulty following discussions when there are side discussions (which are
    > more common with U-shape, in particular, when you're trying to ensure that
    > everyone has access to a microphone. So, you'd also need participants to mute
    > the nearby microphones when they are not speaking. And, actually studies show
    > that women have this problem much more frequently than men - there is
    > research showing that the auditory processing in the brain of men and women
    > is different. So, that might well be why I have difficulty with this style of
    > meeting that isn't extremely well managed. I've been on conference calls
    > where there's a lot of folks in the room and I seem to be the only one that
    > can't follow the discussion due to cross talk and poor moderation of the
    > discussion, which is why I wondered and did some research about this
    > potential difference. So, given that we have so few women, even if we
    > experiment, there will likely be a bias in the conclusions.

So the prediction is that if we try this with people who haven't done it
before, then it will fail.  But how can we get trained better if we don't try
it?  Can we go learn how to do this elsewhere?  (where?)


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-