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]/
[iot-discussion] chair selection processes
- Previous message (by thread): [iot-discussion] RIPE 75 draft agenda now confirmed and available
- Next message (by thread): [iot-discussion] chair selection processes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Oct 3 17:00:31 CEST 2017
> On 3 Oct 2017, at 15:32, Anna Wilson <anna.wilson at heanet.ie> wrote: > > Fully agree that we should adopt an existing one (that's what we did for ipv6-wg.) I struggle with the "draw lots" clause though; I think when there are multiple remaining candidates, the WG ought to express a preference. Well that’s what’s supposed to happen Anna. The WG reaches consensus on their preferred candidate. But suppose it doesn’t or can't. Then what? IMO a “draw lots” thing is the simplest and most convenient way to resolve matters when a selection by consensus is unclear or isn’t possible: for instance, when support for two or more candidates is pretty much equal. A random selection mechanism like drawing lots provides a very pragmatic way to break those sort of deadlocks. Other ways to resolve a tie are of course possible. However they are likely to end up in a monument to process. And probably less robust/effective too. Besides, if the names of the tied candidates all go into a hat, those who wish to shed-paint can get to debate who holds the hat, how big it is, what it’s made from, etc, etc. :-)
- Previous message (by thread): [iot-discussion] RIPE 75 draft agenda now confirmed and available
- Next message (by thread): [iot-discussion] chair selection processes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]