<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello Elvis,<div><br></div><div>Thank you for your interest in the document and the call we have made. </div><div><br></div><div>Short answer to your concerns is that the current document is a "DRAFT" document, as both my mail and the tittle on the relevant webpage points, as well as having a time set in the future (5 February 2014) for comments.</div><div><br></div><div><br></div><div>You can find a longer answer with further clarification below: </div><div><br></div><div>Regarding the Vice Chairs: </div><div><br></div><div>As you may know, following a Task Force's proposal, the RIPE Programme Committee was supported and was setup at RIPE 62, in May 2011. </div><div>I joined the RIPE PC in the following meeting and was selected as the Vice Chair to the Chair (who was Todd Underwood by then). </div><div>So RIPE PC had Vice Chairs to assist the Chair operationally almost since the beginning of its formalisation. </div><div>But this was not mentioned in the document previously (ripe-531). </div><div>As we were updating the document this time around, RIPE PC decided to include this too, to document the status-quo more clearly.</div><div><br></div><div>Regarding your other point, the intention of the PC with this is very clear: </div><div><br></div><div>We updated our Charter, outlining our responsibilities and functions the best way we can think of. </div><div>RIPE Community advocates for transparency and the RIPE PC follows this principle. </div><div>In this spirit, we shared the draft document with the RIPE Community on the ripe-list and set a future date for comments. </div><div>If you have suggestions on how to do this any better, please let us know that too. </div><div><br></div><div>I hear you that the document having a number already assigned to may be seen as somewhat puzzling. </div><div>As we are informed, this is how the RIPE NCC's document management process works. </div><div>It is an operational matter and out of the scope of the RIPE PC as we do not actually update any pages or assign numbers to documents. </div><div>RIPE NCC told us though that if the final document's content would be different to the current draft, it would receive a new number indeed. </div><div><br></div><div>Kind regards</div><div>Filz</div><div><br></div><div><br></div><div><br></div><div><div><div>On 15 Jan 2014, at 18:12, Elvis Velea <<a href="mailto:elvis@velea.eu">elvis@velea.eu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
Hi Filiz,<br>
<br>
<div class="moz-cite-prefix">On 15/01/14 17:28, Filiz Yilmaz wrote:<br>
</div>
<blockquote cite="mid:F26B807C-B9AA-4C6D-8B91-B2080BE1280B@gmail.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div><br>
</div>
Dear colleagues,<br>
<br>
As the RIPE Programme Committee, we have done some house-keeping
recently and updated our charter. <br>
<br>
The most prominent parts of the update are for the reflection of a
previous change in the size of the membership of the Committee
(from 8 to 12 seats) and for the documentation of the possibility
of removal of a PC member based on unanimous vote, following
Committee's decision at RIPE 67. <br>
<br>
</blockquote>
Just to document the changes, I see there's a third difference,
which you do not mention, between the two documents. <br>
"The PC members also select up to two Vice Chairs who aid the Chair
as necessary."<br>
<br>
further, the responsibilities of the Vice Chairs are:<br>
"The Vice Chairs will work towards to ensuring active participation
of PC members."<br>
<br>
I also see that the PC has already selected the Vice Chairs,
basically accepting the changes to the Charter before any feedback
could be offered.<br>
<br>
Isn't active participation of all the PC members the main
responsibility of all it's members? Will the Vice Chairs have any
other responsibilities in the future RIPE Meetings?<br>
<blockquote cite="mid:F26B807C-B9AA-4C6D-8B91-B2080BE1280B@gmail.com" type="cite">Further updates were for wording improvements towards
better readability. <br>
<br>
The updated draft document is at:
<div>
<div style="margin: 0px; font-size: 12px; color: rgb(2, 30,
170); "><span style="text-decoration: underline ;
letter-spacing: 0.0px"><a moz-do-not-send="true" href="https://www.ripe.net/ripe/docs/ripe-600">https://www.ripe.net/ripe/docs/ripe-600</a></span></div>
</div>
<div><br>
</div>
<div>and is to replace:</div>
<div>
<div><a moz-do-not-send="true" href="https://www.ripe.net/ripe/docs/ripe-531">https://www.ripe.net/ripe/docs/ripe-531</a><br>
</div>
</div>
</blockquote>
ripe-531 has already been marked as obsolete.<br>
<br>
"This document is obsoleted by ripe-600"<br>
<blockquote cite="mid:F26B807C-B9AA-4C6D-8B91-B2080BE1280B@gmail.com" type="cite">
<div>
<div>We will ask the RIPE NCC to publish the updated draft
document as a final RIPE Document on 5 February 2014. <br>
Until then, please let us know if you have any comments. <br>
</div>
</div>
</blockquote>
It's already published as a RIPE document and AFAIK any further
comments would require a new RIPE document to be created. Not that I
have any comments to the changes you guys have decided, it is up to
the PC how it organizes it's activity.. I am commenting on the way
you request the comments on the changes made to the charter.<br>
<br>
You are requesting feedback on some changes that have already been
documented, approved by the PC (which has already chosen it's Vice
Chairs) and published in ripe-600 (thus rendering any comments
useless).<br>
<blockquote cite="mid:F26B807C-B9AA-4C6D-8B91-B2080BE1280B@gmail.com" type="cite">
<div>
<div>Kind regards<br>
Filiz Yilmaz, Shane Kerr & Benno Overeinder<br>
PC Chair and Vice Chairs</div>
</div>
</blockquote>
cheers,<br>
elvis<br>
</div>
</blockquote></div><br></div></body></html>