<div>I imagine so, I think it is just awkward timing for the first week.<br></div><div><br></div><div>I will definitely raise the need for rotation on our call, if it is not mentioned by the Chair.<br></div><div><br></div><div>Best wishes, Ayden <br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On 24 July 2018 5:57 PM, farzaneh badii <farzaneh.badii@gmail.com> wrote:<br></div><div> <br></div><blockquote type="cite" class="protonmail_quote"><div><div dir="auto">We used to have rotating times in other groups to distribute the pain. Is it the same for this group? <br></div></div><div><div><br></div><div class="gmail_quote"><div dir="ltr">On Tue, Jul 24, 2018 at 12:54 PM Ayden Férdeline <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>All of the proposed times for the first EPDP call next week are very convenient for Europe and North America, and dreadful for Japan. The call would be beginning, at the earliest, at 1:00am in Tokyo, which is not ideal for Rafik. So let's make sure our NCSG calls, at least, are at a sensible hour for everyone! I'm even prepared to set my alarm for 6am for you, Rafik...<br></div><div><br></div><div>Best wishes, Ayden <br></div><div><br></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On 24 July 2018 7:53 AM, Farell FOLLY <<a href="mailto:farell@benin2point0.org" target="_blank">farell@benin2point0.org</a>> wrote:<br></div><div><br></div><blockquote type="cite" class="m_417466683767513739protonmail_quote"><div>Dear Rafik,<br></div><div><br></div><div>You are very strong, do you ever get a rest? I am sure you missed your vocational job as a soldier.. LOL..<br></div><div><br></div><div><br></div><div><div>Thanks for bringing this, indeed we need to go forward. I agree with Steph on the bi-weekly plan so that we do not get (a) burden too soon but also have materials to discuss after two weeks. I am ok with Ayden suggestions, too. Good EPDP team.<br></div><div><br></div><div><div dir="auto" style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><br></div><div>@__f_f__<br></div></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div>Best Regards<br></div><div>____________________________________<br></div><div><br></div><div>Ekue (Farell) FOLLY<br></div><div>Technology Champion & Chapter Head<br></div></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Africa 2.0 Foundation.<br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="http://www.africa2point0.org" target="_blank">www.africa2point0.org</a><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="http://linkedin.com/in/farellf" target="_blank">linkedin.com/in/farellf</a><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><div><br></div></div></div><div><br></div></div><div><br></div></div><div><br></div></div><div><div><br></div><blockquote type="cite"><div>On 24 Jul 2018, at 05:02, Stephanie Perrin <<a href="mailto:stephanie.perrin@MAIL.UTORONTO.CA" target="_blank">stephanie.perrin@MAIL.UTORONTO.CA</a>> wrote:<br></div><div><br></div><div><div bgcolor="#FFFFFF"><p><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font">Yes thanks for getting
this started Rafik! I agree that a biweekly call would be
helpful, more than that is too much I think. We do need a
back channel to use during meetings, either skype or slack is
fine with me, I leave it to you techies. </span></span><br></p><p><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font">I agree with Ayden
that it is necessary to check the transcript, it is tedious
but perhaps a team could take that on in turns. </span></span><br></p><p><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font">We need someone to
organize an archive of relevant resource materials. On the
wiki makes sense, need a finding aid prepared as well. We
also need resources sorted so that we can find them....not my
forte but we may have volunteers who could take this on. Even
just to gather all the supporting documents in one place
(e.g. letters from DPAs, legislation, etc). </span></span><br></p><div class="m_417466683767513739moz-cite-prefix"><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font">I am working on the annotated interim unified access
model... will send when it is done. Also perhaps pull out
some of the key things wrong with the EWG report, since it is
being cited as a guide to tiered access....</span></span><br></div><div class="m_417466683767513739moz-cite-prefix"><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font"></span></span><br></div><div class="m_417466683767513739moz-cite-prefix"><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font">Stephanie</span></span><br></div><div class="m_417466683767513739moz-cite-prefix"><span style="font-size:undefinedpx" class="m_417466683767513739size"><span style="font-family:"Lucida Grande"" class="font"></span></span>On 2018-07-23 22:53, Ayden Férdeline
wrote:<br></div><blockquote type="cite"><div>(cc’ing in those who are not subscribed to this list)<br></div><div><br></div><div>Hi Rafik,<br></div><div><br></div><div>Thanks for initiating this discussion. <br></div><div><br></div><div>I agree with starting a new, closed discussion list for EPDP
strategising. We will need to watch the enrolment to ensure that
only NCSG members subscribe; I remember when we had the
closed GDPR list, an unexpected email address subscribed...<br></div><div><br></div><div>A biweekly NCSG EPDP call seems sensible to me, as does the
informal Skype chat. Or we could use the NCSG Slack, which is
growing in use. Last week it had over 500 messages exchanged. <br></div><div><br></div><div>As for tasks, it would be helpful to have volunteers to
listen to the meeting recordings and to compare our
interventions with the transcript. I have just done this for our
July 19 Council meeting — and emailed through a number of
corrections to ensure it is a verbatim record. <br></div><div><br></div><div>Best wishes,<br></div><div><br></div><div>Ayden<br></div><div><br></div><div id="m_417466683767513739protonmail_mobile_signature_block">Sent from ProtonMail
Mobile<br></div><div><div><br></div><div><div><br></div><div>On Tue, Jul 24, 2018 at 01:10, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> wrote:<br></div></div><blockquote class="m_417466683767513739protonmail_quote" type="cite"><div dir="ltr"><div>Hi all, <br></div><div><br></div><div>as we are done now with the selection, we can resume
our discussion on how to coordinate NCSG interventions and
support EPDP members actions.<br></div><div><br></div><div>several NCSG members expressed interest to help and
volunteer for tasks (to be listed). so please share your
ideas for any relevant task.<br></div><div><br></div><div>one quick action is to create a separate mailing list
including EPDP reps and any interested volunteer. the
mailing list may be non-public as we can strategize
there. @Maryam can you please create a new list?<br></div><div><br></div><div>for the EPDP conf calls, it would make sense to have a
skype chat for example for real-time discussion and
coordination. I can set up that quickly.<br></div><div><div><br></div><div>documentation: that point was made several times that we
need to document positions, interventions etc for
referring to them later. I think that can be supported by
volunteers and with guidance from EPDP members. same for
working documents versioning.<br></div></div><div><br></div><div>we can also schedule EPDP NCSG call. maybe weekly will
be too much in term of scheduling and adding more burden.
biweekly would make more sense.<br></div><div><br></div><div>please share your thoughts and suggestions if I missed
anything.<br></div><div><br></div><div>in meantime, Maryam can create a wiki space where to
put info, having a documents repository and so on. <br></div><div><br></div><div>Best,<br></div><div><br></div><div>Rafik<br></div><div><div><br></div><div class="gmail_quote"><div dir="ltr"><div>---------- Forwarded message --------- <br></div><div>From: <b>Rafik
Dammak</b> <span dir="ltr"><<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>></span> <br></div><div>Date: mar. 17 juil. 2018 à 13:43 <br></div><div>Subject: Re: [NCSG-PC] call for volunteers for EPDP
team / Selection process <br></div><div>To: Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>> <br></div><div>Cc: ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank">ncsg-pc@lists.ncsg.is</a>> <br></div></div><div><br></div><div><br></div><div dir="ltr"><div>Hi, <br></div><div><br></div><div>Thanks Stephanie and Martin for the quick
response, looking to hear from others.<br></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<br></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<br></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.<br></div><div>- documenting positions and arguments (for
example in wiki or google doc) so we can refer to
them easily.<br></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. <br></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. <br></div><div><br></div><div>Best,<br></div><div><br></div><div>Rafik<br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204)"><br></blockquote></div></div></div></div></div></div></blockquote></div><div><br></div><pre class="m_417466683767513739moz-quote-pre">_______________________________________________
NCSG-PC mailing list
<a class="m_417466683767513739moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>
<a class="m_417466683767513739moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
<br></pre></blockquote></div><div>_______________________________________________<br></div><div>NCSG-PC mailing list<br></div><div><a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br></div><div><a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br></div></div></blockquote></div></div></blockquote><div><br></div><div>_______________________________________________<br></div><div> NCSG-PC mailing list<br></div><div> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br></div><div> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br></div></blockquote></div></div><div>-- <br></div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-family:verdana, sans-serif" class="font">Farzaneh</span><br></div></div></div></blockquote><div><br></div>