Re: IESG Statement on surprised authors

Warren Kumari <warren@kumari.net> Tue, 02 June 2015 22:34 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6E81B317C for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 15:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.722
X-Spam-Level:
X-Spam-Status: No, score=0.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 qWSJ7YZ7xsBS for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 15:34:20 -0700 (PDT)
Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) (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 4A20C1B3179 for <ietf@ietf.org>; Tue, 2 Jun 2015 15:34:20 -0700 (PDT)
Received: by oifu123 with SMTP id u123so137203099oif.1 for <ietf@ietf.org>; Tue, 02 Jun 2015 15:34:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JxFGGTI6yeSZFOh6O6UbthLOmDlwbPb05linncl9NCk=; b=LoKntjO3BvAXGpZqL0+Lu9Il6nBktkQFjMyEnaxvYwymH+ZWT3uHF72kHtbl6qNx6R bWgXM/uLDCD5y6VscH35IvukXy1Lr3geXaPSKKJA2Lr1lEn7sfGXbjkDaeBVPi6Pc4yo V4gCppfJ9gx3PtlBxNNdmktwKEZOAlHVnZi5p393Y6eH1pe/Dk0oydGkuJOSfmv2Axz8 dEXYe8A3inE3OCmt/B5urkmZMmUfuSw+keZQFg7S3KabqvDxDiLmVY+CQg+myrX6gCys j6N5JTIcw64uf9N0XtHMg0/nTknjdeO7rwhOVcuuMWFgCxPV7Sz5/fIxYqB31/qJajFs kIQQ==
X-Gm-Message-State: ALoCoQkRCqBAivTaroXz/NV20rGAHzAV0Je8eGP6nz3CVP39WxJB71fNRR3tYtBEkPB0apDnybip
MIME-Version: 1.0
X-Received: by 10.60.79.137 with SMTP id j9mr24656110oex.69.1433284459656; Tue, 02 Jun 2015 15:34:19 -0700 (PDT)
Received: by 10.202.196.75 with HTTP; Tue, 2 Jun 2015 15:34:19 -0700 (PDT)
In-Reply-To: <20150602215747.35990.qmail@ary.lan>
References: <C40606B1-4F3E-423C-8813-1AAD2EF19A0D@nominum.com> <20150602215747.35990.qmail@ary.lan>
Date: Tue, 02 Jun 2015 18:34:19 -0400
Message-ID: <CAHw9_iL__nCxZb-WqU5uost8cZq-fBixVZnHnna5YJr9+zOjpA@mail.gmail.com>
Subject: Re: IESG Statement on surprised authors
From: Warren Kumari <warren@kumari.net>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5j3u-TAapxXf1P9M_yDXdb-NfFM>
Cc: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 02 Jun 2015 22:34:22 -0000

On Tue, Jun 2, 2015 at 5:57 PM, John Levine <johnl@taugh.com> wrote:
>>> So  there is an opportunity for a surprise author to alert the IESG & RFC
>>> editor.
>>Yes, there is a chance to publicly humiliate the submitter. I would not want to do that, so your proposed solution doesn't address my need.

Why not?
There are many things that we do where we self police and train people
into more appropriate behavior by pointing out where they are being
anti-social. We try and do this privately, but if that doesn't work,
we often do it in a more public venue.
For example, I remember an instance where I was having a side
conversation in the middle of a working group meeting and you
(rightly) poked me and asked me to shut up or take it outside. If I
had continued to do this, I would have expected you to ask more loudly
and / or ask the chairs to request that I shut up.
There are many places where we act the way that we do simply because
of social convention, which is arrived at by communicating what is
appropriate and what isn't - for example, I walk the extra few steps
to throw away my chewing gum in the trash receptacle  instead of
simply sticking it on your laptop. If I were to smear it all over your
keyboard, I'd expect you to object -- and if I did it repeatedly I'd
expect you to object in a more and more public manner, until I learnt
what is, and what isn't appropriate.

If you are walking down the road an a pickpocket grabs your wallet and
runs off, would you feel uncomfortable shouting "Stop! Thief!!!"
because it may humiliate him?

>
> Considering that most of these situations appear to be mistakes, why
> should correcting this mistake be more humiliating than correcting the
> zillions of other mistakes fixed from one version of an I-D to the
> next?

Yup - if this is an accident / mistake then mentioning it publicly it
need not humiliate anyone[0] - and if it done maliciously then I think
it is perfectly appropriate to call it out publicly to get the
behavior changed. You could always email the authors privately first
and expect them to do the right thing - if I'd (mistakenly) added you
as an author to a draft I'm writing, I'd immediately release a new
version without you listed, and post a note to the list (and probably
put an editor's note at the top of the document) saying something like
"Sorry all. I'd mistakenly listed Ted as an author on version -xx of
this document. I'd thought he'd agreed to be an author and contribute
text, but it seems I misunderstood". If this was an honest mistake I
wouldn't be humiliated -- and if this sort of thing *did* make me feel
shame, I'd simply make very sure that everyone who I listed as an
author had agreed to be one.

When used maliciously this tactic only has any value because it
creates the perception of support - by removing this incentive the
tactic becomes valueless.

W
[0]: Especially if done with tact - coming out and saying "Bob is a
big doo-doo head. He added me to this without my permission and so is
scum" isn't. Mentioning that you don't remember having contributed to
this document or having agreed to author, and asking Bob to release a
new version without you listed should be fine. I've been on both sides
of this - I've added people who I thought had agreed to contribute
(and then discovered that they hadn't meant to give that impression),
and also been surprised to be added. In at least one case I've stood
at the mic and said "I think that's a great idea...", only to discover
that I was an author :-)[1]. In all cases it was settled peaceably,
and without drama - but if it had been done maliciously I would feel
no guilt calling people out on it.

[1]: Actually, in this particular case I had contributed significantly
to the document, it was just being discussed in a manner where I
didn't recognize which document it was...

> R's,
> John
>
> PS: If it's not clear, this is a real question.
>
>
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf