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

gang Antgam <antgamgang@gmail.com> Mon, 02 August 2021 22:24 UTC

Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5336F3A1F2A; Mon, 2 Aug 2021 15:24:17 -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 xjkbT-HJKfOz; Mon, 2 Aug 2021 15:24:12 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 2DFD83A1F3B; Mon, 2 Aug 2021 15:24:12 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id f13so26476944edq.13; Mon, 02 Aug 2021 15:24:11 -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=c3qnhkilVEk0ftQSvutgn33T5xytt4BrWeTMIl7euuc=; b=m8LcCkSpXKE7cG4AS1jrJcGpbfKRIVLRO4umuHu1wkYiadIKBGRKdqT4TX2t0c9ebY vzqLyh46Abr31HkKqZEE+4gOTl1lkHK0AwhEhec8c4bBFHa9q3d1YU8553aeQJNdqVdk acfvniCfDbVtc1ayYw4k9oIs7N8wZLjeNzghPilStX9UcgeNCZ1kU2dmp0CTLZDQMMDl sBH0M/GwC3rRHfwmGBtBzXOO3ZKyILrk4I9GrskAbb0ucw/fRPOKC0y0ExHx1+AWa4RD 3spWLCJQISBLOttLiWIdxTB78gw4I1aqQTSAewBBOzYG4jLzSfOvbLOBXyu0pW1ERoB6 q2MA==
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=c3qnhkilVEk0ftQSvutgn33T5xytt4BrWeTMIl7euuc=; b=Jt0hrsX0HxwgVrAk8LpQrPmYio/SBWSYVcrTTIsdA0Lxg1sdncq0/aYR5CpIl3j1Dv xibQa25QtjUyx3dfds3dy8chpqTkK5b2EFHmZ8I27zLQ0DjLhwStyc2+P3GrLz3pbph6 x/ZvwIB/B8QIt5hfNHE+6DQvYM1ozsIf7UUmq+2R5tzaewoteoD7kVte0hz8SltXvx5m iXxXyUA2xz9sSxMjLTvVvDxgWXiGflKTj9FVZ19QXSiVt49Oi98zz8aq/lTEmGzXurXH eNy8VAcSsrWmsbdEUqk1y15OwbKNg0uJniFglskW3fMxieWEtEPLwASnE7muNVafp3hs fsNw==
X-Gm-Message-State: AOAM532nA1YkeCUIzfiA3Dpxix39KYKYgms0rLqb9kYfjKj579IS4Oto MoxD9JVL9XRZPfc0vIcN8MjnAai1n/pIdmYrhJUZ0wWykS+qGw==
X-Google-Smtp-Source: ABdhPJzz1gDGncwBlUA1TNXg8XmD51lVj6pjsVgeKb0RkD/3MVs785c0dSYChH5KWpJa/o/hkpANxhNTGMNpDY6+ou0=
X-Received: by 2002:a05:6402:1e96:: with SMTP id f22mr16214455edf.189.1627943045521; Mon, 02 Aug 2021 15:24:05 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dyUbOgM=cAmeALJoUpX9PVUzH+__VjESyT+VF8dzREnw@mail.gmail.com> <4268651f-6bd7-10ce-6ed8-a758bd956062@meetecho.com> <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
In-Reply-To: <a936f89d-f29c-fe36-5293-5292d70edb06@petit-huguenin.org>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 3 Aug 2021 02:53:54 +0430
Message-ID: <CA+d13g3GGfFstzFwn-1400GLagMg1W8Ei4kZ-5tnKCvJk6kU2A@mail.gmail.com>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
Cc: tools-discuss@ietf.org, Meetecho IETF support <ietf@meetecho.com>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f1642c05c89b0657"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/VafR1CyjZYJlcluxdsUjC7D9dPY>
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-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:24:26 -0000

در تاریخ دوشنبه ۲ اوت ۲۰۲۱،‏ ۲۲:۱۸ Marc Petit-Huguenin <
marc@petit-huguenin.org> نوشت:

> 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 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
> >
> [...]
>
> --
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: https://marc.petit-huguenin.org
> Profile: https://www.linkedin.com/in/petithug
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>