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/ripe-chair-discuss@ripe.net/
[ripe-chair-discuss] Status of RIPE Chair discussion?
- Previous message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
- Next message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Thu May 18 12:37:06 CEST 2017
> On 18 May 2017, at 11:34, Daniel Karrenberg <daniel.karrenberg at ripe.net> wrote: > > So we have: > > 1. RIPE Chair job description: Doing the sort of things that the RIPE > Chair should do and actively maintaining an open dialogue with the > community. > > 2. RIPE Chair selection process: Selected as needed. > > 3. RIPE Chair continuity: The RIPE Chair may appoint and dismiss a vice > chair. Works for me. Though to address Nick's point, perhaps change 2 to: 2. RIPE Chair selection and removal process: Selected as needed
- Previous message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
- Next message (by thread): [ripe-chair-discuss] Status of RIPE Chair discussion?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]