Re: WG meeting structure

Loa Andersson <loa@pi.nu> Fri, 17 May 2019 12:38 UTC

Return-Path: <loa@pi.nu>
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 A174A120151 for <wgchairs@ietfa.amsl.com>; Fri, 17 May 2019 05:38:05 -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] 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 7b3OAlfeCu3d for <wgchairs@ietfa.amsl.com>; Fri, 17 May 2019 05:38:03 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D562A12004A for <wgchairs@ietf.org>; Fri, 17 May 2019 05:38:02 -0700 (PDT)
Received: from [192.168.1.13] (unknown [119.94.160.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 7485C33F5AF for <wgchairs@ietf.org>; Fri, 17 May 2019 14:37:56 +0200 (CEST)
Subject: Re: WG meeting structure
To: wgchairs@ietf.org
References: <61D81D11-1BA0-4123-80C9-C7A97297ED5C@episteme.net> <BF668B4C-6D67-4D7D-A31F-C24523F04EB2@gmail.com> <CAJU8_nUGXL6D1E6Sx-byC8FX66LZb=xe6rDf9_45bqd+0peXng@mail.gmail.com> <EFF30784-E39A-43EE-ADCB-0F0561EA6430@gmail.com> <23773.39810.527083.979022@gro.dd.org> <E832787C-F0E3-4424-8F06-C4155C88B28D@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <088778b8-f20d-4dd1-40b1-dfc74e1d2e77@pi.nu>
Date: Fri, 17 May 2019 20:37:49 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <E832787C-F0E3-4424-8F06-C4155C88B28D@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/DWr-28kulucpLXWgpN_m_OsLiqA>
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: Fri, 17 May 2019 12:38:06 -0000

All,

I agree with most of what what Fred says, drawing on experience from
other wg's.

I'm a bit nervous when this type discussions pops up. As long they are
discussions on "good ideas we tried, and the results we had", I think it
is fine.

When they slide away to instruct wg chairs what they should do, I'm
very concerned.

I'm convinced that when it comes to IETF wg's we don't have and will
never have a seating arrangement that fit all wg's, nor fit a single
working group for all of its life time.

If there are experiments necessary, let the wg chairs do the experiments
and the evaluation of the experiments.

/Loa


On 2019-05-17 10:04, Fred Baker wrote:
> 
> 
> Sent from my iPad
> 
>> On May 16, 2019, at 10:18 AM, Dave Lawrence <tale@dd.org> wrote:
>>
>> Fred Baker writes:
>>> And we generally have a few tables toward the front, with the
>>> express understanding that people sitting there have read the drafts
>>> in prep for the meeting. That tends to be the "core" group for at
>>> least some discussions.
>>
>> Kind of annoying though when you're one of those participants though
>> and have to keep squeezing out from the middle to get to the mic line.
>> I imagine this could be fairly easily remedied though by remove a row
>> or two of gallery seating to allow the tables to be a little more
>> spaced.
> 
> That, of course, depends on room size, and that actual number of people that show up. IPv6 Operations seems to randomly vary between 75 and 200, which is in part why I’m unconvinced about a layout that works well for 20 people. Every meeting doesn’t need to be organized for 200, and it’s true that in every meeting of 200 there is a meeting of 20 struggling to be had - a different 20 on each draft. But that doesn’t mean that every meeting is or should be organized for 20 people.
> 
> I also have questions about Meetecho, which would really like whoever is currently speaking to stand in a small square at exactly one of the three microphones. If we really want that form of A/V (and it looks like I’ll be dependent on it in July), I think we’re going to have to seriously rethink it. Zoom, perhaps, or something like it, using every laptop as a camera, microphone, and display for its owner, might be a solution, if it runs on IPv6.
> 
> In Prague, besides having a giant box or something occupying the center, and obscuring my view, of a good part of the room, I’m not at all sure there was “extra” floor space for aisles and space between rows in any of the breakout rooms on the first two floors (Kaplan I-Iii, or the ones in the “business” area). We had about 70 people, I think, and that worked because some were willing to stand against the back wall.
> 
> In Bangkok, I sat in on hrpc, which had 20-30 people arranged as Pete suggests and didn’t have Meetecho; we still needed to pass a mike around the room simply for people to be able to hear each other. It did allow people to get a lot of opinions voiced. As someone else noted, I wouldn’t have wanted to be the jabber scribe, although jabber might have been a useful solution to “the mike’s at the other end of the room and I want to talk”.
> 

-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64