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

["Martin J. Dürst" <[e-mail]>]

Hello Jay,

Here just my two cents:

In general, this looks like a good proposal. I think the selection of 
the people is good, I at least trust all of them. (I'd put yourself last 
rather than first, but that's a minor detail.)

I'd keep any mention of the RSOC out of the text. I didn't even know 
that Peter is RSOC chair. We are working on replacing the RSOC, so we 
shouldn't need it anymore. The RSAB isn't constituted yet, but it's easy 
to get feedback from the IRTF chair and from the Independent Submission 
Editor (or whatever his title was, sorry) in addition to the IAB and 
IESG, which (with the exception of the RSCE, which we are hiring) covers 
all of the RSAG.

Regards,   Martin.

On 2022-02-01 10:50, Jay Daley wrote:
> 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
> 
> 

-- 
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology
College of Science and Engineering
Aoyama Gakuin University
Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan