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/ncc-services-wg@ripe.net/
[ncc-services-wg] WG Chair appointment process
- Previous message (by thread): [ncc-services-wg] NCC Services WG Chair Selection
- Next message (by thread): [ncc-services-wg] NCC Services WG Chair Selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Sep 5 15:04:11 CEST 2017
> On 5 Sep 2017, at 12:30, Denesh Bhabuta <dblists at icloud.com> wrote: > > That said, should we be looking at term limits etc in the future, to allow new blood to come forward too? All too easy for newcomers not to put themselves forward when more experienced people and those doing it for years are still up for the task. Hi Denesh. I agree that term limits are a good thing, largely for the reasons you've outlined. [It also helps to have a healthy turnover in the leadership from time to time.] However the WG did not make provision for this in its chair appointment process. I don't know (or care) why it did that: presumably there were good reasons for reaching consensus on that process. It would probably be unwise to revisit the WG chair appointment process given the potential for shed-painting and rat-holing. If it's not broken, don't "fix" it. I would like to think we can trust the WG leadership to know when they'd overstayed their welcome and to step aside in an orderly manner. I did that in the DNS WG even though that WG's process does have provision for term limits.
- Previous message (by thread): [ncc-services-wg] NCC Services WG Chair Selection
- Next message (by thread): [ncc-services-wg] NCC Services WG Chair Selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]