Re: Minutes being messed with?

Bob Hinden <bob.hinden@gmail.com> Tue, 06 August 2019 15:33 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 E7F8F120145 for <wgchairs@ietfa.amsl.com>; Tue, 6 Aug 2019 08:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Q-7wYO2HTBla for <wgchairs@ietfa.amsl.com>; Tue, 6 Aug 2019 08:33:23 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 C3CC21203D2 for <wgchairs@ietf.org>; Tue, 6 Aug 2019 08:33:22 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id v19so76928152wmj.5 for <wgchairs@ietf.org>; Tue, 06 Aug 2019 08:33:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NQKw/HyALMd3h5Jn8UjykCeqHGYhmHjYaje1dEAXmD4=; b=pg94Bs4mCS8lOfX8me0HFKn0o1a+WtbvKa2APL/GPDYJdCtuTSDRRGwKT47wy0RtRQ EDwzd9HoVO7PRXk6GUL2hcSeqdiXhxpazq7UlDuxG5+s3RZ+VEPaMe/WpYUeJTuiTRyO vqQOJ1Xlg1DbGNPQLTA7KzDoMBt+NpNv81jPNYosxmAIQ6vYmro4LnlWefcjZdGHTMPN iYgHd13F2qwedfnM+KJkB7FsYsPz3B8NTonGGOz2kncD2e3Pa0fLeUzAnT4+U5rPDjLb kCIg2ax1saMDx8MMBsb0qjZkmz8NS0I9JU++OWlYkrk4MlLLvZOdK725xaRzfyJUq6qp /lKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NQKw/HyALMd3h5Jn8UjykCeqHGYhmHjYaje1dEAXmD4=; b=erxcAYfniFzAOJNwqRtp+2799uWrvAkJKOLJovJZ+X2I1fm46Ko8mOHuHbf/915yNM YX2kgKx48ojB6aG/nrdvD4gqfDOljXu5MOu8loH44qqN7n8Wx6fJAytC0G4V1sIlMN3J +3aw+PovU5NmDRa5pI5T+H4NHmBkASw6+60GVCxcoScs0BjtSsxc21vvOyGMn24Of0gr GwSNY6WN63BWDQa/jkjygl/RGvmcgd6aeKZ2AL+C0CO2StXwxRmIcn4TP+kEyTvzDaUj X/6BcRhZjaX0g6nr7j38DoPLh5Nqg4Gc1BHp9Sc4Ig+bYDQrxXrOOdJa4cYypfIxDf3C yKmA==
X-Gm-Message-State: APjAAAVotoFbw3AcQy/R3EFcvrtazCPOMOdaBIflY2DH1loI1KYxeDAK 70L4St6HIdmQypAcSmEDsbHixCXp
X-Google-Smtp-Source: APXvYqxn6+r0xVbfJU4ZT5ap+M8KvgOEDSyaFov2AwF4BRymOedYAqVlU//faD0EgDCron1Jl3K4UA==
X-Received: by 2002:a05:600c:28d:: with SMTP id 13mr5425063wmk.5.1565105600965; Tue, 06 Aug 2019 08:33:20 -0700 (PDT)
Received: from [10.0.0.199] (c-24-5-53-184.hsd1.ca.comcast.net. [24.5.53.184]) by smtp.gmail.com with ESMTPSA id e19sm122080600wra.71.2019.08.06.08.33.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Aug 2019 08:33:20 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <DBFDF146-C2AD-49A8-AED0-B7112733D29E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4B26D82C-BC4E-4089-A8F0-CF6F6D96C261"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Minutes being messed with?
Date: Tue, 06 Aug 2019 08:33:16 -0700
In-Reply-To: <7466_1564562703_5D41550F_7466_455_3_65b0b515-b273-177b-84ce-210ef716f0cd@orange.com>
To: IETF WG Chairs <wgchairs@ietf.org>
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>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ViIDN8CQhgGsMdgfKnFjh3ZOovA>
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: Tue, 06 Aug 2019 15:33:25 -0000

In 6man, as I suspect in most other w.g.’s, the minute takers use Etherpad to take the raw minutes.   It's a problem, if others can rewrite it during or after the fact.

For the purpose of producing w.g. minutes, it would be nice to be able to lock its write access to the minute takers.   We usually know who they are in advance.

Is this possible in Etherpad?   That is, limit write access while allowing everyone else to have read access.

I note that Etherpad has the ability to show users, this is helpful, but since there is no login, doesn’t solve the problem.

Suggestions?

Bob

p.s. I note the parallels here with the issues we see on the Internet.  A tools that works great for a set of users who are aligned, but then it breaks when you get other users who have other intents.  Sigh...



> On Jul 31, 2019, at 1:45 AM, julien.meuric@orange.com wrote:
> 
> Hi,
> 
> I agree with Patrick on this. I'm among those people who are reluctant
> to create accounts on websites, especially if:
> - creating the account is more effort/out-of-context action than the
> info I was about to share/get (our case here),
> - the 1st benefit is mainly to the system and barely to me (our case
> here too).
> If I didn't already have a datatracker account, I wouldn't mind using an
> anonymous "edit" button but I would certainly not create an account just
> to update my speaker name in Etherpad...
> 
> Julien
> 
> 
> On 29/07/2019 17:59, Patrick McManus wrote:
>> please don't add a datatracker login to the etherpad requirements - it
>> is already hard enough to find people to take minutes.
>> 
>> however an anonymous "click to edit" button would do fine and likely
>> prevent this from accidentally happening without breaking the no-doubt
>> useful translation feature being used.
>> 
>> On Mon, Jul 29, 2019 at 11:54 AM Henrik Levkowetz
>> <henrik@levkowetz.com <mailto:henrik@levkowetz.com>> wrote:
>> 
>> 
>>    On 2019-07-29 17:30, Jim Fenton wrote:
>>> On 7/29/19 1:06 AM, Van De Velde, Gunter (Nokia - BE/Antwerp) wrote:
>>>> Yep, they were swapped, while I was typing.. it confused the
>>    heck out of me .
>>> 
>>> If this is disrupting things, and it sounds like it is, perhaps
>>    Etherpad
>>> should require a Datatracker login in order to edit. That would
>>    at least
>>> provide some accountability, and we would know who we need to
>>    "coach".
>> 
>>    Yes, this has been my conclusion from the thread so far.
>> 
>>            Henrik
>> 
>>> I missed the ADD BOF, so I tried looked at Etherpad afterwards
>>    and it
>>> was a bunch of Cyrillic text. Glad to know about the history slider!
>>> 
>>> -Jim
>>> 
>>> 
>>> 
>> 
> 
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>