Hi Ted, On 14/07/2019 20:08, Ted Hardie wrote: > A key question now is whether we conduct the hiring > according to a slightly modified SOW and have the new incumbent participate > in the larger discussion or conduct the discussion prior to recruiting a > new RSE. The first strategy seems to be permitted by RFC 6635 under the > general rubric of the RSE's role in evolving the series. The second is > also possible, but the result will likely be that there is no overlap > between a new incumbent and Heather. I agree the above is a key question on which we need community input in the very near term. I have a question about the options though, we have previously had Olaf take on the role of acting RSE (much to his delight wrt the acronym:-). That happened in different circumstances, with which I'm not familiar (and I suspect I'd mostly prefer to maintain my innocence as to those;-). So I (and I suspect other IETF participants) am unclear if we do or do not have a real option to try find a member of the community to take on the role of acting RSE whilst we do the work on a revision to the RSE model (aka a substantive revision of 6635). If that were an option, then I guess we'd have 3 high level options from which to choose - a) appoint a new RSE now (which I guess likely has to be the default if there's no clear community view about other actions), b) make no appointment whilst the community discuss a revision to the RSE model, or perhaps, c) try find an acting RSE whilst the community discuss revision of the RSE model. I'm not arguing for option (c) above, but just wonder if that is or is not a real option. I guess the potential benefit would be that we'd have time for proper community discussion but also have someone to whom e.g. decisions about format change details could be directed if a case arose that the RFC production centre weren't happy to handle themselves. But, there may be downsides to that option that I'm not seeing, so I'm not sure. Cheers, S.
Attachment:
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
