> On 14 Mar 2023, at 17:59, Nigel Titley via ripe-list
> wrote:
>
> Having said that, it may well be that continuing to accept that the RIPE NCC
> continues to employ the RIPE Chair(s) is the only workable solution.
>
Would it be any better if the RIPE Chair was remunerated out of funding
Hi
Text looks good to me. Concise, descriptive and sets expectations from the
begininng.
Thanks
Joao
> On 9 May 2022, at 15:50, Niall O'Reilly wrote:
>
> On 12 Apr 2022, at 15:28, Niall O'Reilly wrote:
>
>> I also see that the text can be made clearer, and will revise it accordingly
>> befo
Hi Mirjam, all,
A code of conduct is a welcome addition to RIPE’s toolset. It is a pity we need
one but such is humanity.
The problem with any code/rulebook is, as has been shown, how it gets applied.
Hans Peter’s was a most unfortunate action: not only was it completely out of
line, showing po
rly pragmatical person, so I would like to
invoke the “pragmatism” section of RIPE 727 and request that this message be my
input to "Any such deviations and the appropriate community involvement should
be clearly documented each time."
Regards,
Joao Luis Silva Damas
Just a RIPE community participant
Dear all,
I also support the current proposed documents and am happy that they are
modelled on existing working processes from communities with which RIPE has a
good affinity.
> On 29 Jul 2019, at 15:19, Daniel Karrenberg wrote:
>
>
>
> On 25 Jul 2019, at 15:41, Peter Koch wrote:
>
>> The
