Re: WG meeting structure

Wes Hardaker <wjhns1@hardakers.net> Sat, 18 May 2019 14:27 UTC

Return-Path: <wjhns1@hardakers.net>
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 474E812023B for <wgchairs@ietfa.amsl.com>; Sat, 18 May 2019 07:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 Y0H24K3wItpY for <wgchairs@ietfa.amsl.com>; Sat, 18 May 2019 07:27:17 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C54A71200F7 for <wgchairs@ietf.org>; Sat, 18 May 2019 07:27:16 -0700 (PDT)
Received: from localhost (24-32-26-232.erkacmtk05.com.dyn.suddenlink.net [24.32.26.232]) by mail.hardakers.net (Postfix) with ESMTPA id 4A60E20EFF; Sat, 18 May 2019 07:27:14 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Lars Eggert <lars@eggert.org>
Cc: Gorry Fairhust <gorry@erg.abdn.ac.uk>, WG Chairs <wgchairs@ietf.org>, Pete Resnick <resnick@episteme.net>
Subject: Re: WG meeting structure
References: <61D81D11-1BA0-4123-80C9-C7A97297ED5C@episteme.net> <BF668B4C-6D67-4D7D-A31F-C24523F04EB2@gmail.com> <CAJU8_nUGXL6D1E6Sx-byC8FX66LZb=xe6rDf9_45bqd+0peXng@mail.gmail.com> <CAD62q9U1do+3K5g8KXYJpmuZ2mR2JFBOxt1Qi=bn2v-=QxGUxA@mail.gmail.com> <CAJU8_nUUJPU19msBJrBJ2WyxgBKOqBKMz-scDKG5C=-2eqPtRw@mail.gmail.com> <5CDBBAE4.4030407@erg.abdn.ac.uk> <D3B7C6EB-C471-4C32-A84B-03F4BBE136E0@eggert.org>
Date: Sat, 18 May 2019 07:27:12 -0700
In-Reply-To: <D3B7C6EB-C471-4C32-A84B-03F4BBE136E0@eggert.org> (Lars Eggert's message of "Wed, 15 May 2019 10:57:17 +0300")
Message-ID: <ybly333g7nj.fsf@wu.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/H-gpFvMZfBjTsPGFNo-vh4ok2NY>
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: Sat, 18 May 2019 14:27:19 -0000

Lars Eggert <lars@eggert.org> writes:

> that was exactly the intent. QUIC never made much progress on any open
> issues during the IETF meetings, because the serialized "discussion"
> enforced by the mic lines is simply very inefficient at that. 

TLDR; In the end, I think a setup like that would work for a small WG
with a need for real brainstorming, but has
fairness/management/exclusionary issues with larger groups.


Jumping in here randomly, but the above at least works for some of my
context:

1) Some other standards organizations have rooms set up this way, as
people mentioned.  Typically these work well when the conversations to
be had are functionally "closed" but "open to observers", similar to
(large) board meetings and things.  It definitely impacts the
desire/ability to have other people in the room participate, and if
you're looking for a diversity of opinions this will hamper that.

2) Queue management becomes a different problem, which is harder for the
chair.  People raise hands to get put into a "I want to talk on the
subject queue", and when that list becomes long it's a real pain.  We
tend to have long lines at mics at the IETF, so the chairs may have
their work cut out for them.  If you don't do queues and do free-form
discussion, then mic monopolization becomes a serious problem, or some
people with valid inputs simply never get to express their thoughts
because its hard to be heard in a group of shouting people.  I'm
constantly concerned that without management, we only hear from
extroverts.  IE, "fair" becomes a real issue if it's not a small group.

3) Serialization itself isn't an issue *if* people are responding to
previous people's comments in an orderly fashion (more in a sec).  I
have seen many productive mic lines where 2-3 people resolve an issue
all standing at the mic, with a longer line behind them.  Which brings
me to:

4) One counter idea is to have rooms with two microphones (like many
have now, but run into issues with #2 above), but mandate that we use
them in the way we have in the past at plenaries: one mic is for
introducing new ideas, and the second is for responding to that
comment/issue.  Then you resolve some of the issues with not being able
to rapidly close sub-ideas with "discussion" style conversations that at
least still promotes fairness (smaller queues on a single topic).

-- 
Wes Hardaker
USC/ISI