Re: RFC Series Editor (RSE) Statement of Work

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 29 July 2019 18:16 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 DE01A120025 for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2019 11:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 goXTOyahC-1H for <ietf@ietfa.amsl.com>; Mon, 29 Jul 2019 11:16:02 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 1872112001A for <ietf@ietf.org>; Mon, 29 Jul 2019 11:16:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 45y7D208y4zkpc1; Mon, 29 Jul 2019 11:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1564424162; bh=rZ1RBzcg8Z2IE+7e+WwbNBbZRbRTdg4TEElFnuq2Y3A=; h=Subject:To:References:From:Date:In-Reply-To:From; b=osdOarB8AEnmdSqz8FYJ/SIUXl4bVgX7CVz5K1tDkbFMUKyAsr76I/mi5FTtBzD9F XJVW8rvnI8+HplL9y9FYsg/0OyHfOG6fQVWG1KUYjRAoNBZkmbJNnlUoA45LYQdpcB mxqRsVzrMSD4TkIr9rO/6DG+eOcay4JfB9uxbLCU=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.20.7.244] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 45y7D13739zFptL; Mon, 29 Jul 2019 11:16:01 -0700 (PDT)
Subject: Re: RFC Series Editor (RSE) Statement of Work
To: Wes Hardaker <wjhns1@hardakers.net>, IETF discussion list <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> <afa876d5-e0f0-44d1-ea03-85dba387e432@comcast.net> <ybl7e80n26m.fsf@w7.hardakers.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <c94f02c6-dc58-d529-aa9c-480ea832ee8e@joelhalpern.com>
Date: Mon, 29 Jul 2019 14:15:58 -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: <ybl7e80n26m.fsf@w7.hardakers.net>
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/3jm2wQpy9rvvkETbbl22Hck7Vaw>
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: Mon, 29 Jul 2019 18:16:05 -0000

     I agree that the way we behave towards our staff (senior and 
otherwise) is the important part.  Unfortunately, we have two problems 
in that area.
     First, we have recently been interacting with the RSE in ways that 
seem unlikely to encourage strong professionals to expect positive 
treatment.  I do not think that was the intention, even of those who 
want changes in the series.  But I think it is a likely effect.
     Second, we are in the process of hiring the person who, if the RSE 
were to be an employee, would be that person's boss.  So it is hard for 
anyone interviewing to judge how the organization will work.  Again, 
that was not a deliberate choice on anyone's part.  But it is an 
important part of the reality.

     It seems to me therefore that we have to find ways to define and 
describe the job so that we can give likely candidates confidence in 
what they are likely to face / be supported by.  While the formal part 
of that falls to the RSOC, we all share in the informal part of it.

Yours,
Joel

On 7/29/2019 2:08 PM, Wes Hardaker wrote:
> Michael StJohns <mstjohns@comcast.net> writes:
> 
>> 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):
> 
> I think your terms and definitions are reasonable, so I won't quibble
> about those. I've been on both sides of most of those terms.  And none
> of them are as rigid as you state, of course, because there is a lot of
> gray area in any definition list.  I've seen contractors be told exactly
> what to do and be micro-managed (and they put up with it or they lose
> the contract), and I've seen employees be let free to roam and do what
> they thought was best because they were hired to be smart.
> 
> 
> 
>> * 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).
> 
> Your use of "can be" in the employee definition is the important part.
> Its not the definitions of the position type that matters.  It's how we,
> as the organization and people that are defining the role interact and
> manage said role.  If we want to attract and keep good talent for the
> critical RSE role, then the way to do that is by being the type of
> organization and manager that will attract talented folks and make them
> want to stick around regardless of the business relationship type we select.
> 
> [...other quotes snipped for length...]
>