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

Meetecho IETF support <> Tue, 03 August 2021 14:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 341BF3A25E4 for <>; Tue, 3 Aug 2021 07:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VXQ5jppz-KKT for <>; Tue, 3 Aug 2021 07:36:42 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 643503A25E0 for <>; Tue, 3 Aug 2021 07:36:42 -0700 (PDT)
Received: from [] ([]) by Aruba Outgoing Smtp with ESMTPSA id AvX6m7PpUnyXHAvX6mTuIu; Tue, 03 Aug 2021 16:36:41 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=a1; t=1628001401; bh=Ek3uBrSSN1UTQqBq/QOl28ZQlGBH2XB1NP+5aLO5NeM=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=UiFqc19YUEQqMhDHiWjzZE3hcmsU+YaoBlwW+yHfQRq+Rw+IQ2jvU7kRvabceUph9 O637IxBm2sPf5YrQ94qS9tKILJTZSknlOj3irJvWc03zx83csc0kTa837JgPMYs2Ou uEi/35mHDN5mw8fiOPRwaZiQGHGkB4oh31eIaXnlMfvw88y0cBJ9j4Rw2ULvuSsGOn CER8/HRiP8JQol/FUMp+WN3uxJDxAzFbb9BKYOejYanIqHS5Kb7LVIF9zgI5NtwKWn 64rDBw7k3mQhId3SCw9sAOzUgI51MDw3PkmYEmnFdZWfr8NvZEbl9Obftk1B14EB8K VcObejlQELzQg==
To: Marc Petit-Huguenin <>,
References: <> <> <>
From: Meetecho IETF support <>
Message-ID: <>
Date: Tue, 03 Aug 2021 16:36:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.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
X-CMAE-Envelope: MS4wfPieQXzZC6Gx1fLdGCZ9ODgEQbrlcA3Jg4DBMgA3Fh8lWoxy/Fgm4bOlnr+pc/4cNp+uBylK4SLedcjHV94tNprN5N8w3PKTHu3yUbV2m1+ySjzU/dL6 9khN2Soiwbq8IXq4FBQgCPgwhxWu80cCVmBY+QCT7hBMFAFaNfEqPL2JCcU2JqBye/UiZ40LCtoiKKtGxP/waToOpbwM5/7/H8x+wFCkDqPswykIY3lIOEUV
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: Tue, 03 Aug 2021 14:36:48 -0000

Hi Marc,

while the TTS suggestion is interesting and worth exploring, in the 
short run I think it might be worth revamping the custom recording 
player we had in the past, which integrated the YouTube video, the 
Jabber logs and also the audio transcripts automatically generated by 
YouTube. See for instance:


Il 02/08/21 19:48, Marc Petit-Huguenin ha scritto:
> 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
> [...]