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/address-policy-wg@ripe.net/
[address-policy-wg] WG chair re-selection procedure
- Previous message (by thread): [address-policy-wg] WG chair re-selection procedure
- Next message (by thread): [address-policy-wg] WG chair re-selection procedure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Mon Sep 15 21:01:43 CEST 2014
On 15 Sep 2014, at 19:37, Scott Leibrand <scottleibrand at gmail.com> wrote: > Who determines whether consensus on a new chair has been reached? If a vocal minority objects to replacing the current chair and blocks consensus on a new one, does that mean he could continue chairing the WG indefinitely? I think we should apply common sense rather than try to enumerate solutions for every possible corner case. If the WG can't reach consensus -- for some loose definition of that -- kick the problem upstairs for a judgement. IMO that could best be done by the RIPE chair. Who could intervene if there's an appeal or dispute on the consensus decision. I suppose the WG Chairs Collective could also be used for that role, though they may be considered too close to the Chairs of the AP WG to take on that task. I would like to think that if a chair cannot get the support from the WG, he/she would know this would be the point to stand down and make way for a replacement.
- Previous message (by thread): [address-policy-wg] WG chair re-selection procedure
- Next message (by thread): [address-policy-wg] WG chair re-selection procedure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]