<div dir="ltr">Hi Farzaneh,<div><br></div><div>looks ok. I am just for keeping it simple :)</div><div>unless we may have several members missing many calls in a row, everything should be ok and we get enough coverage with 3 alternates.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik<br><br><div class="gmail_quote"><div dir="ltr">Le mer. 25 juil. 2018 à 02:07, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@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><div dir="auto">Hi </div></div><div dir="auto"><br></div><div dir="auto">So our agreements can be as follows: </div><div dir="auto"><br></div><div dir="auto">1. Members have to assign an alternate for any meeting they cannot attend. </div><div dir="auto"><br></div><div dir="auto">2. They need to announce on ncsg epdp list. And announce the alternate. </div><div dir="auto"><br></div><div dir="auto">3. Preferably if two members cannot attend the same meeting need to assign two different alternates. If two members have chosen the same alternate they should agree among themselves to assign an additional alternate. </div><div dir="auto"><br></div><div dir="auto">4. Preferably no one alternate should represent two members at the same meeting. </div><div dir="auto"><br></div><div dir="auto">5. If the alternates cannot attend either, the world will come to an end and we don't even have to discuss epdp </div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jul 24, 2018 at 9:24 AM Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>> wrote:<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">I agree that we need
100% coverage whenever possible. I think that how we arrange
alternates will depend on frequency of calls, time rotation of
calls (so far based on the doodle poll, not seeming much
flexibility in the timing) and how people prefer to work. I
doubt that all the calls will happen to be in the middle of
the night for me because the two most popular time zones are
likely to be (based on overall composition) California and
Washington. I think perhaps we can do like we do for Council,
let people select their alternative? I expect a lot of these
calls are going to be (as usual) in the middle of the night
for David, we should perhaps be preparing a wee map of our
timezones....</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers Steph</font></font><br>
</p></div><div text="#000000" bgcolor="#FFFFFF">
<div class="m_-4999914606541451423m_4799778247187249613moz-cite-prefix">On 2018-07-23 23:07, Ayden Férdeline
wrote:<br>
</div>
<blockquote type="cite">
<div>Hi all,</div>
<div>
<br>
</div>
<div>Just thought I’d start this conversation off now re: how and
when we appoint alternates. </div>
<div>
<br>
</div>
<div>1) I think it would be beneficial for the NCSG to have 100%
coverage on all calls; wherever possible we should not have
calls where there are not 6 NCSG members present. Is this
reasonable?</div>
<div>
<br>
</div>
<div>2) How will we appoint alternates? Is this something that
should be arranged by the NCSG Chair, or is it an individual
responsibility to find an alternate to cover us where we are
unavailable?</div>
<div>
<br>
</div>
<div>3) Do we want rotation to be in place to ensure that all
alternates are, to the greatest extent possible, invited to be
an alternate for an equal number of calls? Or should other
factors be considered, i.e. timezone of call/alternate, subject
matter?</div>
<div>
<br>
</div>
<div>Best wishes,</div>
<div>
<br>
</div>
<div>Ayden</div>
<div>
<br>
</div>
<div id="m_-4999914606541451423m_4799778247187249613protonmail_mobile_signature_block">Sent from ProtonMail
Mobile</div>
<br>
<fieldset class="m_-4999914606541451423m_4799778247187249613mimeAttachmentHeader"></fieldset>
<pre class="m_-4999914606541451423m_4799778247187249613moz-quote-pre">_______________________________________________
NCSG-PC mailing list
<a class="m_-4999914606541451423m_4799778247187249613moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>
<a class="m_-4999914606541451423m_4799778247187249613moz-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>-- <br><div dir="ltr" class="m_-4999914606541451423gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></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>