<div dir="ltr">Following the thread, I highlight that <div><br></div><div>1. CROP should not be interfeared with because Outreach and Engagement within the region needs to be done especially with strong focus in Engagement. My view of CROP is that we have done tremendous work and succeeded in getting ALSes. This has been driven by the awesome increase in numbers of the ALSes. Focus of O&E should be towards how do we enhance engagement of the new ALSes and Individuals who come in. </div><div><br></div><div>2. COP is great and definitely in the next FY an appropriate budget should be allocated for the mentees and mentor to attend the meetings. There input and engagement during the mentorship process should be monitored which again calls in the metrics.</div><div><br></div><div>3. Newcomers are great despite most of them do not understand the PDPs, with guidance I believe the fellowship program is great, I happened to snick into one of the NextGens and Fellowship meetings at ICANN60, I can testify that the work done there is simply amazing, Beran was doing a great job with mentees which was really great which I believe all the others are doing. </div><div><br></div><div>4, If funds/slots are available then some can be allocated to the mentees to attend the meetings because these meetings enhance their engagement in the processes.</div><div><br></div><div>5. CROP use of funds out of the region are restricted for ALSes - I believe this needs to be revised because some Global events like the IGF calls in more International participation and Outreach from the RALO is not adequate, this requires joint effort from all regions. This years IGF we have a number of representatives from O&E where the booth is being managed by Glenn, which I could look at as a pilot of how best we can have Outreach and engage members at the iGF, awaiting the report. </div><div><br></div><div>Dev did a great job in the COP program with Beran and Isaac - Personally I appreciate the work done by Dev, I suggest that Since Olivier is leading the program under O&E we should have a call such that best recommendations be discussed and we explore possibilities and impossibilities, opportunities that can be tapped in to maximise the effective and efficient impementation of COP.</div><div><br></div><div>Daniel K. Nanghaka</div></div><div hspace="streak-pt-mark" style="max-height:1px"><img alt="" style="width:0px;max-height:0px;overflow:hidden" src="https://mailfoogae.appspot.com/t?sender=aZGFuaWVsLm5hbmdoYWthQGlzb2MudWc%3D&type=zerocontent&guid=dc9a0b82-ab0b-451e-a96b-a86c29ecc5b0"><font color="#ffffff" size="1">ᐧ</font></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Daniel Nanghaka </div><div dir="ltr"><span style="font-family:Calibri,sans-serif;font-size:12.8px">ALAC Sub-Committee on Outreach and Engagement – Co-chair from AFRALO</span><br><div>ISOC Uganda Chapter </div><div>Tel: +256 772 898298</div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 24 November 2017 at 00:30, Beran Dondeh via Alac-sc-outreach <span dir="ltr"><<a href="mailto:alac-sc-outreach@atlarge-lists.icann.org" target="_blank">alac-sc-outreach@atlarge-lists.icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Dear all, <div><br></div><div>This is just to clarify that this proposed implementation was a document that Dev, myself and Isaac developed and shared with Janice and Alan at the time. We will gladly share with staff to put it on the agenda for the ALAC call on the 28 for further discussion. <div><br></div><div>Best </div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">Beran <br><div><br></div></font></span><div><br><div><blockquote type="cite"><div><div class="h5"><div>On Nov 23, 2017, at 3:10 PM, Olivier MJ Crépin-Leblond <<a href="mailto:ocl@gih.com" target="_blank">ocl@gih.com</a>> wrote:</div><br class="m_4583023464927775704Apple-interchange-newline"></div></div><div><div><div class="h5">
<div text="#000000" bgcolor="#FFFFFF">
Hello all,<br>
<br>
on the process to select mentors/mentees.<br>
<br>
<div class="m_4583023464927775704moz-cite-prefix">On 22/11/2017 00:01, Seun Ojedeji
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="m_4583023464927775704quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> ALAC Selection
Committee?<br>
</div>
</blockquote>
</div>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">SO: I think this group are used to reviewing and
selecting such non-RALO centric positions and may be in a better
place to perform this task. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Overall my suggestion is to push this to the ASC.</div>
</blockquote>
<br>
Recognising it was an excellent idea I shared this with the ALT
yesterday and this idea has received support.<br>
<br>
Today I had a call with Beran Dondeh Gillen, one of this past year's
Mentees. She, along with Isaac Maposa, were mentored by Dev Anand
Teelucksingh and put together a proposal for a follow-up to the
mentoring program. This proposal was that in the next cycle, five
people from At-Large should be mentored, one from each RALO. <br>
<br>
With the news that only 1 mentee & 1 mentor would be funded,
specifically in the lead up to the next ICANN meeting, with 1 other
mentee that would need to be funded by other means, the concept of
having 5 mentees sounded as though not possible. Heidi asked Ergys
Ramaj about having 5 mentees funded, one for each region. That was
categorically refused as there isn't the funding to do this, this
year.<br>
<br>
So Beran suggested a version of the proposed plan: <br>
<br>
- 5 mentees, to be proposed by each RALO, but actually selected, one
per region, by the ALAC Selection Committee.<br>
- 1 mentor selected from a slate of applicants, by the ALAC
Selection Committee<br>
<br>
The mentor starts mentoring all 5 mentees through a set of calls
throughout the year, with the 5 mentees. The mentor travels to each
of the ICANN meetings in the year.<br>
With 3 ICANN meetings in a year, 2 mentees go to March meeting. 2
mentees go to June meeting. 1 mentee goes to AGM in November. Thus,
all 5 mentees have had a chance to attend one funded ICANN meeting.
This means there is actually a shortfall of only 2 travel slots, one
at the March meeting and one at the June meeting. As the focus for
mentoring is about policy, one slot for each of these two meetings
could be a discretionary slot current available for a policy person
to take part in the meeting.<br>
<br>
This is just a simple proposal - Feedback/Comments welcome as soon
as possible! We need to have finalised a process by the end of this
week.<br>
<br>
Kindest regards,<br>
<br>
Olivier <br>
</div></div></div><span class="">
______________________________<wbr>_________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>At-Large Online: <a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a><br>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a></span></div></blockquote></div><br></div></div></div></div><br>______________________________<wbr>_________________<br>
Alac-sc-outreach mailing list<br>
<a href="mailto:Alac-sc-outreach@atlarge-lists.icann.org">Alac-sc-outreach@atlarge-<wbr>lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/alac-sc-outreach" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/alac-sc-outreach</a><br>
<br></blockquote></div><br></div>