Re: RFC Series Editor (RSE) Statement of Work

Michael StJohns <mstjohns@comcast.net> Sat, 27 July 2019 23:08 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 B00E912018F for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2019 16:08:51 -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 FpSvAqNN7pkr for <ietf@ietfa.amsl.com>; Sat, 27 Jul 2019 16:08:49 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 68053120135 for <ietf@ietf.org>; Sat, 27 Jul 2019 16:08:49 -0700 (PDT)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id rVi6hlhq4c9cbrVo0h0ypM; Sat, 27 Jul 2019 23:08:48 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1564268928; bh=y4qL5cY9qoJzXnnZk9NToALQeHFC7tnt32Zo/hporE0=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=VzSgSmoUwB4Y8i0w9RlJHTtuq+AUmtNcef1KYwSOtzNi9Ntm3+bCwT5GKDQ6Hn6lz CZeKS88F2YhCYPyCWuN38PGjzya5KVQzAAUcNZ2elaBFYjgSOK0pPq5nJSWipuuqFY laGm+Zf/DPni5zZemULOFrWEviRs31lHAX2xVa+GInD0P1b3TnH0r5JPAGlJ6nqRkM RvIaP/CdAyUsU2v3DPMXhQ1ag8zCv3i105woBgPxD6i3tvbfJnbZ7aKm5TvwZhD8dY dvwjMcmjFp41GGO0Gyt8a2Uq0kMNUeOxkbEPYY6n9tGPsJVqNGaCV818Z2ZF6etBPH Pzr16tQUL0M0w==
Received: from [IPv6:2601:152:4400:437c:9c78:2dcd:9346:8ea4] ([IPv6:2601:152:4400:437c:9c78:2dcd:9346:8ea4]) by resomta-ch2-07v.sys.comcast.net with ESMTPSA id rVnzhAKaFBmBKrVo0hpc44; Sat, 27 Jul 2019 23:08:48 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: RFC Series Editor (RSE) Statement of Work
To: ietf@ietf.org
References: <9817BB4B-D828-4128-A70C-A8B966E6642F@encrypted.net> <CAL02cgRcGF80R_h5it_u7eGQrMjavpZ6_noEKb5vY5i1HqJYaA@mail.gmail.com> <7e82f47a-6a1d-8d3e-b183-e5159a071481@gmail.com> <9f7e969e-0374-2f9f-4ec6-e2d85a2fb819@gmail.com> <B027130E-8357-44C7-AAAF-FA11C249FD92@isi.edu> <F6C97564-6DD6-47A2-A9E6-5401F50BE4D5@cable.comcast.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <afa876d5-e0f0-44d1-ea03-85dba387e432@comcast.net>
Date: Sat, 27 Jul 2019 19:08:48 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <F6C97564-6DD6-47A2-A9E6-5401F50BE4D5@cable.comcast.com>
Content-Type: multipart/alternative; boundary="------------C9D2B757F987FD8E3C64DE8E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vM8CxKlAdYUcAXGTwRN-VlsCMRM>
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: Sat, 27 Jul 2019 23:09:01 -0000

On 7/27/2019 3:38 PM, Livingood, Jason wrote:
> On 7/25/19, 3:52 PM, "ietf on behalf of John Wroclawski" <ietf-bounces@ietf.org on behalf of jtw@isi.edu> wrote:
>>     The basic gestalt of a search committee process is to find the best person in the world for a job, whether or not that person would have otherwise applied, or even whether they had any idea beforehand that the job existed and they’d be good at it.
>>     The basic mindset of an RFP process is to pick the best person that applies.
>>     I think the IETF wants option one.
>      
> [JL] If this is the case, I wonder if it much matters to the community whether the role is an employee (full or part time) or a contractor (full or part time)? Or whether that might be left open-ended to depend upon the particulars of the country in which someone resides or their other commitments & preferences. IIRC, Sean Turner raised this question perhaps six months ago - which of course predated the current situation (so views may have changed).
>
> Jason
>      
>

Hi Jason -

Let me run a few terms past you (we can quibble about each, but this 
seems to be the general  set I've seen - there are variations within each):

Employee, contract employee, employee with a contract, 
contractor/consultant.

* Employee - generally at will employment, most positions within a 
company, can be told what to do, when to do it and how to do it 
generally by anyone above them in the food chain.  Generally only has a 
single employer (at least for salaried employees).

* Contract employee - an employee of an organization that is contracted 
by a second organization for work.  AKA Body shop contractor (but there 
are other variations on this for more senior folk - something like 
outside counsel arrangements with law firms).

* Employee with a contract - an employee, but with a contract that 
spells out conditions and modifications to the general labor practices 
of the company, may include bonus, and exceptional compensation items 
(e.g. golden parachutes); usually the way a number of the C staff in 
larger companies are hired.  Employment is generally not at will, but 
there are mechanisms for termination that can be exercised by each 
party.  Usual manager is either CEO or the board, or rarely another C staff.

* Contractor/consultant.  Has a contract for services to a given 
company, may do work for multiple entities.  May be tasked by the 
company (generally a specific contract POC), *_but not told when or how 
to do it_*.    May be an individual or a company.   Includes both common 
services contractors (e.g. IT) and Subject matter expert consultants.  
Contracts may be very specific in deliverables, or much more open 
ended.  May be duration or task based.

The main problem I see with trying to do this role as an "employee",  is 
that the LLC doesn't have a deep enough organization to handle an 
employee as senior and independent as the role needs to be.   It's 
possible that the "employee with a contract" model might work, but given 
our experience with Heather and the fact that we were only utilizing  
about 50% or so of her time, it might be difficult to cover the 
additional 50% of an full time employee and keep them fully engaged and 
interested year after year.

SME Consultant with a lot more constraints on who gets to give the RSE 
direction than we currently have seems to  me to be a better choice than 
either of the employee variations.

As I was writing the above, something struck me.   Heather (and Jon, Bob 
and Joyce before her) is as senior and competent in her field as the 
various lawyers we've engaged to deal with the LLC, Trust etc over the 
years are in theirs.  We wouldn't think it would be a good idea to 
micromanage the lawyers (and I'm sure they wouldn't tolerate it).  I'm 
not quite sure why we thought it was a good idea to provide the level of 
"oversight" and management to such a senior level position, and that 
appears to have been part of the problem.

Later, Mike