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/iot-wg@ripe.net/
[iot-wg] extension of co-chair selection process
- Previous message (by thread): [iot-wg] extension of co-chair selection process
- Next message (by thread): [iot-wg] extension of co-chair selection process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Thu Apr 25 16:14:11 CEST 2019
> On 25 Apr 2019, at 08:20, Eric van Uden via iot-wg <iot-wg at ripe.net> wrote: > > I agree, this may also be the time to consider whether the voting process can be done differently/better. RIPE does not vote!!! We take decisions by consensus. If you think the current appointment process can be improved, let's hear your suggestions. However it's impractical and unwise to change the current process while it's under way. Any new or revised process would need to be something to adopt AFTER a co-chair is appointed with the current procedure that's in progress. Unless of course the WG decides it doesn't want to use the current procedure => we enter a world of pain where there's no appointment process or an additional co-chair for the forseeable future.
- Previous message (by thread): [iot-wg] extension of co-chair selection process
- Next message (by thread): [iot-wg] extension of co-chair selection process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]