Re: [irsg] Chat comments for the record...

Bob Hinden <bob.hinden@gmail.com> Fri, 01 April 2022 17:09 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFA63A00DF for <wgchairs@ietfa.amsl.com>; Fri, 1 Apr 2022 10:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 sZXkPYH3PcQ7 for <wgchairs@ietfa.amsl.com>; Fri, 1 Apr 2022 10:09:09 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 227C23A0115 for <wgchairs@ietf.org>; Fri, 1 Apr 2022 10:08:55 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id w21so5183280wra.2 for <wgchairs@ietf.org>; Fri, 01 Apr 2022 10:08:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=OPps+mRA7NM9OrZDTppZ8YeHO9CUTkapOGsLpFZYfx4=; b=DvUMjO0RD45i4K7MGgpvYh4TjM/1DmywJw/2lHKLWZVVI9rc+d7JsUUhSvM8HiO4bZ uGd5vrsZ6kmAogbLw3zm5+uUG+wg121iLZAE2f8PfdNyNdtXq9Zxa3wxhaEe+fKfXprN CYIC5ZxL7udAOV8EdhOg9/iQ5je7iKTr41R9Aul3yEbxb/Rs6XnZtwcnKRyNuR3+RVk9 1+UgcXCaOZjUkHnik4w7JC/3NeymFG4E/P3Qjfip1hGq/YOnEBRPp9XDlTn91DrYATYA Er/mlMKs3DI9D97sk5Wso4R28V2jqsiMb+HWrb/Y5SJutVTzPjfE8rjoiZp+XONGvol3 nn1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=OPps+mRA7NM9OrZDTppZ8YeHO9CUTkapOGsLpFZYfx4=; b=fhHRVUqaAgvWDFGRdigaTUiH3GoXjLInE155CH3NK6ia2m1b/XvFNXm2ABB2ghhC5K hO30iX2kSDnFEQRU1+urYqf5C0cMsbN5Cnbf+1q5HcbL9diEVv4+HwiLupmvCjo1JOTq Wl7IcAlx4c05XjY2KXLIOwj5Bn/PnEmtY+Rq8O2eJ80vXElTtCifYU/UsWbQ99MDZubX DhclvZPNmpHVh5bwMtNKN8mS68hn5B6ONKI29Txn8EJDok/+LY4oKzbbsOJYuhlkxe5T OT+gjuj8reVCTodvbhG1a1nmalEZsdJooSD1ypj5+Q5hTYr4f9c7ha/6MbJmQERTsx2w XnPA==
X-Gm-Message-State: AOAM531tAU02e7va4PlapvYBDMtakiUrEFT7Oh8ku/0FzFZACkNZPwR5 fT6G3C7u3F9/YzxtUFxzduA=
X-Google-Smtp-Source: ABdhPJyIvJzsF+hpZq99SKvcxosNtleZUE1QklpGFASjvyGEA9ksAnDJ8zbsZp4urC+9qIYoojOKCQ==
X-Received: by 2002:a5d:598a:0:b0:204:6fb:6461 with SMTP id n10-20020a5d598a000000b0020406fb6461mr8593199wri.132.1648832932891; Fri, 01 Apr 2022 10:08:52 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:fdbe:6565:2c2f:65c1]) by smtp.gmail.com with ESMTPSA id i15-20020adffdcf000000b00203efad1d89sm3439794wrs.9.2022.04.01.10.08.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Apr 2022 10:08:52 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_123C33FA-8283-4BFF-98BD-29737DDE62B7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Subject: Re: [irsg] Chat comments for the record...
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <Ykcu0wQA3mIx2CKP@faui48e.informatik.uni-erlangen.de>
Date: Fri, 1 Apr 2022 10:08:49 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, WG Chairs <wgchairs@ietf.org>
Message-Id: <8A47B0AE-6F05-4D7A-9EF3-8518D5D0B147@gmail.com>
References: <YkXvmifVYJBA+Job@faui48e.informatik.uni-erlangen.de> <E3D631E5-ADD8-4B70-95B7-5A5505A8A131@tzi.org> <CAKKJt-dTV6gxtTzA5n_7nPB9P1Mb91rZ01wbD+f=oyRN_OAq1w@mail.gmail.com> <7B746C7F-1986-4E15-B626-37540B39727C@gmail.com> <Ykcu0wQA3mIx2CKP@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/UIGpTF9HA9cNdjNl5xQzXJr1xWc>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2022 17:09:14 -0000


> On Apr 1, 2022, at 9:56 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> Agreed for not automating or blind merge.
> 
> If we don't manually merge or (as i am suggesting) ask for contributors
> to add notes-worthy contributions directly to the log, then maybe at miniminum
> one may want to include the URL to the jabber log of the meeting day into
> the notes with just the comment that the jabber log _may_ contain additional
> relevant contributions. And thats just because it seems that even the existance
> of chat/jabber logs seem to be a surprise to quite a few IETF participants.

I like that!

Bob

> 
> Cheers
>   Toerless
> 
> On Fri, Apr 01, 2022 at 08:34:43AM -0700, Bob Hinden wrote:
>> I don’t support some kind of automatic merging of the jabber/chat log into the minutes.   There can be a lot of noise and off topic discussion there.   For example, here is the one for the 6MAN session:
>> 
>>   https://jabber.ietf.org/jabber/logs/6man/2022-03-22.html
>> 
>> A very low signal to noise ratio.
>> 
>> For 6MAN, our minute takers, Peng Shuping and Pascal Thubert (many thanks to them), include on topic excerpts from the jabber log.  For example from the published minutes:
>> 
>>    From jabber:
>> 
>> 	• Loba Olopade: I prefer the normal/exception terminology to fast/slow path
>> 
>> The session video recording and jabber log are retained and are available to anyone who wanted to look at them. I don’t think they should be automatically added to the minutes.
>> 
>> Bob
>> 
>> 
>>> On Apr 1, 2022, at 8:04 AM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
>>> 
>>> Top-posting to say that I agree a lot with Carsten here.
>>> 
>>> I try not to be a note-taker these days (because I'm just not as good at it as I used to be), but I remember taking notes on "what was going on in the meeting" while watching the discussion in chat/jabber and thinking "that's where the real discussion is happening".
>>> 
>>> It's likely that different people will have different experiences with this, based on participation in different working groups, but I've been in meetings where someone was presenting in the meeting, and discussion on aspects of that presentation was still taking place 15 minutes later in chat/jabber. So, in the meetings where I hang out, merging based on timestamps doesn't work, because we're two presentations out of sync between the meeting and the chat/jabber.
>>> 
>>> I think that's especially likely for BOFs and side meetings (and, yes, I've offered my own working group's jabber logs as a place to exchange thoughts for an unrelated side meeting - my working group wasn't using it at the time, and rarely if ever does).
>>> 
>>> I applaud the dedication of chairs and secretaries who go to the effort of cleaning up the chat/jabber conversations for inclusion in the minutes, but at their best, some chat/jabber conversations are WELL worth including, even in raw form.
>>> 
>>> IMO, of course. Do The Right Thing.
>>> 
>>> Best,
>>> 
>>> Spencer
>>> 
>>> On Thu, Mar 31, 2022 at 4:34 PM Carsten Bormann <cabo@tzi.org> wrote:
>>> On 2022-03-31, at 20:14, Toerless Eckert <tte@cs.fau.de> wrote:
>>>> 
>>>> suggest to the WG participants to directly write suggestions that they
>>>> would like to be on the record (when they cannot/wantnot make them
>>>> on the microphone), not (only) into the chat, but directly
>>>> into the notes.ietf.org notes as they are being taken.
>>> 
>>> That is such a great idea that we have been doing this in interims, design team meetings etc. for quite a while now.
>>> 
>>> I sometimes do that when touristing in WGs where I’m not as familiar with the current customs; this may seem a bit jarring to people who think that a minutes document cannot contain things that haven’t been said.
>>> 
>>> So it would be good to make this part of the etiquette, and maybe develop a notation convention for things that have not (yet) been said.  In particular, people who are going to make a comment at the microphone might want to write up their comment in the notes before that so the note-takers don’t have to do this in real-time.
>>> 
>>> Grüße, Carsten
>>> 
>> 
> 
> 
> 
> --
> ---
> tte@cs.fau.de