July 2018 - Alac-sc-outreach

NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call
by ICANN At-Large Staff July 31, 2018

July 31, 2018

Dear All, Please complete the Doodle poll to schedule the next ALAC Subcommittee on Outreach and Engagement Call on Monday, 20 August 2018. Doodle: https://doodle.com/poll/kpi4c6r3eq6kipsb I have enabled the time zone so that it can be changed to your zone. This doodle will close on Tuesday, 14 August 2018. Thank you. Kind Regards, Yeşim Nazlar

1 0

Urgent questions about CROP guidelines for FY19
by Olivier MJ Crépin-Leblond July 25, 2018

July 25, 2018

Dear Colleagues, I am reading through the CROP FY19 guidelines ( https://community.icann.org/x/yicFBQ ) and as already mentioned in the meeting we had with CROP staff, and wearing my EURALO Chair hat, I have real problems understanding the thinking behind some of this year's guidelines/restrictions. - The first out of the three CROP trips needs to be used on an ICANN meeting What is the thinking behind this? CROP is meant for Outreach. Outreach at an ICANN meeting is already taking place through the Fellowship, through the NextGen, through the joint NCSG-ALAC or NCUC-At-Large sessions that we have organised. An ICANN meeting already has the regional leadership in attendance and they are already organising outreach there. We also make sure that we have volunteers at the booth, and frankly our experience at the ICANN or RALO booth at an ICANN meeting is that there are very few newcomers that are not already participating in the various other programs. And then CROP is only for 4 days, 3 nights, so anyone attending an ICANN meeting through CROP will only be there for an amount of time that is shorter than the shortest of ICANN meetings. What good is one person going to do when we already have our regular travellers there? So what we risk doing is to really waste that slot. - Alternatively, the first slot can be used for another type of meeting organised by ICANN, such as GDD summits. GDD summits are reserved solely for Contracted Parties (rather explicitly: https://www.icann.org/gddsummit ) so this does not make sense. Other local ICANN meetings are targeted towards a specific type of stakeholder, like businesses or government. Any CROP traveller from At-Large would not fit in the criteria for participants. Domains Fora that organised by ICANN are commercial in scope, so again, this does not correspond with the scope of the ALAC. The only meetings that would fit the At-Large purview are meetings organised by ICANN for end users. To my understanding, in 20 years of history, ICANN has never organised such a meeting. I would *really* like to see such a meeting being created by ICANN. - Then we can use the two remaining CROP slots on an ICANN supported meeting What does this mean? - does this mean a meeting that ICANN is sponsoring financially? - does this mean a meeting where ICANN is already organising sessions/workshops? - does this mean a meeting that is not sponsored by ICANN or where ICANN is not organising sessions/workshops, but where a member of the ICANN Board or Staff is attending? Given that an application needs to be made more than 6 weeks and 5 working days in advance of the date of the meeting, how is a RALO meant to know if ICANN is supporting the above? Is a list of ICANN approved meetings going to be published? Or does a RALO need to ask the GSE Team each time whether ICANN is supporting this meeting? These are my questions/concerns regarding the new CROP process. Now onto the second part of my email and it is concerning the CROP RT/PC. At the moment, the CROP Review Team (CROP RT) is made up of 10 people (plus 2 observers and one Chair), two from each region, who collectively look at each CROP application and ensure that the application follows the program guidelines, including minimum time for an application. It also checks any discrepancy with the application. The CROP RT members are selected by each region, with one member coming from the Finance & Budget Sub-Committee (FBSC) and one member coming from the Outreach & Engagement working group. Why? It is because part of the checking of applications is to check that they correspond with the ICANN overall Strategy Goals (which the FBSC is involved in) and with the Outreach & Engagement plans of the ALAC (which the Sub-Committee on Outreach & Engagement is in charge of). I do not think that this was well understood. There is a proposal that this committee be disbanded/ended. The CROP Program Committee (CROP PC) is mandated by the CROP staff as this is the Committee that interfaces the ALAC with CROP staff. This cannot be disbanded. At present, the CROP PC is exactly the same people as the CROP RT. But ending the CROP RT does not let you end the CROP PC which needs to remain in operation. So my question which I asked on yesterday's call but which I do not think I received a response for, was that since we keep the CROP PC but not the CROP RT we effectively are not changing the group? The only thing we are doing is to take away the method on how we currently select the CROP PC, and also remove the need for a CROP RT representative to check other RALO CROP applications. Thus this checking would need to be done by CROP program staff. So my questions here : how can a RALO change its CROP PC representatives now? Are these people appointed by the ALAC or by the RALOs. Do these people need to be in any other committee (like FBSC or O&E)? I would appreciate that we work out these issues as soon as possible, because until then, EURALO will be in the impossibility to submit a CROP request. Our deadline for submitting a CROP request for ICANN Barcelona (20th October 2018) is Friday 31st August. Kindest regards, Olivier MJ Crépin-Leblond EURALO Chair

8 15

Fwd: FY19 CROP - Ready for use
by Olivier MJ Crépin-Leblond July 23, 2018

July 23, 2018

Dear colleagues, with the new financial year FY19 having started on please be so kind to find the information below about the Community Regional Outreach Program (CROP). At present, we need to do two things: 1. appoint or re-appoint CROP programme committee representatives 2. draft our Outreach Strategic Plan May I suggest that we appoint two new representatives on this committee? We need to do this as soon as possible. As this is an administrative function, may I suggest that we send out a call for candidates and have the EURALO Board make the selection? I would recommend that at least one of the two people should be Wale Bakare or me, as this function is closely related to EURALO strategy. As for drafting out an Outreach Strategic Plan, may I suggest that this be undertaken by the EURALO ALS Engagement Task Force? Work needs to start immediately. Kindest regards Olivier -------- Forwarded Message -------- Subject: FY19 CROP - Ready for use Date: Tue, 3 Jul 2018 17:11:48 +0000 From: Benedetta Rossi <benedetta.rossi(a)icann.org> To: CC: At-Large RALO and GNSO Constituency Leaders: We are pleased to report that the Community Regional Outreach Program (CROP) FY19 Wiki space is now ready to be used. Please also refer to Sally Costerton’s and David Olive’s blog post published today <https://www.icann.org/news/blog/fy19-community-regional-outreach-program-cr…> on this subject. For FY19, US$50,000 was allocated to the final FY19 Budget for CROP. The Board made this decision on the recommendation of ICANN organization, based on community consultations and public comments on the Draft FY19 Operating Plan & Budget as well as further consideration about how to provide support to community outreach efforts while remaining within appropriate budget limits. As part of this process, staff was directed to review current guidelines and develop improved, additional criteria. To ensure consistency with other community travel and outreach requests administered under all ICANN programs, the final criteria balances the program goals with the need to ensure cost-effectiveness. The general principle governing the updated CROP guidelines <https://community.icann.org/x/yicFBQ> is that CROP may be used for FY19 outreach efforts that are *directly and demonstrably related to ongoing ICANN policy, technical and advisory activities*. CROP allocations will be subject to the new CROP guidelines <https://community.icann.org/x/yicFBQ> and specific criteria, with a staff assessment to be conducted at the end of FY19. *Each RALO & each eligible GNSO Constituency (BC, IPC, ISPCP, NCUC & NPOC) is allocated up to three (3) individual regional trips (4 days and 3 nights maximum per trip).* Travel allocations are to be used for the following types of events: * ICANN Public Meetings occurring in the relevant region; or * Official meetings organized by ICANN Org occurring in the relevant region; or * If there is _no Public Meeting or official ICANN meeting occurring in the relevant region in that FY,_ a meeting in that region that is assessed by the relevant regional GSE VP as being: 1. Directly and demonstrably related to ongoing ICANN policy, advisory or technical activities (e.g. a Regional Internet Registry meeting), and 2. Consistent with ICANN Org’s outreach plan for that region. (For RALOs, “relevant region” means the region applicable to each RALO. For GNSO Constituencies, this means the region where the ICANN Public Meeting, CANN-organized meeting, or an event assessed under the criteria outlined in (ii) above is taking place.) * *Please note:*if a RALO or eligible GNSO group has used at least one allocation for an ICANN meeting (or ICANN-organized meeting), it may use its remaining allocation(s) for meetings that are assessed by the relevant regional GSE VP as being directly and demonstrably related to ongoing ICANN policy, technical or advisory activities (e.g. RIR meetings). * *No out-of-region travel will be permitted. * We invite you to browse through the CROP FY19 space <https://community.icann.org/x/pIRHBQ> and through the CROP Procedures & Guidelines page <https://community.icann.org/x/yicFBQ> for details about the program. Please email us (crop-staff(a)icann.org <mailto:crop-staff@icann.org>) if you have questions on specific aspects of the FY19 program. For a complete list of individuals who have CROP duties, please see our CROP Contacts page <https://community.icann.org/x/fgKfB>. If there are any changes to your community Program Coordinators for CROP, please inform us as soon as possible so the list can be updated accordingly. We are looking forward to collaborating with all of you over this fiscal year. Please don’t hesitate to reach out to CROP Staff: crop-staff(a)icann.org <mailto:crop-staff@icann.org> Kind regards from your extended CROP Team: Benedetta Rossi (crop-staff(a)icann.org <mailto:crop-staff@icann.org>) -- *Benedetta Rossi *| Manager, Policy Support & Community Services benedetta.rossi(a)icann.org <mailto:benedetta.rossi@icann.org> | +33.610.38.27.02 *ICANN* | Internet Corporation for Assigned Names and Numbers

3 3

Re: [Alac-sc-outreach] Request for Special O&E Call with CROP Staff and GSE
by DANIEL NANGHAKA July 23, 2018

July 23, 2018

Dear Staff, I would like to request for a special O&E call with CROP staff and GSE to answer the questions/issues on CROP that have arose which include but not limited to Oureach at ICANN Meetings and ICANN Supported Meetings. Thie purpose of the call will be mainly to discuss CROP from CROP RT, to CROP Process, dee The reference to the question is in the thread:* [Alac-sc-outreach] Urgent questions about CROP guidelines for FY19* Furthermore, there is a need to review the process with a discussion with the WG - apparently, there has been limited or no consultation regarding CROP which raises this concern. In reference to the ALAC Review Implementation Overview Proposal https://community.icann.org/display/ALRW/At-Large+Review+Implementation+Ove… Items #5 & #12 regarding the Uneven contribution of At-Large to a coordinated ICANN strategy for ‘Outreach and Engagement’. Missed opportunities for coordination with other constituencies and ICANN staff. I believe this is one of the scenarios that need to be addressed and jointly discussed in order to come up with appropriate strategies regarding to Outreach and Engagement especially CROP in this case. Further to the discussion, we can discuss a collaborative Outreach and Engagement Strategy with the Co-Chairs and through this we can always work with strong cordination. Looking forward to the Call. Kind Regards Daniel K. Nanghaka -- Regards Nanghaka Daniel K. Executive Director - ILICIT Africa / Chair - FOSSFA / Community Lead - ISOC Uganda Chapter / Geo4Africa Lead / Organising Team - FOSS4G2018 Mobile +256 772 898298 (Uganda) Skype: daniel.nanghaka ----------------------------------------- *"Working for Africa" * ----------------------------------------- ᐧ ᐧ ᐧ

1 0

REMINDER / Meeting Invitation: ALAC Subcommittee on Outreach and Engagement Call on Wednesday, 18 July 2018 at 17:00 UTC
by ICANN At-Large Staff July 18, 2018

July 18, 2018

Dear All, Further to the Doodle poll, the next ALAC Subcommittee on Outreach and Engagement Call is scheduled on Wednesday, 18 July 2018 at 17:00 UTC. For other times: https://tinyurl.com/ybxmg8m4 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/Z4pHBQ Wiki Workspace: https://community.icann.org/x/cqfbAQ Adobe Connect Link: https://participate.icann.org/alacso/ Conference ID: EN: 1638 ES: 1738 Dial-in numbers: http://adigo.com/icann If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<applewebdata://47A8FDB3-E19D-4BBA-AC04-7262B4637119/staff@atlarge.icann.org> with your preferred number. Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/@ICANNAtLarge> [cid:image001.png@01D41948.531C99B0] From: ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> Date: Wednesday, July 4, 2018 at 2:31 PM To: Alac-sc-outreach <alac-sc-outreach(a)atlarge-lists.icann.org<mailto:alac-sc-outreach@atlarge-lists.icann.org>> Cc: ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> Subject: NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call Dear All, Please complete the Doodle poll to schedule the next ALAC Subcommittee on Outreach and Engagement Call for the week of 16 July 2018. Doodle: https://doodle.com/poll/yn5mgpfcevb62bqz I have enabled the time zone so that it can be changed to your zone. This doodle will close on Tuesday, 10 July 2018. Thank you. Kind Regards, Yeşim Nazlar

7 6

Meeting Invitation: ALAC Subcommittee on Outreach and Engagement Call on Wednesday, 18 July 2018 at 17:00 UTC
by ICANN At-Large Staff July 18, 2018

July 18, 2018

Dear All, Further to the Doodle poll, the next ALAC Subcommittee on Outreach and Engagement Call is scheduled on Wednesday, 18 July 2018 at 17:00 UTC. For other times: https://tinyurl.com/ybxmg8m4 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/Z4pHBQ Wiki Workspace: https://community.icann.org/x/cqfbAQ Adobe Connect Link: https://participate.icann.org/alacso/ Conference ID: EN: 1638 ES: 1738 Dial-in numbers: http://adigo.com/icann If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<applewebdata://47A8FDB3-E19D-4BBA-AC04-7262B4637119/staff@atlarge.icann.org> with your preferred number. Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://DC66FE18-271C-4E2B-B202-92C384AFE565/@ICANNAtLarge> [cid:image001.png@01D41948.531C99B0] From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wednesday, July 4, 2018 at 2:31 PM To: Alac-sc-outreach <alac-sc-outreach(a)atlarge-lists.icann.org> Cc: ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call Dear All, Please complete the Doodle poll to schedule the next ALAC Subcommittee on Outreach and Engagement Call for the week of 16 July 2018. Doodle: https://doodle.com/poll/yn5mgpfcevb62bqz I have enabled the time zone so that it can be changed to your zone. This doodle will close on Tuesday, 10 July 2018. Thank you. Kind Regards, Yeşim Nazlar

2 1

At-Large IGF2018 Workspace Now Posted
by Heidi Ullrich July 11, 2018

July 11, 2018

Dear All, As requested during ICANN 62, I have created the At-Large Outreach Activities at IGF 2018 Paris<https://community.icann.org/display/atlarge/At-Large+Outreach+Activities+at…> Workspace. It has been posted on the SC on Outreach and Engagement Workspace as well as the ALAC Portal Workspace. Kind regards, Heidi Heidi Ullrich VP, Policy Development & At-Large Relations Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 (310) 437 - 3956 Fax: +1 (310) 823 - 8649 E-mail: Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

2 1

FINAL REMINDER / NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call
by Yesim Nazlar July 11, 2018

July 11, 2018

Dear All, This is the final reminder for those who haven’t completed the doodle, yet. Thank you. Kind Regards, Yeşim Nazlar From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wednesday, July 4, 2018 at 2:31 PM To: Alac-sc-outreach <alac-sc-outreach(a)atlarge-lists.icann.org> Cc: ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call Dear All, Please complete the Doodle poll to schedule the next ALAC Subcommittee on Outreach and Engagement Call for the week of 16 July 2018. Doodle: https://doodle.com/poll/yn5mgpfcevb62bqz I have enabled the time zone so that it can be changed to your zone. This doodle will close on Tuesday, 10 July 2018. Thank you. Kind Regards, Yeşim Nazlar

1 0

REMINDER / NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call
by Yesim Nazlar July 9, 2018

July 9, 2018

Dear All, Kind reminder for those who haven’t completed the doodle, yet. Thank you. Kind Regards, Yeşim Nazlar From: ICANN At-Large Staff <staff(a)atlarge.icann.org> Date: Wednesday, July 4, 2018 at 2:31 PM To: Alac-sc-outreach <alac-sc-outreach(a)atlarge-lists.icann.org> Cc: ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: NEW DOODLE: ALAC Subcommittee on Outreach and Engagement Call Dear All, Please complete the Doodle poll to schedule the next ALAC Subcommittee on Outreach and Engagement Call for the week of 16 July 2018. Doodle: https://doodle.com/poll/yn5mgpfcevb62bqz I have enabled the time zone so that it can be changed to your zone. This doodle will close on Tuesday, 10 July 2018. Thank you. Kind Regards, Yeşim Nazlar

1 0

ICANN CROP FY19 ready for use by ICANN community
by Dev Anand Teelucksingh July 4, 2018

July 4, 2018

Read the blog post : https://www.icann.org/news/blog/fy19-community-regional-outreach-program-cr… and the CROP FY19 wiki at https://community.icann.org/x/pIRHBQ

7 13