<div>I can start compiling the resources in a Google Doc; I will share it on this list later in the week. Once complete (or complete enough) we can perhaps port to the wiki. </div>
<div>
<br />
</div>
<div>Ayden</div>
<div>
<br />
</div>
<div id="protonmail_mobile_signature_block">Sent from ProtonMail Mobile</div>
<div>
<br />
<div>
<div>
<br />
</div>On Tue, Jul 24, 2018 at 05:02, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" class="">stephanie.perrin@mail.utoronto.ca</a>> wrote:</div>
<blockquote class="protonmail_quote" type="cite">
<p><font size="+1"><font face="Lucida Grande">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. <br /> </font></font>
</p>
<p><font size="+1"><font face="Lucida Grande">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. <br /> </font></font>
</p>
<p><font size="+1"><font face="Lucida Grande">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). </font></font>
<br
/>
</p>
<div class="moz-cite-prefix"><font size="+1"><font face="Lucida Grande">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....</font></font>
</div>
<div class="moz-cite-prefix"><font size="+1"><font face="Lucida Grande"><br /> </font></font>
</div>
<div class="moz-cite-prefix"><font size="+1"><font face="Lucida Grande">Stephanie<br /> </font></font>
</div>
<div class="moz-cite-prefix"><font size="+1"><font face="Lucida Grande"></font></font>On 2018-07-23 22:53, Ayden Férdeline wrote:
<br />
</div>
<blockquote type="cite" cite="mid:m_1XAOrFlaKLdtUjV0yirpj5S8DpPUb7rs-nerlHmjsl9fb99LELC9GNOWNA8Y9gMwistJE5BTmnhJ-pYUx_Jv8NTZDZgWfSEhJdcfj98VI=@ferdeline.com">
<div>(cc’ing in those who are not subscribed to this list)</div>
<div>
<br />
</div>
<div>Hi Rafik,</div>
<div>
<br />
</div>
<div>Thanks for initiating this discussion. </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...</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. </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. </div>
<div>
<br />
</div>
<div>Best wishes,</div>
<div>
<br />
</div>
<div>Ayden</div>
<div>
<br />
</div>
<div id="protonmail_mobile_signature_block">Sent from ProtonMail Mobile</div>
<div>
<br />
<div>
<div>
<br />
</div>On Tue, Jul 24, 2018 at 01:10, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" class="" moz-do-not-send="true">rafik.dammak@gmail.com</a>> wrote:</div>
<blockquote class="protonmail_quote" type="cite">
<div dir="ltr">Hi all,
<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.</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.</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?</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.</div>
<div>
<br />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.</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.</div>
<div>
<br />
</div>
<div>please share your thoughts and suggestions if I missed anything.</div>
<div>
<br />
</div>
<div>in meantime, Maryam can create a wiki space where to put info, having a documents repository and so on. </div>
<div>
<br />
</div>
<div>Best,</div>
<div>
<br />
</div>
<div>Rafik</div>
<div>
<br />
<div class="gmail_quote">
<div dir="ltr">---------- Forwarded message ---------
<br />From: <strong class="gmail_sendername" dir="auto">Rafik Dammak</strong> <span dir="ltr"><<a href="mailto:rafik.dammak@gmail.com" moz-do-not-send="true">rafik.dammak@gmail.com</a>></span>
<br />Date: mar. 17 juil. 2018 à 13:43
<br />Subject: Re: [NCSG-PC] call for volunteers for EPDP team / Selection process
<br />To: Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>>
<br />Cc: ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is" moz-do-not-send="true">ncsg-pc@lists.ncsg.is</a>>
<br />
</div>
<br />
<br />
<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>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex;">
<br />
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br />
<fieldset class="mimeAttachmentHeader"></fieldset> <pre class="moz-quote-pre" wrap="">_______________________________________________NCSG-PC mailing list<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
</blockquote>
</div>