IETF Logo Mail Archive

[Rfced-future] Hires/contracts/selects/nominates/appoints

Adrian Farrel <adrian@olddog.co.uk> Wed, 24 June 2020 22:37 UTC

Return-Path: <adrian@olddog.co.uk>
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 3BF803A11BC for <rfced-future@ietfa.amsl.com>; Wed, 24 Jun 2020 15:37:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 qILwwQQt8BXS for <rfced-future@ietfa.amsl.com>; Wed, 24 Jun 2020 15:37:01 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 912B73A11BB for <rfced-future@iab.org>; Wed, 24 Jun 2020 15:37:00 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 05OMavmd007017; Wed, 24 Jun 2020 23:36:57 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DC7522203B; Wed, 24 Jun 2020 23:36:56 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id C79832203A; Wed, 24 Jun 2020 23:36:56 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.26.18]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 05OMatVI003080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 Jun 2020 23:36:56 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Brian Rosen' <br@brianrosen.net>
Cc: rfced-future@iab.org
Date: Wed, 24 Jun 2020 23:36:54 +0100
Organization: Old Dog Consulting
Message-ID: <05ed01d64a77$f6cf6940$e46e3bc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdZKd9cOWT9MtpyESOiPe9njIv9XdQ==
Content-Language: en-gb
X-Originating-IP: 84.93.26.18
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25502.003
X-TM-AS-Result: No--6.271-10.0-31-10
X-imss-scan-details: No--6.271-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25502.003
X-TMASE-Result: 10--6.270900-10.000000
X-TMASE-MatchedRID: RSMWFfuXjag+D3J+ThgLRp00SCdpx1uvi+TAnPnbttjLkl8e9W70i+mW pqKXmZL5r8LPT7YEIHZyDJ5eR7262mJQK9wIJ221zniFfjFXqM7dOKPIz0+bToB4XybRlTmEE+E VwCB2XWkN3YZLVs0RTb+LR20OeUVYyQWMBUbcSBkK4MBRf7I7pgKflB9+9kWV9fB+4MvepQyjxY yRBa/qJeHvPwwcLlxnDV8DVAd6AO/dB/CxWTRRu25FeHtsUoHuLOIKCuE/YBKgLDB5/akv99VI9 0AjPMVRVH+a9dtwvkxLDBwYotNgRw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/iYYsT1kboIgbw_h_Xeg5WE56wWU>
Subject: [Rfced-future] Hires/contracts/selects/nominates/appoints
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: Wed, 24 Jun 2020 22:37:03 -0000

Hi Brian,

> 2. Who hires/contracts the RSE?
> Also seems like we can likely wrap this up quickly on-list.  I sense the current
> direction is the LLC.  Brian offered some options.  If you think it should be
> some entity other than the LLC, please speak up.

I tried before but maybe got lost in the noise.

I think the question as phrased has ambiguities.

Hires != Contracts

I have no issue with the LLC holding the contract and even doing any necessary contract negotiation.

But:
- who writes the job spec and sets out the fundamentals of the contract?
- who reviews the applications?
- who short-lists?
- who interviews?
- who comes up with a preferred candidate?
- who ratifies that candidate?

All of that MIGHT [RFC6919] be covered by the term "Hires" in which case (and meaning no offence to the LLC) I don't think the LLC has the necessary experience to perform the task.

Cheers,
Adrian

v2.23.0 | Report a Bug | By Email