[ripe-list] The NomCom Requests your Support

Hi,

<with my RIPE NomCom member hat on>

On 26/05/2020 07:59, Andy Davidson wrote:
> Without
> responding to any of the concerns - or 'addressing' them to use your
> choice of word, or even reference to them, Daniel then opens a new
> thread on an entirely different mailing list 

I believe that Daniel is just doing his chairman duty and is following 
the process to the letter. RIPE-728 says:

“ All announcements must be made using at least the mechanism used by 
the RIPE NCC for its announcements, including a notice on the RIPE NCC 
website.
As of the publication of this document, the current mechanism is an 
email message to the'ripe at ripe.net' mailing list.”

He sent a message to the appropriate mailing list.

> asking for wide
> community support to proceed unchanged.

This was a consensus reached inside NomCom on what to do next. He did 
not do anything at all on his own.

> 
> This is not consensus building.  This is not suitable methodology
> from the Chair.  This is disingenuous.

I wholeheartedly disagree. He's just doing his job and he's doing it well.

<RIPE community member hat on>

What Nick (and some responses to his initial email) asked is to draw a 
line between the RIPE community and the RIPE NCC. That's fine and lovely.

I think that the RIPE NomCom has absolutely *NO* authority or mandate to 
discuss or draw the line between the RIPE community and the RIPE NCC. 
This might be an interesting subject to discuss over beer, but RIPE 
NomCom is not the place where this discussion could take place and 
therefore this debate *MUST NOT* influence the RIPE NomCom work at 
slightest.

If community wants to define and implement a clear distinction and draw 
a line between RIPE Community and RIPE NCC - we are welcome to do it 
even now, but that does not affect the work of 2020 NomCom. However, 
what community can do is to read our report when we are done and change 
the process for RIPE NomCom that will be formed in 3 years time.

Don't fix the aircraft during the flight. Don't stop the engines and 
jump out of it. Let's land with as less damage as possible and fix the 
process for the next flight.

Cheers, Jan Žorž