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 ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Thu May 18 12:51:54 CEST 2017
Can we all calm down a bit please? We all know each other and I do assume the best intentions on everyone's part. I am also quite sure that we are not out to hurt each other or to have an overly polemic debate. The good thing is that there is a lot of passion here for the future of RIPE. Let's be positive! Daniel On 18.05.17 10:55 , Nurani Nimpuno wrote: > >> On 18 May 2017, at 10:51, Nigel Titley <nigel at titley.com> wrote: >> >> On 18/05/17 07:15, Nurani Nimpuno wrote: >> ... >> I think you've been in close proximity to ICANN folk for far too long. > > Ok, that’s a low shot. > With that, I think I will withdraw from this discussion. > > Nurani > >> YOU may not find it helpful but it is in fact a job description and a >> process. Other people have found it helpful. >> >>> >>> And while I also don’t want something over prescriptive, I do think that unless we do away with the concept of a RIPE chair, we need to define it in a way that people can understand it. >> >> There are many positions that don't have a written job description but >> are nevertheless well regarded, understood and accepted. >> >> Nigel
- 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 ]