Re: Barely literate minutes

Barry Leiba <barryleiba@computer.org> Thu, 29 November 2012 15:11 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B261E21F8773 for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 07:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WCKSiGUUGPMr for <ietf@ietfa.amsl.com>; Thu, 29 Nov 2012 07:11:32 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id D6A3521F8660 for <ietf@ietf.org>; Thu, 29 Nov 2012 07:11:31 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so12336691lah.31 for <ietf@ietf.org>; Thu, 29 Nov 2012 07:11:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=5zzR2JPvlxxZVsuXbl/nzIQWJOmHcROEVYPlLbHha0o=; b=iQN+zLgc3BcIoQM7BNs1s7BB04QGMyz1ydt/od0strbw6q/XcNw2GWz7P+/HMO1DS7 WAHH4VEwSIb4O0G4cSyfHcHvvCQcj8kBCNPyFxPSunlk+nFhnxpQr02Sjc50zHdvA8eQ wSuen73eK79YWYl+i347NSWI9KbIdeT5MvKfzZlGnrqY2+fByAaOk9yqwVRJ1FYYf6hj exnOLxrZDOkfUW4zdCpLnSK2wsZEvNj30POoWC5fyPG88MDrgxc9a8dPKpc7FB2uKavr QeKtlIKE02pgckUb1fO2p2wI7GVw/gXeKl3dXYmOw32H5e6wwyD8pIfB3ynSYlNNh2DD 79EQ==
MIME-Version: 1.0
Received: by 10.112.10.34 with SMTP id f2mr10067480lbb.47.1354201890612; Thu, 29 Nov 2012 07:11:30 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Thu, 29 Nov 2012 07:11:30 -0800 (PST)
In-Reply-To: <50B696B0.30904@qti.qualcomm.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com>
Date: Thu, 29 Nov 2012 10:11:30 -0500
X-Google-Sender-Auth: -wU1QHY-AFNvDsUWqRs4G3Fi38s
Message-ID: <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>
Subject: Re: Barely literate minutes
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 15:11:32 -0000

On Wed, Nov 28, 2012 at 5:56 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
...
> chair needs to (with the help of minutes takers and other participants) post
> detailed notes of the discussion to the list and ask for objections. That
> serves two functions: (a) It makes a record of work that was done; and (b)
> it gives people who don't attend meetings (including new folks who come
> along) a chance to participate and voice their concerns. *Achievement* of
> consensus might have to occur f2f for some issues in some WGs, but it seems
> to me that *assessment* of consensus must be completely possible on the
> list, even if the only poster to the list is the chair with all of the f2f
> notes.

What I would prefer to see is that in addition to minutes there be
separate messages posted to the list for each document, detailing the
discussion of that document in the meeting and the changes that will
result from the discussion.  That can be posted by the chair, but I'd
really expect it to come from a document editor.  That makes sure that
everyone can see what the document editor heard and intends to do with
the document, and allows the working group to continue the discussion
or say, "Yes, that's what we heard as well, and it's fine."

And I think that should be posted as soon after the meeting session as
possible.  It should definitely not wait for the document updates to
be done, perhaps weeks later, after everyone who was there has
forgotten the details.

I think I have a topic to discuss at the App chairs lunch in Orlando.  :-)

Barry