[cooperation-wg] WG Chair Selection Process - candidates and launch of the discussion
- Previous message (by thread): [cooperation-wg] WG Chair Selection Process - candidates and launch of the discussion
- Next message (by thread): [cooperation-wg] WG Chair Selection Process - candidates and launch of the discussion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Jan 5 16:10:00 CET 2021
> On 5 Jan 2021, at 14:34, Michele Neylon - Blacknight via cooperation-wg <cooperation-wg at ripe.net> wrote: > > Is there a limit on the number of co-chairs a group can have? Not really. There are no rules about this and that is how it should be. Each WG gets to choose how to organise itself and agree a charter. For coop, this says "The RIPE Coop WG aims for multiple Chairs, with two or three Chairs”. The general convention is a WG has 2 or 3 co-chairs. IMO 4 is excessive unless there’s a *very, very* busy WG. Three’s probably too many too*. In the good old days, there was just one WG Chair per WG with a backup/stand-in to cover for absences. Back then Rob Blokzijl wanted to have exactly one point of contact in each WG to keep things clear and simple. * As a data point, it takes far more to run an IETF WG than a RIPE WG: more meetings and conf calls, busier mailing lists, tracking/advancing wannabe RFCs, more process to follow, heavier workload, etc, etc. Offhand, I can’t think of any IETF WG - tls, quic, dnsop, httpbis and so on - which has >3 co-chairs.
- Previous message (by thread): [cooperation-wg] WG Chair Selection Process - candidates and launch of the discussion
- Next message (by thread): [cooperation-wg] WG Chair Selection Process - candidates and launch of the discussion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]