RE: [Ext] [irsg] Minutes being messed with?

"STARK, BARBARA H" <bs7652@att.com> Fri, 09 August 2019 11:13 UTC

Return-Path: <bs7652@att.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 8D2D312014B for <wgchairs@ietfa.amsl.com>; Fri, 9 Aug 2019 04:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 2Fze9LW-2VHQ for <wgchairs@ietfa.amsl.com>; Fri, 9 Aug 2019 04:13:53 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6496120161 for <wgchairs@ietf.org>; Fri, 9 Aug 2019 04:13:52 -0700 (PDT)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x79B63t1028298; Fri, 9 Aug 2019 07:13:28 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049459.ppops.net-00191d01. with ESMTP id 2u976c8my6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 09 Aug 2019 07:13:27 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x79BDR3g008525; Fri, 9 Aug 2019 07:13:27 -0400
Received: from zlp30486.vci.att.com (zlp30486.vci.att.com [135.47.91.177]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x79BDEKC008350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 9 Aug 2019 07:13:22 -0400
Received: from zlp30486.vci.att.com (zlp30486.vci.att.com [127.0.0.1]) by zlp30486.vci.att.com (Service) with ESMTP id 68D054009E8A; Fri, 9 Aug 2019 11:13:14 +0000 (GMT)
Received: from GAALPA1MSGHUBAA.ITServices.sbc.com (unknown [130.8.218.150]) by zlp30486.vci.att.com (Service) with ESMTPS id 565E04009E79; Fri, 9 Aug 2019 11:13:14 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.84]) by GAALPA1MSGHUBAA.ITServices.sbc.com ([130.8.218.150]) with mapi id 14.03.0439.000; Fri, 9 Aug 2019 07:13:14 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "MORTON JR., AL" <acm@research.att.com>, 'Paul Hoffman' <paul.hoffman@icann.org>, "'wgchairs@ietf.org'" <wgchairs@ietf.org>
Subject: RE: [Ext] [irsg] Minutes being messed with?
Thread-Topic: [Ext] [irsg] Minutes being messed with?
Thread-Index: AQHVRdaFEXnIuVzhwE+8N9h5jgc8QabhZKGAgAAWnYCAAAK/gIAAAmWAgAB8AYCAAAaigIAAAXwAgAKrXYCACeALAIAACVUAgAGQJYCAAAZoAIAAAssAgAAR+4CAACg+gIAABS4AgAEryoCAAC1HAP//3dZQgABQvICAANb9gP//6TwA
Date: Fri, 09 Aug 2019 11:13:13 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114E25CF52@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <2C180C92-9DE3-416B-8A6B-7765BCAEEDB1@eggert.org> <DB7PR07MB51483F20F4261CDE848E3EAFE0DD0@DB7PR07MB5148.eurprd07.prod.outlook.com> <1f00cab2-991f-7f0c-f061-a692f10cad16@gmail.com> <A6240C58-14C4-4900-A9CD-86779D7A44BC@eggert.org> <DB7PR07MB51487A4B4E8F38979893FFE4E0DD0@DB7PR07MB5148.eurprd07.prod.outlook.com> <92621f1a-7050-1558-86dc-1836e17c6f7c@bluepopcorn.net> <473915be-8fe1-ba82-fb30-8bd05751cb32@levkowetz.com> <CAOdDvNqDZN6kR_jv+Em3PoSR9sWx8U2JTLWFzJtCVY=QZrsS3A@mail.gmail.com> <7466_1564562703_5D41550F_7466_455_3_65b0b515-b273-177b-84ce-210ef716f0cd@orange.com> <DBFDF146-C2AD-49A8-AED0-B7112733D29E@gmail.com> <A09242D6-B4A5-49AE-9CFD-78E34FB638FE@tzi.org> <B8AE42B2-8A28-4041-AD2F-0136900BAE4F@gmail.com> <8B059BA9-B235-4A1E-9AC2-5339C1C9CE13@akamai.com> <7df564fa-5940-4c92-1d73-856bffc81ce1@bluepopcorn.net> <F7ECF7DB-9639-40EA-9774-82DB940FA342@tislabs.com> <42E6A418-879F-482B-BDAD-66D4DD46475C@gmail.com> <693C8CDA-76DE-4C6F-B19D-7500C962C66F@tzi.org> <1032b409-1905-ec3a-b271-f2a23ca4beac@nostrum.com> <241D5A95-D3DC-41C7-9AB8-D2260F0A0AAA@tzi.org> <2D09D61DDFA73D4C884805CC7865E6114E25BBE0@GAALPA1MSGUSRBF.ITServices.sbc.com> <B0A1E5CF-8E79-42B0-BCE4-A3D5A6B71548@icann.org> <4D7F4AD313D3FC43A053B309F97543CFA0ADB084@njmtexg4.research.att.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CFA0ADB084@njmtexg4.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.201.29]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-09_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=741 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908090114
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/LRwPk3Sj9w8-NLMH_Z242Ks-4jo>
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, 09 Aug 2019 11:13:56 -0000

> > [ As the person who started this thread... ]
> >
> > There is a good chance that the (temporary) damage happened after the
> > meeting. Thus, knowing this in advance, I might export the results at
> > the end of the meeting.
> >
> > Even if I don't, as long as the history function works, I can alway
> > reverse the damage.
> [acm]
> There was an unfortunate Etherpad crash during one set of sessions some
> years back - that experience caused me to occasionally scrape the screen to a
> text file while taking minutes, and periodically asking my minute-takers to
> scrape as well.
> 
> (Status of the built-in history recall unknown after recovery in connection
> with this one failure instance.)
> 
> >
> > Given that, I don't see any good reason for the proposed premature
> > optimizations.
> [acm]
> If the over-writes were accidental, registered participants may have
> performed them, so I tend to agree with Paul and Barbara.

My personal "best" practices are to click the star on Etherpad at the very end of a session so it marks a specific point in the history, and to immediately copy the contents and email them to the chairs. If I think they need refining or there's a 2nd session still coming (so I don't want to email them to the chairs right away), I'll save a copy to a local text file. Just in case.
Barbara