[Rfced-future] Proposal for RSCE recruitment committee and process

Jay Daley <exec-director@ietf.org> Tue, 01 February 2022 01:50 UTC

Return-Path: <exec-director@ietf.org>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC1043A03F7 for <rfced-future@ietfa.amsl.com>; Mon, 31 Jan 2022 17:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 YOjGhlyFhHnb for <rfced-future@ietfa.amsl.com>; Mon, 31 Jan 2022 17:50:08 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9F373A03AA for <rfced-future@iab.org>; Mon, 31 Jan 2022 17:50:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id B92EE4096D32 for <rfced-future@iab.org>; Mon, 31 Jan 2022 17:50:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zerk38IrwRez for <rfced-future@iab.org>; Mon, 31 Jan 2022 17:50:07 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 585234096D30 for <rfced-future@iab.org>; Mon, 31 Jan 2022 17:50:07 -0800 (PST)
From: Jay Daley <exec-director@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
Message-Id: <119A2179-3949-46F3-9B42-4F1DD7BBF98E@ietf.org>
Date: Tue, 01 Feb 2022 14:50:03 +1300
To: rfced-future@iab.org
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Rs2KQ9vA3Hmjr8NL3vdpX3dhp7Y>
Subject: [Rfced-future] Proposal for RSCE recruitment committee and process
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2022 01:50:12 -0000

In line with Peter’s proposed text [1], here is my proposal for the RSCE selection committee and recruitment process, which I would like community feedback on.  I realise that things have not been fully settled but this recruitment is going to take some time and the sooner we can start the better.  If this is too soon then please let me know.

# Rationale

1.  The RSCE role is very different from the previous RSE role and for the recruitment to be a success it is critical that the committee recruits to the new RSCE role as defined.  It would be problematic if anyone on the committee was not clear about the new role and was inadvertently targeting the old role.  The committee members therefore need detailed knowledge of the new role, in all its subtleties.

2.  The committee needs detailed knowledge of the working environment in which the new RSCE will operate in order to assess fit and answer questions.  This environment includes the RPC, IETF community, IETF community leadership and non-IETF RFC community (as such as it exists and we have knowledge of it).

3.  The committee needs good knowledge of the contracting options available to ensure that these are all properly considered.


#  Composition

I have approached all of the following and they have agreed to provide their time and expertise to this process.  They all have detailed knowledge of the new role.

- Jay Daley, IETF Executive Director (me), recruitment and contracting expertise
- Sandy Ginoza, RPC Director, detailed knowledge of the working environment
- John Levine, Temporary RFC Series PM, detailed knowledge of the working environment
- Peter Saint-Andre, RSOC chair and editor of new model, detailed knowledge of new model and the working environment
- Mike St Johns, community member, detailed knowledge of new model, contracting expertise


# Process

a.  Get community feedback on all of this and adjust as needed
b.  In lieu of the RSAB get feedback from the RSOC, IAB and IESG once community feedback incorporated
c.  Committee meets to identify community members for the recruiters to meet with as part of their research and to provide advice to recruiters on where to look
d.  Recruiter meets community members and then does its stuff
e.  Recruitment process
f.   Committee presents LLC board with one or more recommended candidates and contracting options for final decision.


[1]  https://github.com/intarchboard/program-rfced-future/issues/151


-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org