This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] NCC Services WG Chairs
- Previous message (by thread): [ncc-services-wg] NCC Services WG Chairs
- Next message (by thread): [ncc-services-wg] NCC Services WG Chairs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Fri Apr 5 13:28:24 CEST 2019
> On 5 Apr 2019, at 08:16, Kurtis Lindqvist <kurtis at kurtis.pp.se> wrote: > > We both feel that the workload is low enough that she could continue as WG chair until the following RIPE meeting in the fall, when a new co-chair would be selected to replace me. It is worth noting that Bijal is also up for reselection at the same meeting, but she is wiling to continue for another term. 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? Obligatory rant against vile Americanisms: the season after summer is called autumn, not the fall. :-)
- Previous message (by thread): [ncc-services-wg] NCC Services WG Chairs
- Next message (by thread): [ncc-services-wg] NCC Services WG Chairs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]