Re: [Tools-discuss] [111attendees] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 01 August 2021 20:37 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEF03A0E52; Sun, 1 Aug 2021 13:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 ryjQGs-waTEQ; Sun, 1 Aug 2021 13:37:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101703A0E4D; Sun, 1 Aug 2021 13:37:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 18DB038A19; Sun, 1 Aug 2021 16:41:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tbp81oT-Dr_s; Sun, 1 Aug 2021 16:41:20 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 352D238A17; Sun, 1 Aug 2021 16:41:20 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B87A1B24; Sun, 1 Aug 2021 16:37:14 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Bron Gondwana <brong@fastmailteam.com>, 111attendees@ietf.org, tools-discuss@ietf.org
In-Reply-To: <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <99ae28be-dd15-4018-bccc-a1f61ce19e47@dogfood.fastmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Sun, 01 Aug 2021 16:37:14 -0400
Message-ID: <27783.1627850234@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Y-_lwLKOto9EUD7kIiLKK7nzsl0>
Subject: Re: [Tools-discuss] [111attendees] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Aug 2021 20:37:27 -0000

Bron Gondwana <brong@fastmailteam.com> wrote:
    > *a "temporary mute" mode that keeps the audio stream open:*

    > This is still an issue for me.  I often mute myself while chairing so I
    > can take notes without my keyboard sound interrupting the chat - but it
    > means that I can't easily respond to somebody because the rejigging of
    > the audio channel not only creates a hiccup in the incoming audio feed
    > which means I might miss something someone says, but it also creates
    > enough of a delay that by the time I could have responded the other
    > party's mental state has moved on.

Yes, the 3s on/off latency on the audio is a problem.
So one should use a local mute instead, which of course, then causes confusion.

    > Timing is really important in conversation and we're already fighting
    > with the quarter second delay imposed by the size of the planet.
    > Additional delay makes it unwieldy.

Ah... I know of a genetically spliced lab mouse with a plan to reduce the size of the planet.

    > *allow multiple connections by the same person to the same session:*

    > I have multiple times wanted to switch device temporarily - from my
    > desktop computer to a phone / ipad so I can temporarily move to another
    > location while continuing to follow a meeting.  Multiple connection
    > support would mean I could switch over without a break.

It seems like a stretch requirement, but I also know that some chairs want a
second laptop so that they can see whether slides are really advancing.
What I don't understand is, 16 months into pandemic, and 10 years into screen
sharing, how it is that PPT people don't understand that they have to "F5"
before they share.

    > Sure it could be abused by people "sharing" a login, but that would be
    > pretty obvious if both parties tried to participate, and given that we
    > allow fee waivers anyway, it's unlikely to be abused significantly.
    > Sure there are Jabber naming issues, but we can avoid that by giving
    > each jabber name with a serial number (which I believe already happens
    > now?)

Yes. Actually, the ephermalness of the jabber names annoys me, as I can't
message people after they have left.

    > *information about who is speaking in the same place as video feeds*

The video image does do the yellow square when they are speaking.

    > See my previous email :)  Basically the "participant list" should just
    > be an ordered list of participants and only needs to be switched to
    > when seeing who is in the call or opening an individual message to them
    > (and people don't get moved out of order when they're sending
    > something).  The "who is sending something" list should be all together
    > with the video, and chairs pinned even if they're sending nothing right
    > now.

I think that I need a picture.
As my meetecho windows are more vertical than horizontal, I'd also like to be
able to move the video boxes to be under the slides.
see:  https://www.sandelman.ca/mcr/IETF111-virtual-SFO-two-sessions.png

    > Along with visual indicators of "currently sending audio" on people so
    > we know who of those with their audio channel open are currently
    > speaking, this makes it easier to look in one place to see the source
    > of all sound, and eyes can generally flit between the right hand side
    > (video and audio indicators) and the slides, without needing to also
    > track via the participant list.

I think that it would also work better for the youtube recording.

    > *flexible "assign chair"**:*

    > This one hasn't come up in practice, but the chairs for meetings are
    > pre-assigned from datatracker.  It would be great for ADs and the
    > meetecho reps in each meeting to be able to upgrade anybody to a chair
    > role or remove a chair role with a simple click.

That's a good idea.
And with that power, they should be able to advance slides, no matter who
activated them.

    > This has become less important with the ability for individuals to turn
    > on both audio and video themselves, so the chair is going less busywork
    > just approving access, but it would be good to make it possible for
    > someone else to step into the chair if the regular chairs are unable to
    > attend or lose network, rather than making the meeting less able to
    > run.

I'd like the chair to be able to pre-authorize sharing and slides.
Actually, the way I'd implement is that the chair(s) just get to decide who
of the possibly many screen-sharing/slides that are occuring, who is actually
shared.

That lets people (a) test their setup in advance of their slot,
(b) reduce the time to switch.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide