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

Marc Petit-Huguenin <> Mon, 02 August 2021 17:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C7EB73A1228; Mon, 2 Aug 2021 10:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hEVp2bR4bDmL; Mon, 2 Aug 2021 10:48:08 -0700 (PDT)
Received: from ( [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 03D373A1225; Mon, 2 Aug 2021 10:48:07 -0700 (PDT)
Received: from [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd] (unknown [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "" (verified OK)) by (Postfix) with ESMTPS id E9753AE269; Mon, 2 Aug 2021 19:48:03 +0200 (CEST)
To:, Meetecho IETF support <>,
References: <> <>
From: Marc Petit-Huguenin <>
Message-ID: <>
Date: Mon, 2 Aug 2021 10:48:01 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [111attendees] [Tools-discuss] Positive observations and proposals for improvements to Meetecho (was: Re: Re: So, what are jabber scribes actually doing, these days?)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Aug 2021 17:48:13 -0000

One use of the Meetecho recording is to prepare minutes by double checking notes.  One issue with that is that sometimes a presenter answers comments made in the chat, but the chat log does not appear in the recording.  The person preparing the minutes now has to open the minutes, try to synchronize then with the recording and update the minutes to reflect the question/comment that triggers the response by the presenter.  There is two issues with that:

1. Someone watching only the recording only have access to half of that conversation and may not know where the chat logs are, or even that they was a chat running along the session.
2. People taking notes must follow both the chat and the presenter, which could be a bit too much.

I do not think that recording the chat at the same time than the presenter would be a good idea (OTOH displaying the name of the person talking in the recording even if they did not turn on video would help).  The reason is that not all the content of the chat log is relevant for the WG business (that's an understatement).

Having a jabber scribe and some discipline may help: The jabber scribe repeats the chat comment/question, and the presenters does not try to look at the chat, and so now the whole context is captured.

But that's still a bit clunky -- a presenter may want to comment on something that someone said in the chat room even if it was not marked as a question that the Jabber scribe must relay.  After all the chat logs are under NOTE WELL, so they are part of the WG session -- and should be part of the minutes, at least the relevant parts.

My suggestion would be to use TTS to supplement or replace the Jabber scribe.  A remote presenter who want to answer/comment on a chat message triggers TTS on the message itself, which now becomes part of the recording -- and of the minutes.  With a local presenter the Jabber scribe could also use that TTS feature.

On 7/30/21 12:38 PM, Meetecho IETF support wrote:
> 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 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

Marc Petit-Huguenin