Re: RFC Series Editor (RSE) Statement of Work

Jari Arkko <jari.arkko@piuha.net> Mon, 22 July 2019 22:58 UTC

Return-Path: <jari.arkko@piuha.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 225FC1200BA for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 15:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 gqSc57ugTVDD for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 15:57:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 8824A1200F1 for <ietf@ietf.org>; Mon, 22 Jul 2019 15:57:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 023B76601A1; Tue, 23 Jul 2019 01:57:57 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aslVXL87xrPM; Tue, 23 Jul 2019 01:57:55 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 40EF86600A8; Tue, 23 Jul 2019 01:57:55 +0300 (EEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RFC Series Editor (RSE) Statement of Work
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9f7e969e-0374-2f9f-4ec6-e2d85a2fb819@gmail.com>
Date: Mon, 22 Jul 2019 18:57:53 -0400
Cc: IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <09F3525C-6789-4AEE-BA22-DD06B7AB7E30@piuha.net>
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.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HZ7dGJ3PyWYRv10RdW9x9j8PVA0>
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, 22 Jul 2019 22:58:01 -0000

First, big +1 to mentioning Joyce more often :-)

Second, to the substance of Brian’s comments. My personal comments, only of course:

> 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 fully agree!

(With a small caveat of relevant RFCs being flexible enough to allow that. But RFCs can be changed.)

> Obviously there will be a finite budget limit that the search committee will bear in mind. But we aren't trying to find the cheapest RSE; we're trying to find the best one.

I agree with you.

> 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.

I agree that a RSE is a very high level leader. But I’m not sure it directly follows that no statement of work or definition of role should exist. Usually when there’s a role to be filled somewhere in the world, even for a high level leader, there is some definition of what’s the scope and the expectations. But perhaps you meant to have an argument that the current RFC and/or SOW are far too focused on details and should emphasise the leadership aspect and not the details. And should clearly leave room for the selected leader to drive into a direction that she or he will eventually find the best direction. I’d be much easier convinced of that.

I have a similar reservation about appropriateness of “competitive bidding process”. I fully agree that making a search primarily a competition (and particularly, a finance-based competition) for any leadership position is a bad idea. But whether you’re looking for a CEO, Area Director, or the RSE there’s at least some possibility of alternative choices. If competition is the only thing in the search team’s mind, that would be bad. But they need to be aware of the potential out there when they are doing a search.

Jari