Re: RFC Series Editor (RSE) Statement of Work

John Wroclawski <jtw@isi.edu> Thu, 25 July 2019 19:51 UTC

Return-Path: <jtw@isi.edu>
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 475441201CE for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2019 12:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 vFLsV87SqAlW for <ietf@ietfa.amsl.com>; Thu, 25 Jul 2019 12:51:45 -0700 (PDT)
Received: from mail-d.ads.isi.edu (mail-d.ads.isi.edu [128.9.180.199]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD9871201C6 for <ietf@ietf.org>; Thu, 25 Jul 2019 12:51:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.64,307,1559545200"; d="scan'208";a="15867519"
Received: from 30-10-243.wireless.csail.mit.edu ([128.30.10.243]) by mail-d.ads.isi.edu with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2019 12:51:45 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: RFC Series Editor (RSE) Statement of Work
From: John Wroclawski <jtw@isi.edu>
In-Reply-To: <9f7e969e-0374-2f9f-4ec6-e2d85a2fb819@gmail.com>
Date: Thu, 25 Jul 2019 15:51:43 -0400
Cc: Richard Barnes <rlb@ipv.sx>, Sarah B <sbanks@encrypted.net>, RSOC <rsoc@iab.org>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B027130E-8357-44C7-AAAF-FA11C249FD92@isi.edu>
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>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ugkQnTwhZ5d_UqNbQRACQHsZ_eY>
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, 25 Jul 2019 19:51:49 -0000

> On Jul 22, 2019, at 8:52 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> The RFC Series Editor has always been treated as a senior colleague, and part of our community leadership; never as a hired hand, because it isn't the sort of job that can easily be measured or priced. Obviously, as a practical matter, the RSE has to be paid for their time and expenses, but it really doesn't matter whether that's as an employee, an individual contractor, or via their existing employer. That's basically a clerical matter, once the right person has been identified.
> 
> I now think that the notion of a pre-defined statement of work and a competitive bidding process is *completely* inappropriate. What we should do, IMHO, is identify the right person by a search process with a well-informed search committee, and then leave IETF LLC to figure out any necessary employment or contractual details later.

Walking in from the distant sidelines, I would like to +1, or perhaps +1000, this note.

It hadn’t crystalized for me until Brian said it, but I think he’s got the key point exactly.

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.

To address a couple of points raised in replies to Brian, a) search committees absolutely _do_ work from written descriptions of the job, its key objectives, and likely-desirable candidate qualifications, and b) senior/executive search committees do indeed do this type of thing successfully all the time, and c) absolutely there are a great number of details to work out about responsibilities, structuring, communications, etc. that are extremely important as well.

But the key point is, I think, the IETF wants option one.

Cheers, —john