[ALAC] URGENT: Community Onboarding Program

[Alan Greenberg]

There will be a Community Onboarding Program at ICANN62 in Panama.

We have a choice of having ONE mentee and ONE mentor (both of whom 
will receive travel support), or TWO mentees and One mentor who is 
already funded to attend the meeting.

I am asking each RALO Chair, in consultation with their RALO 
leadership team and their three ALAC Members to identify possible 
mentees and mentors.

This is a Policy Meeting, so mentees should have a good grasp of 
ICANN already, and be prepared to participate and learn from all of 
the discussions going on. The Mentor should be someone who is 
prepared to spend time with the mentees and help them understand what 
is happening.

A with the COB program last time, the ALAC Appointee Selection 
Committee will make the selections.

To be clear, I am looking for from each RALO Chair, sent to me and staff:

1. A preference for whether we should have 2 mentees and an already 
funded mentor, or one mentee and a mentor who will be funded to 
attend just as a mentor. If we select the former, we need to be 
really sure the mentor will take the responsibility seriously. A 
person dedicated to that task may take it more seriously, but that 
implies just one mentee.

2. Suggestions for good mentee(s)

3. Suggestions for good mentors, both already funded and not yet funded.

4. In all cases, there should be a brief background and/or rationale 
if the people are not very well known to us. And please brief your 
AASC members on your candidates (see 
https://community.icann.org/x/VwebAw for membership list).

You should verify with anyone you are suggesting that they are able 
to travel to the Panama meeting.

For the record, at ICANN 61, we had two COB mentees, one from APRALO 
and one from LACRALO.

The deadline for submission of names is Sunday, 22 April 2018 at 16:00 UTC.

Alan  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20180412/889b04eb/attachment.html>