[ncc-services-wg] NCC Services WG Chairs

	Jim,

> On 5 Apr 2019, at 12:28, Jim Reid <jim at rfc1035.com> wrote:
> 
> 
> Kurtis, thanks for doing the right thing by avoiding any perception of a conflict of interest.
> 
> The suggested course of action wrt co-chair appointments is poor. Sorry. First, while the workload may be low, the plan means Bijal becomes a SPoF for a while. What if she has other commitments in the run up to RIPE79 or can’t get a Brexit visa for the Netherlands? [Yes, I am painfully aware the IoT WG has the self-same problem. Though that will be fixed this month.] A bigger concern is appointing two co-chairs at the same time means that WG loses the benefit of staggered terms. And would presumably be stuck with that situation forever. That needs to be addressed. Could you and Bijal suggest some way to get round that problem?

Thank you for this. Me and Bijal have been discussing this and given the WG Chair Selection process (https://www.ripe.net/participate/ripe/wg/services/ripe-ncc-services-wg-chair-selection-process) we are a bit limited. While it is true the selection process is meant to be light it does represent the consensus of the WG. One thing we did discuss was a “temporary” WG chair that would be selected at the next meeting and have a term until the autumn meeting unless I was a successful candidate. However, that is not how the process is written. Taking your points, and following the process me and Bijal agreed that calling for a third WG chair is the best way forward, to be selected before the Reykjavik RIPE meeting.

This means that I will be sending out the call for volunteers shortly and the two week period for showing interest, and following the two week discussion period. If I am elected to the RIPE NCC board, the new chair and Bijal will continue and there will be a new selection in the fall for Bijal’s position. If I am not elected to the RIPE NCC board, we continue with three chairs at least until the autumn when we hold a new selection unless anything changes in the mean time.

Best regards,

Kurtis & Bijal / NCC Services WG Chairs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP
URL: </ripe/mail/archives/ncc-services-wg/attachments/20190409/881812fc/attachment.sig>