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

Mark Nottingham <mnot@mnot.net> Sat, 02 April 2022 01:42 UTC

Return-Path: <mnot@mnot.net>
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 55B663A058F for <wgchairs@ietfa.amsl.com>; Fri, 1 Apr 2022 18:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=a4w78bNq; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ARwdE7yD
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 FTxiv0YIo4D3 for <wgchairs@ietfa.amsl.com>; Fri, 1 Apr 2022 18:42:00 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81E9E3A053E for <wgchairs@ietf.org>; Fri, 1 Apr 2022 18:42:00 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 1D00832013BE for <wgchairs@ietf.org>; Fri, 1 Apr 2022 21:41:58 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 01 Apr 2022 21:41:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; bh=5gIzuJb6BilcU5 QcdSh/IgzaN5yGq6ZGKI5I/KK3IuM=; b=a4w78bNqLo3woo2esrG4FDzeYzN9rB HZVUcc6gMVw5L0RPstzDibrWGITNwdag39hDv2u9vlTP1rXsDkMemzoKT6c9aR4P Spatj/J/Sxo+mSZGl9RHqY+0XD1CUbBKzZ6xl01ythqY+c7MPorggfSMSA+AJxA8 hFMfBcYveKmHT2j8e8B8rkO4SoUCtTWbqTpfEVHR8xOpHPZI4Zna1B0VCNoiDeri QaA+cWys+L3MJp9TLHsMH2q0HiYPEXGxR3zjXF1jXTUdTWp9kdMsyHOgYhKZESeC quMBNwcnHZJEz6UHc+UG3lnwrjJcbIJkTyB3Z5HLmIon8MiIAwKdw6+A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=5gIzuJb6BilcU5QcdSh/IgzaN5yGq6ZGKI5I/KK3IuM=; b=ARwdE7yD 3lcbj4t79a7bJNdraqtoKor4ZFEmkF8Jour1gBm3CJ0fH5mTSb3UQXoGG6cdkwPs dqr2n8ppqFu0ux/IZgNB5e3uaDtfhSOu5BfQFb4ToGx4mXFkM/RyAAXe3R9VHtgJ DKuwsvFgW/canLd6izieF7iu+wynNNq6KGFxgIHIXE/zJgj/iAEYRKUrKOfOl/vG CQS562k24l6bDyNSY/pnnZDeOEgN4gjujaHzT3qN4rLKafJFiZBt+9U/Z//rZh3B +Jwxta/p7PPPnDP0797VRWATxwxAPUS0jHu+E8C5ksFLXVm1oCuR5T722BCtJgqk vdGFi7nmkj6GoQ==
X-ME-Sender: <xms:5alHYsHRB6o-CCqwfRImDyKFbD5tcUPbzX633zYRzx1PYbYQmtQczg> <xme:5alHYlXRqW_wpgHEMzkboEMutU6eojrKnNIS6kcMQHm6vnughst240f9k_Lfb_fsk Ux_fSbH6pNaTqWXFg>
X-ME-Received: <xmr:5alHYmLXHMWhETp5vno44BB_3Hjjt4yMI7Mv-Vql8-g1y9_9WCV7U8qeMk3GnJnDla86InpvZ-3ihXsuM-nbz3V1dUu_HJ2xXilOqxzz7eAmCocDdEK8Maiy>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeijedggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne goufhushhpvggtthffohhmrghinhculdegledmnecujfgurhephfgtgfgguffffhfvjgfk ofesthhqmhdthhdtjeenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnh hothesmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpefgteeugeevkeffueduvdfh hfegveffuddukeeifeejhfegffeiudeiteffgfdtheenucffohhmrghinhepfiefrdhorh hgpdhgihhthhhusgdrihhopdhivghtfhdrohhrghdpmhhnohhtrdhnvghtnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhoth drnhgvth
X-ME-Proxy: <xmx:5alHYuEsBabrSUadsFNAQmkeaLpe5Y_8yQg57dEUutF6iX4LuRTNwg> <xmx:5alHYiUGNhB2AtZBzeqmXbZ3kYSp3-A1TxQKAqfvT97YxGWe_wFnIg> <xmx:5alHYhN4iLG78geyaQLviIFVF6vqNt2WDonypY5VE1udMLCz37zdmg> <xmx:5alHYre-9Hmd8EbxQiN4WLNLnUWkuwVBIjg-Npf_wRlR2YlgbqlBnQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <wgchairs@ietf.org>; Fri, 1 Apr 2022 21:41:56 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: [irsg] Chat comments for the record...
Date: Sat, 2 Apr 2022 12:41:54 +1100
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> <8A47B0AE-6F05-4D7A-9EF3-8518D5D0B147@gmail.com> <35632692-508f-1667-b3da-2f40a125656a@erg.abdn.ac.uk>
To: WG Chairs <wgchairs@ietf.org>
In-Reply-To: <35632692-508f-1667-b3da-2f40a125656a@erg.abdn.ac.uk>
Message-Id: <2A7FC504-2E2B-4E4B-85D7-04C694F070FB@mnot.net>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/gOP--tn4mVR_FYnvoPQBX-gkHac>
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: Sat, 02 Apr 2022 01:42:06 -0000

FWIW -

In the W3C, it's common to take minutes in IRC, with a bot collecting them. The bot knows who the scribe is, so it can separate out the 'official' minutes but still intersperse the chatter; it works pretty well.

See, e.g. (chosen somewhat randomly),
  https://www.w3.org/2022/03/22-ag-minutes
  https://w3c-ccg.github.io/meetings/2022-03-15-vcapi/

Cheers,


> On 2 Apr 2022, at 4:10 am, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> 
> On 01/04/2022 19:08, Bob Hinden wrote:
>> 
>>> 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
> 
> +1, seems helpful.
> 
> Gorry
> 
>> 
>>> 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
> 
> 

--
Mark Nottingham   https://www.mnot.net/