<div dir="ltr">Hi,<div><br></div><div>based on what suggested in the NCSG call, I am thinking we can make a list of tasks that support volunteers can cover (and set up space for those tasks). I will also keep a list of those volunteers and make a call later in next days to see who want to join and how they can help based on the tasks we are proposing or they may propose.</div><div>in meantime, I will announce the 24 hours extension as I didn't see any objection. </div><div><br></div><div>Best,</div><div><br></div><div>Rafik<br><br><div class="gmail_quote"><div dir="ltr">Le mar. 17 juil. 2018 à 13:43, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Thanks Stephanie and Martin for the quick response, looking to hear from others.</div><div><br></div><div>I wanted also to add about the coordination channels, which includes PC monitoring EPDP team, regular NCSG confcall for EPDP and getting regular updates from representatives, we can</div><div>- have a non-public mailing list only for our members interested by the topic, but we will keep up to date the whole membership via NCSG list</div><div>- setup a skype channel for including the representatives and others who want to back up so we can do coordination during the calls.</div><div>- documenting positions and arguments (for example in wiki or google doc) so we can refer to them easily.</div><div><br></div><div>it doesn't matter what tech we will choose at the end but we need to setup this quickly and ensure its continuity for the duration of EPDP. I am also mindful to not put more workload and overhead for this effort and keep things bearable for everyone. </div><div><br></div><div>I see the role of PC to support the EPDP representatives and facilitate the work, we need some division of labor to be efficient and effective. that also includes all interested people by the topic who are observers too. </div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div><div><br><br><div class="gmail_quote"><div dir="ltr">Le mar. 17 juil. 2018 à 13:06, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">Please give an extra
day.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">SP</font></font><br>
</p>
<div class="m_2714253446744206245m_4080038379453946944moz-cite-prefix">On 2018-07-16 21:48, Rafik Dammak
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I am resending this as we should talk about the selection
process and agree on it.</div>
<div>the deadline for submission is the 18th. with the current
number of applications, I want to suggest an extension of
24hours. it is also important to encourage more people to
apply. if there is no objection, I will send the extension to
the list (for now I am sending a reminder only)</div>
<div><br>
</div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Rafik</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr">Le jeu. 12 juil. 2018 à 09:02, Rafik Dammak
<<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> a
écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>I accepted most the changes for the draft call <a href="https://docs.google.com/document/d/1YoV5UeR03Q9tFuhxDsWjbfftb4O8q2WZnRg-TRCD8nc/edit?ts=5b45fde2" target="_blank">https://docs.google.com/document/d/1YoV5UeR03Q9tFuhxDsWjbfftb4O8q2WZnRg-TRCD8nc/edit?ts=5b45fde2</a>
. </div>
<div><br>
</div>
<div>We shall receive soon the letter from GNSO about
the appointment to EPDP team. I will update the draft
with the latest relevant text (statement of
participation and requirements) and other relevant
annexes from that call.</div>
<div><br>
</div>
<div>Due to the time constraint, I will send the call
this Thursday. there may some text that can be tweaked
but I think we shouldn't spend more time doing that.
We cannot change the deadline as the date for sending
names around the 20th. We should encourage candidates
to apply but please be careful and indicate that
doesn't mean automatic selection.</div>
<div><br>
</div>
<div>Selection:</div>
<div>There is a matrix for review and ranking in the
document, please check it and let's discuss how we
will manage the selection:</div>
<div>- Review: we will do individually the ranking based
on the compiled applications (Maryam and I will work
on the format for the matrix to get everyone input and
including applicants info)</div>
<div>- Deliberations: last time for an appointment to
SSC, the deliberations didn't happen in the PC list
but with conference calls and private email thread. I
don't have any strong preference (public or private)
but in term of transparency, we can make the list of
applicants public, taking notes of the process. Please
share your thought on the matter. I think we will have
at least one conference call, to be recorded and
transcribed and so available when needed. </div>
<div>- Decision-making: we work with rough consensus and
we need to have a strong support for each
representative to be appointed. The ranking will help
us partly in splitting between members and alternates
(it also depends on people choice).</div>
<div><br>
</div>
<div>this temporary process will be documented and
updated. All <span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">those
elements will be helpful as input for general PC
procedures related to the appointment (Farzaneh and
me working on updating the draft to be shared soon).</span></div>
<div><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">later
on, we can work on preparing for EPDP itself, more
on substance, and how we will liaise with the
members. Several suggestions are made and indicated
in the call for volunteers itself. NCSG PC has a
role in term of support and input including regular
EPDP related calls, giving guidance to
representatives and getting regular updates. </span></div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Rafik</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="m_2714253446744206245m_4080038379453946944mimeAttachmentHeader"></fieldset>
<pre class="m_2714253446744206245m_4080038379453946944moz-quote-pre">_______________________________________________
NCSG-PC mailing list
<a class="m_2714253446744206245m_4080038379453946944moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>
<a class="m_2714253446744206245m_4080038379453946944moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div></div></div>
</blockquote></div></div></div>