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-list@ripe.net/
[ripe-list] The NomCom Requests your Support
- Previous message (by thread): [ripe-list] The NomCom Requests your Support
- Next message (by thread): [ripe-list] The NomCom Requests your Support
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Thu May 28 10:26:55 CEST 2020
Hi,
On Thu, May 28, 2020 at 07:25:03AM +0000, Andy Davidson wrote:
> In the past, the RIPE Community Chair and the chair of a RIPE
> Committee/Task Force/Working Group could have had a conversation
> about a problem regarding RIPE community oversight to an NCC person
> or function or service. Right now, they can't because the RIPE
> Chair and the Chair of this Committee *work for the NCC*, and one
> reports to the other. Do you not see how this is a governance
> problem, however accidentally derived? Yes or no?
No.
Well. You are mixing (at least) three things here, and it would be good
if you speak more precisely about what you are talking about. Because
the differences are very significant.
There is the RIPE Interim Chair which happens to be RIPE NCC MD - which
is something we all want to *end*. It will end sooner if we can present
a successor as planned.
Then, there is the RIPE NomCom Chair - who happens to be an NCC employee,
yes. But the rules of this game are very clear: follow the process
described, lead the NomCom in a neutral and transparent way, do not
influence the candidate selection. The NomCom members are not newcomers
to this game of politics and influence-taking, so we can judge well what
Daniel is doing (exactly what he was asked to do, in a very painstakingly
neutral and correct way).
And then there's RIPE working group chairs, RIPE task force chairs,
who have nothing to do whatsoever with the question at hand (NomCom
and WG chair) - but yes, the question can of course be asked "do we
have a problem here". But this is a different topic, and should not
be randomly lumped all together. By - good - tradition, the chairs
of the address policy and NCC services working group are not NCC
employees, because that could indeed cause conflicts of interest,
while it's very hard to construct such a conflict for, say, the IoT WG
- but strictly speaking, this is a matter for the respective WG or TF
to decide who they want and trust as their chairperson.
Gert Doering
-- NomCom member, APWG chair, NCC member, Community member
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-list/attachments/20200528/404f6b0b/attachment.sig>
- Previous message (by thread): [ripe-list] The NomCom Requests your Support
- Next message (by thread): [ripe-list] The NomCom Requests your Support
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]