Re: Sergeant-at-arms engagement model

Michael StJohns <mstjohns@comcast.net> Fri, 11 October 2019 22:55 UTC

Return-Path: <mstjohns@comcast.net>
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 41255120106 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2019 15:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=comcast.net
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 e4sGZXW2PUPq for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2019 15:55:54 -0700 (PDT)
Received: from resqmta-po-12v.sys.comcast.net (resqmta-po-12v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:171]) (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 DBB18120059 for <ietf@ietf.org>; Fri, 11 Oct 2019 15:55:53 -0700 (PDT)
Received: from resomta-po-02v.sys.comcast.net ([96.114.154.226]) by resqmta-po-12v.sys.comcast.net with ESMTP id IzuCiBZMVp6xOJ3pBiXDwa; Fri, 11 Oct 2019 22:55:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1570834553; bh=MQZ+AKz320RH4X7nwqlpev434DMMquqFUqDdemHH8VE=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=2QnMSO/yx3NfFQxE4yUuwqiQ/EueaS1ijaZj7L/MEHN6kke2/XEG47VWcEDUcKInw cHa47w2uCbKJz5xs4WsDrzR3G7zTJOHSuyOvhg8tg0M4WauBrx6n08c9ssB59TwKP2 T/+uukqFuuhnGqlIzzyENgjwzozujKEWn7ttwZsV1mc9cagLLBSeSV5JWSyLh1+Y2O pE7L72ufHUXdmfzdBi3oZwDIW8gDoL7IJPFlD3erFbaPWu2qC/hlzSoRo5HzXbU3XL Hmq10UYQriSspvaGPRmpc6RqVpPR12IvTEenXn9DbYlGCbP0R5vDTaNgmis8HX8Or8 XkWNnJZNaf+Gw==
Received: from [IPv6:2601:152:4400:437c:1451:c7f2:710:4fe7] ([IPv6:2601:152:4400:437c:1451:c7f2:710:4fe7]) by resomta-po-02v.sys.comcast.net with ESMTPSA id J3p9i5LP4nXc9J3pAiqTck; Fri, 11 Oct 2019 22:55:53 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: Sergeant-at-arms engagement model
To: ietf@ietf.org
References: <9CC87E00-FFFD-44C1-ABD8-ED69C07F4561@ietf.org> <CABcZeBPLDyRLdQOxKftw5ti7=PT_LMjcwEOXUoL5Y4-Jz56HVA@mail.gmail.com> <CAChr6Sz0G_EqF5OD8CQAOipgT4HUAgU6_37SDZBhqeYeCY25Zw@mail.gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <b19f7dc1-f6eb-8e72-2b3a-c975c7087beb@comcast.net>
Date: Fri, 11 Oct 2019 18:55:51 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAChr6Sz0G_EqF5OD8CQAOipgT4HUAgU6_37SDZBhqeYeCY25Zw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F4A551D7AF172B8C4CF17A11"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yKqfsD1Zd8ulIIV9FKAo-H2hUUI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 11 Oct 2019 22:55:57 -0000

On 10/11/2019 12:31 PM, Rob Sayre wrote:
> On Fri, Oct 11, 2019 at 10:54 PM Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>> wrote:
>
>
>     I see that there are a bunch of open issues in the "Unprofessional
>     Commentary" definition. Can you say more about how you plan to
>     evolve that?
>
>
> Yeah, the Github page contains a circular definition (one instance 
> of "Unprofessional Commentary" is "Unprofessional Commentary"...)
>
> What are the boundaries around raising issues that are sure to offend 
> some set of people? For example, the IETF's use of Github might be 
> objectionable to some:
> https://www.bloomberg.com/news/articles/2019-10-10/microsoft-employees-call-to-end-github-ice-contract
>
> I think the rules are pretty clear when someone is spamming / swearing 
> / etc.
>
> thanks,
> Rob

  Please see my commentary on "respectful" "professional" and 
"considerate" at the end of 
https://mailarchive.ietf.org/arch/msg/ietf/2KfRrnvmpra7BDKICXsfQW1G7Rk 
as well as my comments on SAA do's and don'ts at 
https://mailarchive.ietf.org/arch/msg/ietf/pKBtsdVwLY3k8dkml3Wy3oANAJU. 
You've addressed only 1 of my 9 points (#2)

One of the issues we keep having is what are the  boundaries of 
basically ... (*sigh* translating to PC - it's hard to give up idioms 
that have been OK for most of my life ) calling a particular garden tool 
what is is rather than calling it a shovel.

Is a truthful statement "unprofessional" in the "profession" of the 
IETF? (cf our recent discussions on tone policing for the wide range of 
thoughts on this).

I'd like to see something like

>   Lying, being disingenuous,
> deflecting, distracting, ignoring are unprofessional; calling out lying,
> disingenuousness, deflection, distraction, and ignoring when there is
> substantial indication of one of these is not only not unprofessional,
> but required in a consensus based community for the community to
> continue to operate.

Entered into the discussion of what's unprofessional.

Lastly, I'd strongly recommend that the SAA be divorced from the Chair 
similar to the way that the Ombudsteam is.  E.g. chair appoints, SAA 
acts on their own without chair input.  Chair can replace at any time.   
Larger team than is currently there and works with the ombudsteam to 
resolve issues at dispute between the community (e.g. not just one 
person pushing back) and the SAA team.

Later, Mike