Re: [irsg] Chat comments for the record...
Toerless Eckert <tte@cs.fau.de> Fri, 01 April 2022 15:00 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 203003A14E1
for <wgchairs@ietfa.amsl.com>; Fri, 1 Apr 2022 08:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level:
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01,
URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 a4Esmrqe0VRt for <wgchairs@ietfa.amsl.com>;
Fri, 1 Apr 2022 08:00:37 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de
(faui40.informatik.uni-erlangen.de [131.188.34.40])
(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 6EB2C3A1287
for <wgchairs@ietf.org>; Fri, 1 Apr 2022 08:00:36 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de
(faui48e.informatik.uni-erlangen.de [131.188.34.51])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 8F030549E87;
Fri, 1 Apr 2022 17:00:31 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463)
id 74AE74EAAAF; Fri, 1 Apr 2022 17:00:31 +0200 (CEST)
Date: Fri, 1 Apr 2022 17:00:31 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: Carsten Bormann <cabo@tzi.org>, wgchairs@ietf.org
Subject: Re: [irsg] Chat comments for the record...
Message-ID: <YkcTjwaLJyA1ZzVY@faui48e.informatik.uni-erlangen.de>
References: <YkXvmifVYJBA+Job@faui48e.informatik.uni-erlangen.de>
<E3D631E5-ADD8-4B70-95B7-5A5505A8A131@tzi.org>
<60b3b01d-6ac2-e6c5-43a2-57b3436301bf@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <60b3b01d-6ac2-e6c5-43a2-57b3436301bf@joelhalpern.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/McrLqeiQABH2rlSgNcHE7yZjR90>
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 15:00:42 -0000
On Thu, Mar 31, 2022 at 06:12:39PM -0400, Joel M. Halpern wrote:
> Minutes are not intended as a capture of the full content of the discussion
> that took place.
> They are to capture highlights and most importantly
> tentative decisions and action points.
Right. So you need to make a good judgement call whether what you add to the
notes is something that reader of the notes would like to read, e.g.:
salient point, not absorbed by the outcome of any furthre discussion.
As in: No harm done IMHO if a bit too much is written into the notes because
stuff that is not relevant anymore when the notes are finalized after the
meeting is easier deleted, than something that wasn't captured being remembered
(without re-spending 2 hours watching the recording).
> So while I can understand someone wanting to put a suggestion into the
> minutes for the record I am not sure what it will accomplish. If you want
> the Wg to pay attention to the suggestion, sending an email to the list has
> better reach, better visibility, and aligns with the goals.
Actually, i am not sure if this is always the case. The process of using
slots in WG meetings with audio and jabber channel and notes editing in the
end is a more thorough process of trying to create another stepping stone for
specific work items than just any mailing list conversation. Both have pro's and con's.
Cheers
Toerless
> With apologies if I misunderstood the point,
> Joel
>
> On 3/31/2022 5:32 PM, Carsten Bormann 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
- Chat comments for the record... Toerless Eckert
- RE: Chat comments for the record... Linda Dunbar
- Re: [irsg] Chat comments for the record... Carsten Bormann
- Re: [irsg] Chat comments for the record... Joel M. Halpern
- Re: Chat comments for the record... Gorry Fairhurst
- Re: Chat comments for the record... Eliot Lear
- Re: Chat comments for the record... Carles Gomez Montenegro
- Re: [irsg] Chat comments for the record... Toerless Eckert
- Re: [irsg] Chat comments for the record... Spencer Dawkins at IETF
- Re: [irsg] Chat comments for the record... Bob Hinden
- Re: [irsg] Chat comments for the record... Toerless Eckert
- Re: [irsg] Chat comments for the record... Bob Hinden
- Re: [irsg] Chat comments for the record... Gorry Fairhurst
- Re: [irsg] Chat comments for the record... Mark Nottingham