Re: [irsg] Join/Leave beeps, mic muting

Christian Hopps <chopps@chopps.org> Fri, 01 May 2020 00:48 UTC

Return-Path: <chopps@chopps.org>
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 947FB3A175B for <wgchairs@ietfa.amsl.com>; Thu, 30 Apr 2020 17:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Bw5twyBGBz_r for <wgchairs@ietfa.amsl.com>; Thu, 30 Apr 2020 17:48:33 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2E33A1735 for <wgchairs@ietf.org>; Thu, 30 Apr 2020 17:48:32 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 29FA8611EB; Fri, 1 May 2020 00:48:32 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: [irsg] Join/Leave beeps, mic muting
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <E20C4F5A-26D3-4AA3-A777-3D9EF4E9F9D6@juniper.net>
Date: Thu, 30 Apr 2020 20:48:30 -0400
Cc: Christian Hopps <chopps@chopps.org>, WG Chairs <wgchairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C3F7579-6A38-4EC3-82A0-6C6B3B71933B@chopps.org>
References: <8BFDA214-B2FE-49A8-AEB9-A9B21BE99A38@juniper.net> <26697.1588091591@localhost> <08D40B19-0DB4-435D-BE5E-1E5F0064D414@tzi.org> <FC9D862E-BD3E-4101-BAB9-FB370110A424@tzi.org> <E20C4F5A-26D3-4AA3-A777-3D9EF4E9F9D6@juniper.net>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/8CTafW1FRMeR6FMUTUIBSMs2GOA>
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, 01 May 2020 00:48:37 -0000

+1 and also,

tl;dr 10 minute maximum pre-start time is not enough.

In my last meeting (LSR) we spent 20 minutes (10 prior and 10 wasting the WGs time) trying to get webex working. The problem was both chairs were logged in as the "LSR Working Group", neither of us could log in as anything else, and only one of us could share content regardless of who had the presenter ball.

This is probably some webex bug, and we could have setup a new account, and logged in with that; however, there wasn't time for that.

I am not able to log in to webex, get comfortably setup with all the windows etc, and sync up with my co-chair and make sure everything is working, all in under 10 minutes.

Thanks,
Chris.

> On Apr 30, 2020, at 5:18 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org> wrote:
> 
> At our last meeting Sue and I had at least three machines going — one for projection, one for meeting management, and one for queue management and Jabber. Probably this could have been done on two screens or even one, but that’s how we did it.
> 
> Since it looks like we will be doing this for some time to come, I think it would be really quite helpful to assemble a “how to run your WG session with WebEx” training. What I’m not sure of is how practical that is considering the diversity of platforms people are likely to be using; I don’t know how consistent the WebEx UI is across them. I’m also not sure how stable the WebEx UI is — some vendors, naming no names, tend to reshuffle menu items and buttons at least annually, just for fun, or to “freshen” the interface I suppose.
> 
> I’m thinking of simple nuts-and-bolts:
> 
> - how to set the session up
> 	- join/leave beeps are disabled
> 		- how to disable them once the meeting’s started in case you forgot
> 	- available to join 15 minutes beforehand for testing
> - managing open mic disruption
> 	- host should mute them
> 	- don’t bother yelling at them to mute
> - project with a modest screen resolution (scale down your enormous monitor, you show-off :-)
> - project in presentation mode, not edit mode
> - diagnosing and fixing audio feedback
> ...
> 
> Also, what do people think about slide advancement conventions? Since most of our community (me included) doesn’t use WebEx that much, for our WG we’ve chosen to stick with the convention of having the chairs project and the speakers request slide advancement, instead of fumbling about with passing control to the speaker. Other groups I’ve attended recently have done the same. Is this pretty much universal practice, does anyone want to speak in favor of the “pass the ball” alternative?
> 
> It might also be good to discuss queue management conventions. Many groups have adopted the convention from the virtual 107 of using “+q” in the WebEx chat, but some haven’t; the inconsistency isn’t especially helpful for attendees trying to do the right thing.
> 
> Thanks,
> 
> —John