Re: [Tools-discuss] [111attendees] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 02 August 2021 17:30 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
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 C1D3B3A112C for <tools-discuss@ietfa.amsl.com>; Mon, 2 Aug 2021 10:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kc4hCutxsxDN for <tools-discuss@ietfa.amsl.com>; Mon, 2 Aug 2021 10:30:31 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 430EF3A1126 for <tools-discuss@ietf.org>; Mon, 2 Aug 2021 10:30:31 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id v16so9923755vss.7 for <tools-discuss@ietf.org>; Mon, 02 Aug 2021 10:30:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PKDLDRy7JCafSCDSRF74ldSRLmgRMoO4oL7207mlXKk=; b=dVBOsJjLdSvVhc1+ATvU7pFHp0AaUPgl1vZptGMEJeaz/sSvuysl7Gha9e2yE4aJv6 hucPZYOjJkZDLy46TEa0Ast+Qp+44UXwS4IvU8VC1B1xkI89yXqWZ15cqeFgSs4d6EnK 9DH6YVrkVar7jD1Qmm0fAyGUCOt/uWgjD5Wl2bQbCcCUuqi61xxmbfDcL8qQkm3NCOUS EthJ6zCvJaiePJ+wSvdDJMdloczjFjiHA+1DVMXY9Yuww52JF2sIe6t5VxvA7PpASydu BMp3UYwPSj92UUsDE89htrtJ3ruknE1A7vOypa8oHBiLpcT5kPBeD6mVizwdIFS5ES46 zyww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PKDLDRy7JCafSCDSRF74ldSRLmgRMoO4oL7207mlXKk=; b=oA2HJ/s419nKlPxKxiv9RygnLMA+Pwo6ogs7VlqLoG+y0MqLQ5QdPt5rmgeX9JcBR5 NFmgPv+u7DZclDQ3BgYOVonWcxSVEbl57epqFN1eQxne/4Qioy4sIT2gB4mF74So7UI1 jv55fH4wLaj1f/pbhZCKi9oHseHy32VbUYyFLQ1laq3cvgtdVElE2Nnmig8ualU9guVk NXKsAoIOlKHdnrUGZtGZcaVahhEiQUdxCxwPze6f79Se7FEE4ZQshbR55dVS8LfERq/m oM5/a/Zk8vZjd7QZtsw+ez+rsqbwpnGI8wgKuZYU60UQYH0foQk20oP86LhR1SlhUlVm zA5g==
X-Gm-Message-State: AOAM532KNoLvJ2QGstXJHzQMQ2w098M5HV5IJLfS/mU66Zwn5O2WFztZ e0RuskHOL9JSKIlZlsT/t84AI2imI4vXnS64/fPzheIK
X-Google-Smtp-Source: ABdhPJy7g5SVBOlXt028O23nChH/00O2B6xq6CIYCpyEUzSd6nSht5ziQez5/IrLNwmRdc47kqlDm7CiafRTv4SmYoc=
X-Received: by 2002:a67:f854:: with SMTP id b20mr11555908vsp.32.1627925429443; Mon, 02 Aug 2021 10:30:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <BLAPR22MB2259E361386AE105D3452ED7DAEF9@BLAPR22MB2259.namprd22.prod.outlook.com>
In-Reply-To: <BLAPR22MB2259E361386AE105D3452ED7DAEF9@BLAPR22MB2259.namprd22.prod.outlook.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 02 Aug 2021 12:30:01 -0500
Message-ID: <CAKKJt-eTgDryeptOrQomqa4jVicGeY2C6bF91ZufBx2Xa9HEEA@mail.gmail.com>
To: Mike Bishop <mbishop@evequefou.be>
Cc: "tools-discuss@ietf.org" <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f1643205c896ece7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/eBOtfpG_iODClvKWsNdEETckC7s>
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: Mon, 02 Aug 2021 17:30:37 -0000
Hi, Mike, On Mon, Aug 2, 2021 at 12:22 PM Mike Bishop <mbishop@evequefou.be> wrote: > Let me add to the suggestion that names of speakers appear in the video > view -- the recorded sessions which are posted to YouTube don't have names > associated with the video, or with audio-only speakers. Because everyone > is looking at the MeetEcho UI, last names aren't typically being used, > which means I have to guess who is making particular comments when watching > the recordings. > > I'd like to suggest that the idea of having icons of audio-only > participants be expanded to the recordings, and that participants with > video have names attached to the video in the recording. > Yeah, it would be good to look seriously at the YouTube videos and figure out what else we're missing from the video feed. I was thinking about "comments made in Jabber", but your observations are also things worth fixing, and (especially if we make a habit of sticking jabber logs into minutes or otherwise making links to the jabber logs YouTube-visible) more useful for more people. Best, Spencer > Thanks! > > -----Original Message----- > From: 111attendees <111attendees-bounces@ietf.org> On Behalf Of Meetecho > IETF support > Sent: Friday, July 30, 2021 3:38 PM > To: 111attendees@ietf.org > Cc: tools-discuss@ietf.org > Subject: Re: [111attendees] Positive observations and proposals for > improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually > doing, these days?) > > All, > > chiming in just to say that we at Meetecho appreciate and value your > feedback. We'll definitely take it into account when developing the future > releases of the platform. We'll provide comments on the points raised as > soon as we get the chance to parse them, i.e., when the meeting is over. > > Also, I'm cc'ing tools-discuss@ietf.org and setting the reply-to header > to that list as well, as that's the right place to discuss enhancements and > provide feedback that would be easier for us to collect. > > Best, > Alessandro > > Il 30/07/21 19:37, Spencer Dawkins at IETF ha scritto: > > I should have changed the Subject a LONG time ago! But this thread has > > morphed into helpful observations and suggestions, so, if I might add > > a couple of things ... > > > > I agree that Meetecho has been improving (and just for fun, the > > Meetecho guys were participants in the MEDIACTL session I was > > co-chairing in Hiroshima at IETF 76 in November 2009, and they roped > > in a team member from Italy during the discussion using whatever the > > toolset was back then, so many of you have no idea how MUCH they've > improved 😀). > > > > I see that we've already mentioned detaching the chat window, and > > usually I remember that we can detach the chat by Tuesday of each IETF > > meeting week at the latest, which is almost certainly a result of not > > having THAT much experience with Meetecho during the four months > > between meetings. Now that we can use Meetecho for interim meetings, > > that will help me remember more clearly, so good there, too. > > > > The one thing I've noticed this week is how difficult it is to figure > > out who is speaking if they aren't sending video, and there's a long > > list of people in the queue. The suggestion to move the speakers above > > the queue would improve that, and so would simply displaying the > > active speaker names in the screen space where their video would have > > gone, if the person had been sending video.One reason that matters, is > > that it's helpful for everyone to get the speaker's name right in the > minutes. > > That's not just for new attendees, I'm starting to forget what people > > sound like, unless I'm talking to them regularly, or they have a very > > distinctive speech pattern, so I've definitely depending on seeing > > names when I'm taking minutes. . > > > > The one thing I was thinking about, as I read through this thread, was > > that we are kinda *not *talking about what the IETF thinks the target > > audience for our conferencing tool is. > > > > * For probably the last couple of IETFs, I have a GREAT setup for > > remote participation (my laptop screen, plus two 25-inch monitors). > > But I do have tiled windows on all three screens. > > * If we think people who can't throw a few hundred dollars at monitor > > screens are part of our target audience, that's worth noting. > > * If we think we're going to have hybrid meetings, in at least some > > scenarios, it's going to be good to use Meetecho in the conference > > rooms (especially if we need to be distancing, so more spread out, > > front to back in the conference rooms). > > * Even if we aren't doing hybrid meetings, I've participated in some > > working group meetings from my hotel room, but I wasn't tryng to > > co-chair a meeting, or even to present at a meeting. > > * When Michael Richardson and I talked to the Cellar working group > > participants about switching to Meetecho for our (monthy) interims, > > the first question we got was, "is there an iOS/Adroid client?" I > > haven't checked Meetecho on my phone in years, but I'd bet offhand > > that (1) it would work, but (2) it might not be as easy to use as > > some other conferencing systems, on those devices. Do people have > > experience with that? > > > > I'll let you folks continue to share these positive observations and > > proposals. Make Good Choices, of course. > > > > Best, > > > > Spencer > > > > On Thu, Jul 29, 2021 at 6:15 PM Jay Daley <jay@ietf.org > > <mailto:jay@ietf.org>> wrote: > > > > Thanks Bron. Personally I think that’s a great usability adjustment > > and will forward to the Meetecho team for them to consider. > > > > Jay > > > > > On 30/07/2021, at 10:58 AM, Bron Gondwana <brong@fastmailteam.com > > <mailto:brong@fastmailteam.com>> wrote: > > > > > > On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote: > > >> No we have absolutely not pushed Meetecho into being "just a > > contractor", they are a valued partner and we work very well > > together. If you have any doubts about that then ask them directly. > > >> > > >> It is disappointing that you have escalated a personal concern > > that you have with our services into such a strong criticism when > > that is entirely unsupported by any evidence. > > > > > > Jay, I agree with your sentiment here - this attitude to Meetecho > > is counterproductive. They've done great work for the last couple > > of IETFs and the experience is improving each time. I have > > particularly appreciated the embedded slide management, and I'm sure > > that will be even better next time too. > > > > > > Regarding the specific interface issues that remain, I do think > > there's a question of "where do we propose improvements in a way > > that will be noticed"? I've seen the suggestion made very many > > times that the "speaker" area (where the video shows) should have > > additional lines for each person sending anything, rather than that > > information being at the top of the participant list. This is much > > more like the experience with other chat systems, for example Zoom > > shows either a photo or a blank item for somebody who isn't > > currently sending video, but they're otherwise treated "the same" as > > a person sending video in terms of real-estate and where to look for > > their presence by default. > > > > > > Right now with meetecho, my eyes are normally at the video are > > when people are speaking, but if a non-video person is speaking I > > need to look across to the other side of the screen to see the audio > > indication. > > > > > > And as was also suggested in this thread, you can't scroll the > > participant list to find someone to chat to, because they jump to > > the top when they are sending, then back to alphabetical position. > > This is also a usability pain. Separating "the list of > > participants" (which wouldn't move about) and "the list of people > > sending something" with the video and audio indications being > > together in one place would be a significant improvement. And as an > > additional benefit, when you're looking at the chat window, you > > would still be able to see all the details of who is sending > > (including yourself - if you're sending then the indicator of your > > own audio should be the same as the indicator of everyone else's > > audio, rather than being in yet a third location up under your own > > name). > > > > > > <image.png> > > > So those two names would appear in the right hand side, and also > > still have their name in the participant list, and the video feeds > > would each have a "here's what's being sent". Chairs would always > > have a presence on the right, with whatever they were currently > > sending - and the "participants" tab would only have the list of > > participants, and not be a place you needed to go to see activity, > > so you could mostly keep the chat tab open. > > > > > > Bron. > > > > > > > > > -- > > > Bron Gondwana, CEO, Fastmail Pty Ltd > > > brong@fastmailteam.com <mailto:brong@fastmailteam.com> > > > > > > > > > -- > > > 111attendees mailing list > > > 111attendees@ietf.org <mailto:111attendees@ietf.org> > > > https://www.ietf.org/mailman/listinfo/111attendees > > <https://www.ietf.org/mailman/listinfo/111attendees> > > > > -- > > Jay Daley > > IETF Executive Director > > jay@ietf.org <mailto:jay@ietf.org> > > > > -- > > 111attendees mailing list > > 111attendees@ietf.org <mailto:111attendees@ietf.org> > > https://www.ietf.org/mailman/listinfo/111attendees > > <https://www.ietf.org/mailman/listinfo/111attendees> > > > > > > -- > 111attendees mailing list > 111attendees@ietf.org > https://www.ietf.org/mailman/listinfo/111attendees > ___________________________________________________________ > Tools-discuss mailing list - Tools-discuss@ietf.org > This list is for discussion, not for action requests or bug reports. > * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org > * Report tools.ietf.org bugs to: webmaster@tools.ietf.org > * Report all other bugs or issues to: ietf-action@ietf.org > List info (including how to Unsubscribe): > https://www.ietf.org/mailman/listinfo/tools-discuss >
- Re: [Tools-discuss] [111attendees] Positive obser… Meetecho IETF support
- Re: [Tools-discuss] [111attendees] Positive obser… Bron Gondwana
- Re: [Tools-discuss] [111attendees] Positive obser… Eric Rescorla
- Re: [Tools-discuss] [111attendees] Positive obser… Michael Richardson
- Re: [Tools-discuss] [111attendees] Positive obser… Eric Rescorla
- Re: [Tools-discuss] [111attendees] Positive obser… Jonathan Morton
- Re: [Tools-discuss] [111attendees] Positive obser… Mike Bishop
- Re: [Tools-discuss] [111attendees] Positive obser… Spencer Dawkins at IETF
- Re: [Tools-discuss] [111attendees] Positive obser… Spencer Dawkins at IETF
- Re: [Tools-discuss] [111attendees] Positive obser… Marc Petit-Huguenin
- Re: [Tools-discuss] [111attendees] Positive obser… Michael Richardson
- Re: [Tools-discuss] [111attendees] Positive obser… Meetecho IETF support
- Re: [Tools-discuss] [111attendees] Positive obser… Meetecho IETF support
- Re: [Tools-discuss] [111attendees] Positive obser… Meetecho IETF support
- Re: [Tools-discuss] [111attendees] Positive obser… Spencer Dawkins at IETF