Re: Revised proposed IETF LLC Community Engagement Policy

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 15 October 2020 03:09 UTC

Return-Path: <jmh@joelhalpern.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 55E853A1228; Wed, 14 Oct 2020 20:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 kOqJPTNxoa_a; Wed, 14 Oct 2020 20:09:53 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 E0B773A1225; Wed, 14 Oct 2020 20:09:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4CBZ5Y4nByz6G8Mn; Wed, 14 Oct 2020 20:09:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1602731393; bh=l7d2jFI/au/+3OoKtAxLLTNePKuM478xpoR+xe1D164=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=XtBhdzZwv42TJnCMxSjsi9/L8wDwy9hOF1gpCfN6MJl9PNKqW086rqPCieOsd6scJ x9tbVLYdGK5pxm42rEfdBSnraj2Bfj24toLfw6kz2r93q4ZPaLB8GraB5ySt88PV1c 4FT/svtt/SoM3Wwf2WXbQIcCqa6SYOHvqlI0ACw0=
X-Quarantine-ID: <T-YYw-_UuEkt>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4CBZ5Y0Pfpz6GDBW; Wed, 14 Oct 2020 20:09:52 -0700 (PDT)
Subject: Re: Revised proposed IETF LLC Community Engagement Policy
To: Jay Daley <jay@ietf.org>
Cc: IETF discussion list <ietf@ietf.org>
References: <4967F60A-89A6-4A5A-BD0F-C65DD05F3C4F@ietf.org> <3253184c-6e45-763e-7d6b-f61402baf0c6@joelhalpern.com> <F3907B0B-334F-4F51-9F43-3F80D1619C81@ietf.org> <E51BF92F-91F7-46DD-875B-ACF8F5C9F9D1@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <11d90766-3c15-eafc-dcbf-58bff5f7ee45@joelhalpern.com>
Date: Wed, 14 Oct 2020 23:09:50 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <E51BF92F-91F7-46DD-875B-ACF8F5C9F9D1@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lbKqjomnlavOdsGMNYU66aYrMoo>
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: Thu, 15 Oct 2020 03:09:55 -0000

Jay, I think it would be good if the Volunteering policy was explicit 
that this restrictive clause would take LLC board action.  And I would 
expect it to say that the LLC would state this if possible when the role 
is defined.  Just so everyone is on the same page.  (I dislike vague 
clauses, but at least if we know who that helps.)

Yours,
Joel

On 10/14/2020 10:41 PM, Jay Daley wrote:
> 
> 
>> On 15/10/2020, at 3:40 PM, Jay Daley <jay@ietf.org 
>> <mailto:jay@ietf.org>> wrote:
>>
>>
>>
>>> On 15/10/2020, at 2:06 AM, Joel M. Halpern <jmh@joelhalpern.com 
>>> <mailto:jmh@joelhalpern.com>> wrote:
>>>
>>> Thank you for the improvements.
>>> One question I did not think to ask originally.
>>>
>>> The policy says "Some Covered Roles may require Covered Individuals 
>>> to be explicitly prohibited from acting as community volunteers." 
>>>  That seems to be deliberately vague.  Who decides about this?  How 
>>> is it communicated / appealed / understood?  Can you explain why the 
>>> clause is needed?
>>
>> Yes it is deliberately vague and part of the reason for that is the 
>> feedback received from others that we may want to keep something like 
>> that in place.  The clause is basically there in case there is a clear 
>> conflict of interest that needs to be addressed and it the clause is 
>> not there now then adding it later becomes considerably more 
>> difficult.  I think it’s a reasonable safeguard should that become 
>> necessary.
> 
> Sorry, I forgot to say that this would probably be an LLC board decision 
> given the importance of this type of action to the community.
> 
> Jay
> 
>>
>> BTW see my next email about the relationship between this and the COI 
>> policy.
>>
>> Jay
>>
>>>
>>> Thank you,
>>> Joel
>>>
>>> On 10/13/2020 11:09 PM, Jay Daley wrote:
>>>> Thanks again for all of the feedback.  A revised draft is available 
>>>> [1] that addresses all of the open issues and feedback on this 
>>>> revised draft is now sought.  Please note the following:
>>>> 1.  The contentious text has been removed
>>>> 2.  One section, now called "Volunteering in the IETF" contains a 
>>>> minimal set of provisions around volunteering.  This is almost 
>>>> identical to a previous section that was not the subject of feedback 
>>>> and has been adjusted to apply to all Covered Individuals with the 
>>>> meaning otherwise unchanged. The key provisions are:
>>>> - an acknowledgement that anyone can also be a community volunteer
>>>> - an acknowledgement that some contracts may have restrictions due 
>>>> to the nature of the contract
>>>> - a requirement to avoid conflict of interest from volunteering
>>>> - a requirement to make it clear to people what role someone is 
>>>> engaging in
>>>> 3.  The phrase "acting as an individual" is not used as there is an 
>>>> argument that some roles do not allow people to step out of them 
>>>> (mine for example [2]) and this way avoids trying to resolve that or 
>>>> put rules around it.
>>>> 4.  The important sections on "Community Feedback" and "Engagement 
>>>> Mechanisms" remain unchanged.
>>>> As a reminder, please provide feedback by 26 October 2020 00:00 UTC 
>>>> using any of the following methods:
>>>> * Raising an issue on the Github repository [3]
>>>> * Direct to the IETF Executive Director atexec-director@ietf.org 
>>>> <mailto:exec-director@ietf.org>
>>>> * Direct to the IETF LLC Board (not including the IETF Executive 
>>>> Director) atllc-board-only@ietf.org <mailto:llc-board-only@ietf.org>
>>>> * To theietf@ietf.org <mailto:ietf@ietf.org>list
>>>> [1] 
>>>> https://github.com/ietf-llc/community-engagement-policy-consultation/blob/latest-updates-from-consultation/DRAFT%20Community%20Engagement%20Policy.md
>>>> [2] 
>>>> https://mailarchive.ietf.org/arch/msg/ietf/6ZgAe1stcpFPlsx3SXOxEEppkLs/
>>>> [3] 
>>>> https://github.com/ietf-llc/community-engagement-policy-consultation/issues
>>>> Jay
>>>
>>
>> -- 
>> Jay Daley
>> IETF Executive Director
>> jay@ietf.org <mailto:jay@ietf.org>
> 
> -- 
> Jay Daley
> IETF Executive Director
> jay@ietf.org <mailto:jay@ietf.org>
>