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]/
[ripe-chair-discuss] WG Chair selection
- Previous message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
- Next message (by thread): [ripe-chair-discuss] WG Chair selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Oct 9 15:14:45 CEST 2018
> On 9 Oct 2018, at 11:00, Filiz Yilmaz <koalafil at gmail.com> wrote: > > To explain my concerns further; RIPE WG Chair Selection process is not a uniform one and every group is left to decide on their selection process. This was largely because WGs or their Chairs at the time could not agree on an uniform process across RIPE. Filiz, that’s a discussion for another thread on another mailing list. IMO the fact there’s no over-arching WG Chair selection process is a strength, not a weakness. It’s also a feature of bottom-up decision making. Each WG gets to decide for itself how the WG is best run. Embrace diversity. :-) Oh, and since those WG Chair mechanisms have come into effect, there has been a healthy but prudent turnover in WG leadership. A complete regime change has taken place in DNS and IPv6. Other WGs are not far behind. Most selection procedures incorporate term limits too. Future discussion on this topic should be moved to another list.
- Previous message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
- Next message (by thread): [ripe-chair-discuss] WG Chair selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]