About the CROPP Review Team
Dear All, As we discussed on the last Outreach call, there was discussion about the CROPP program and how this would work in At-Large with the CROPP Review Team. Below is the text which sets to explain how this will be done. Comments, suggestions appreciated. Dev Anand --------------- ICANN has launched a Community Regional Outreach Pilot Program (CROPP) for ICANN Fiscal Year 2014 (FY14). The CROPP provides a framework in which each of the 5 At Large RALOS will have available 5 "regional" (three-day) outreach trips funded in FY14. More information about the CROPP can be found at https://community.icann.org/x/QVp-Ag Similar to how RALO budget requests were reviewed by the At-Large Finance and Budget Sub-committee (FBSC) before submitting to ICANN Finance, a CROPP Review Team (CROPP RT) will be established to: - review and approve RALO travel requests to the CROPP to ensure that the objectives of the travel requests are in line with ICANN’s strategic and regional engagement strategy. - confirm with the relevant regional Stakeholder Engagement VP that the purpose/goals of the travel request are consistent with ICANN’s strategic and regional engagement strategy. - submit the requests to ICANN after approval by the CROPP RT. The CROPP RT will comprise two members from each region, one member being from the: * ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC). The CROPP RT will therefore have 10 members. Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes. RALOs and members of the Outreach SC should note the following before submitting travel requests : - Each RALO has up to five (5) regional outreach travel allocations available before the end of ICANN Fiscal Year 2014 which runs between July 2013 and June 30 2014. - Proposed Trips must originate and conclude within the same region and should, wherever practicable, be taken by someone working in or proximate to that territory. - Travel requests must be submitted 8 weeks before any such travel to an event takes place. - Any single outreach event may be attended by multiple persons; however, each traveler is counted as utilizing one (1) of the RALO's allocated trips. - Travel requests must include an alternate traveler that would able to go in case of the proposed traveler is unable to go at the last minute. - The CROPP funding for any outreach travel allocation is limited to transportation, lodging and a per diem for up to three (3) days, two (2) nights ONLY per traveler. - The CROPP does NOT fund items such as conference fees or visa fees for any traveler. - Travel requests cannot be used for travel to a regularly scheduled ICANN Meeting. - If approved, travelers must prepare an complete post-event Trip Assessment within three weeks after the return date which describes how the original purpose(s) and outcome(s) of the Trip were realized. This would be filed with ICANN by the CROPP RT as part of the CROPP program. Proposed Criterion ---------------------------- The RALO Outreach Travel Request must include the following information about the travel request : - Traveler’s name and email address - Alternate Traveler’s name and email address (in the event that the Traveler is unable at the last moment, the alternate would travel in his/her stead) - Departure Date of Requested Travel - Return Date of Requested Travel - Travel Itinerary From City, Country - Travel Itinerary To Destination City and Country - Event/Conference Name, Title or Description - Event/Conference Website - Primary Event/Conference Location - ICANN Geographic Region - Activity Sponsors (the event sponsors must be identified to comply with ICANN Travel Guidelines) - the purpose and goals of the travel request. The purpose and goal should be consistent with any established ICANN regional engagement strategy and/or ICANN's overall mission. - the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented.
Hi Dev, Thank you for sharing this excellent draft. I fully agree with the content. I would like to raise one question about the criterion. Does the event have to have a website? In my region, there might be very interesting meetings about Internet strategies with different stakeholders. There might not be a website linked to it and these kinds of events can be great opportunities to get hold on end users and engage them. What do you think? Best regards, Fatimata Seye Sylla Sent from my iPad On 31 oct. 2013, at 02:03, Dev Anand Teelucksingh <devtee@gmail.com> wrote:
Dear All,
As we discussed on the last Outreach call, there was discussion about the CROPP program and how this would work in At-Large with the CROPP Review Team.
Below is the text which sets to explain how this will be done. Comments, suggestions appreciated.
Dev Anand
---------------
ICANN has launched a Community Regional Outreach Pilot Program (CROPP) for ICANN Fiscal Year 2014 (FY14). The CROPP provides a framework in which each of the 5 At Large RALOS will have available 5 "regional" (three-day) outreach trips funded in FY14.
More information about the CROPP can be found at https://community.icann.org/x/QVp-Ag
Similar to how RALO budget requests were reviewed by the At-Large Finance and Budget Sub-committee (FBSC) before submitting to ICANN Finance, a CROPP Review Team (CROPP RT) will be established to:
- review and approve RALO travel requests to the CROPP to ensure that the objectives of the travel requests are in line with ICANN’s strategic and regional engagement strategy.
- confirm with the relevant regional Stakeholder Engagement VP that the purpose/goals of the travel request are consistent with ICANN’s strategic and regional engagement strategy.
- submit the requests to ICANN after approval by the CROPP RT.
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
RALOs and members of the Outreach SC should note the following before submitting travel requests :
- Each RALO has up to five (5) regional outreach travel allocations available before the end of ICANN Fiscal Year 2014 which runs between July 2013 and June 30 2014.
- Proposed Trips must originate and conclude within the same region and should, wherever practicable, be taken by someone working in or proximate to that territory.
- Travel requests must be submitted 8 weeks before any such travel to an event takes place.
- Any single outreach event may be attended by multiple persons; however, each traveler is counted as utilizing one (1) of the RALO's allocated trips.
- Travel requests must include an alternate traveler that would able to go in case of the proposed traveler is unable to go at the last minute.
- The CROPP funding for any outreach travel allocation is limited to transportation, lodging and a per diem for up to three (3) days, two (2) nights ONLY per traveler.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
- Travel requests cannot be used for travel to a regularly scheduled ICANN Meeting.
- If approved, travelers must prepare an complete post-event Trip Assessment within three weeks after the return date which describes how the original purpose(s) and outcome(s) of the Trip were realized. This would be filed with ICANN by the CROPP RT as part of the CROPP program.
Proposed Criterion ----------------------------
The RALO Outreach Travel Request must include the following information about the travel request :
- Traveler’s name and email address - Alternate Traveler’s name and email address (in the event that the Traveler is unable at the last moment, the alternate would travel in his/her stead) - Departure Date of Requested Travel - Return Date of Requested Travel - Travel Itinerary From City, Country - Travel Itinerary To Destination City and Country - Event/Conference Name, Title or Description - Event/Conference Website - Primary Event/Conference Location - ICANN Geographic Region - Activity Sponsors (the event sponsors must be identified to comply with ICANN Travel Guidelines)
- the purpose and goals of the travel request. The purpose and goal should be consistent with any established ICANN regional engagement strategy and/or ICANN's overall mission.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented. _______________________________________________ Alac-sc-outreach mailing list Alac-sc-outreach@atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/alac-sc-outreach
Please see my comments interlaced within your message. . Thanks. -ed On Thu, Oct 31, 2013 at 2:03 AM, Dev Anand Teelucksingh <devtee@gmail.com>wrote:
Dear All,
As we discussed on the last Outreach call, there was discussion about the CROPP program and how this would work in At-Large with the CROPP Review Team.
Below is the text which sets to explain how this will be done. Comments, suggestions appreciated.
Dev Anand
---------------
ICANN has launched a Community Regional Outreach Pilot Program (CROPP) for ICANN Fiscal Year 2014 (FY14). The CROPP provides a framework in which each of the 5 At Large RALOS will have available 5 "regional" (three-day) outreach trips funded in FY14.
More information about the CROPP can be found at https://community.icann.org/x/QVp-Ag
Similar to how RALO budget requests were reviewed by the At-Large Finance and Budget Sub-committee (FBSC) before submitting to ICANN Finance, a CROPP Review Team (CROPP RT) will be established to:
- review and approve RALO travel requests to the CROPP to ensure that the objectives of the travel requests are in line with ICANN’s strategic and regional engagement strategy.
- confirm with the relevant regional Stakeholder Engagement VP that the purpose/goals of the travel request are consistent with ICANN’s strategic and regional engagement strategy.
- submit the requests to ICANN after approval by the CROPP RT.
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
This committee is too large and volunteers very scarce. I propose to make it smaller with only Outreach SC members. FBSC members do not have too much relevance in CROPP since budget allocation for this program is almost pre-set at 5 trips per region.
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
I suggest that we make aware all RAOS about CROPP sooner than later. We are getting close to the of the year. For January 2014 events (if there are any) people will have to submit the paperwork by mid November 2013.
RALOs and members of the Outreach SC should note the following before submitting travel requests :
- Each RALO has up to five (5) regional outreach travel allocations available before the end of ICANN Fiscal Year 2014 which runs between July 2013 and June 30 2014.
- Proposed Trips must originate and conclude within the same region and should, wherever practicable, be taken by someone working in or proximate to that territory.
- Travel requests must be submitted 8 weeks before any such travel to an event takes place.
- Any single outreach event may be attended by multiple persons; however, each traveler is counted as utilizing one (1) of the RALO's allocated trips.
- Travel requests must include an alternate traveler that would able to go in case of the proposed traveler is unable to go at the last minute.
- The CROPP funding for any outreach travel allocation is limited to transportation, lodging and a per diem for up to three (3) days, two (2) nights ONLY per traveler.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
These fees should be included in the reimbursement otherwise we may be limiting the type of events that the region can go to.
- Travel requests cannot be used for travel to a regularly scheduled ICANN Meeting.
- If approved, travelers must prepare an complete post-event Trip Assessment within three weeks after the return date which describes how the original purpose(s) and outcome(s) of the Trip were realized. This would be filed with ICANN by the CROPP RT as part of the CROPP program.
Proposed Criterion ----------------------------
The RALO Outreach Travel Request must include the following information about the travel request :
- Traveler’s name and email address - Alternate Traveler’s name and email address (in the event that the Traveler is unable at the last moment, the alternate would travel in his/her stead) - Departure Date of Requested Travel - Return Date of Requested Travel - Travel Itinerary From City, Country - Travel Itinerary To Destination City and Country - Event/Conference Name, Title or Description - Event/Conference Website - Primary Event/Conference Location - ICANN Geographic Region - Activity Sponsors (the event sponsors must be identified to comply with ICANN Travel Guidelines)
- the purpose and goals of the travel request. The purpose and goal should be consistent with any established ICANN regional engagement strategy and/or ICANN's overall mission.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented.
I am troubled by this. For example: The main thrust behind this pilot is to Outreach. So, I presume that one of the deliverables will be to provide Outreach results and I am not sure how you can measure and document that. It will be a good idea to create a template for an imaginary event with all blanks filled. The template can help RALOs in preparing the documentation required by CROPP. _______________________________________________
Alac-sc-outreach mailing list Alac-sc-outreach@atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/alac-sc-outreach
-- *NOTICE:* This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately.
Dear Eduardo, Thanks for your comments. My comments inline On Thu, Oct 31, 2013 at 2:15 PM, Eduardo Diaz <eduardodiazrivera@gmail.com>wrote:
Please see my comments interlaced within your message. .
Thanks.
-ed
On Thu, Oct 31, 2013 at 2:03 AM, Dev Anand Teelucksingh <devtee@gmail.com>wrote:
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
This committee is too large and volunteers very scarce. I propose to make it smaller with only Outreach SC members. FBSC members do not have too much relevance in CROPP since budget allocation for this program is almost pre-set at 5 trips per region.
The CROPP calls for 2 persons from each RALO to act as program coordinators, so that is 10 persons already. Hence a RALO having 2 members on the CROPP RT (one from outreach SC, one from FBSC) should be achievable.
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
I suggest that we make aware all RAOS about CROPP sooner than later. We are getting close to the of the year. For January 2014 events (if there are any) people will have to submit the paperwork by mid November 2013.
Agreed. I do want to send the text by November 1 2013 to the RALOs.
RALOs and members of the Outreach SC should note the following before submitting travel requests :
- The CROPP funding for any outreach travel allocation is limited to transportation, lodging and a per diem for up to three (3) days, two (2) nights ONLY per traveler.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
These fees should be included in the reimbursement otherwise we may be limiting the type of events that the region can go to
Unfortunately, with this pilot program, it is not included. I've mentioned this in the GSE outreach call earlier today, but there is no mechanism within the CROPP to get such funding for these and other such meeting logistics (eg funds to operate a booth at a conference).
.
- Travel requests cannot be used for travel to a regularly scheduled ICANN Meeting.
- If approved, travelers must prepare an complete post-event Trip Assessment within three weeks after the return date which describes how the original purpose(s) and outcome(s) of the Trip were realized. This would be filed with ICANN by the CROPP RT as part of the CROPP program.
Proposed Criterion ----------------------------
The RALO Outreach Travel Request must include the following information about the travel request :
- the purpose and goals of the travel request. The purpose and goal should be consistent with any established ICANN regional engagement strategy and/or ICANN's overall mission.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented.
I am troubled by this. For example: The main thrust behind this pilot is to Outreach. So, I presume that one of the deliverables will be to provide Outreach results and I am not sure how you can measure and document that. It will be a good idea to create a template for an imaginary event with all blanks filled. The template can help RALOs in preparing the documentation required by CROPP.
Well possible examples of clear purposes and outcomes : - a speaker/panellist representing ICANN At-Large to a diverse number of persons that are (presumably) involved or interested in Internet governance. A deliverable would be audio and video recordings of such an event. If the profile of ICANN is raised further by reporting in the local media (newspaper, radio, tv), then that's is also a clear additional outcome that can be pointed to in the trip assessment. - obtaining contact information from members of organisations that can join ICANN At-Large. So if the event will have persons from organisations that can be possible At-Large candidates, then a purpose will be to meet and exchange information about ICANN At-Large with a specific number of organisations. A deliverable will be to have such contact information of possible organisations that can join At-Large. This information can be followed up by the regional members of the Outreach SC to have a special conference call (or join the RALO monthly call, etc) with those prospective At-Large members. If they sign up immediately within 3 weeks, that would be a great deliverable especially if from a country without At-Large representation. Anyone have other suggestions? Dev Anand
Eduardo, please see my comments in-line: On 31/10/2013 18:15, Eduardo Diaz wrote:
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
This committee is too large and volunteers very scarce. I propose to make it smaller with only Outreach SC members. FBSC members do not have too much relevance in CROPP since budget allocation for this program is almost pre-set at 5 trips per region.
I hear what you're saying, but one member from each region is not enough because what happens when that member cannot make it to a call - their region is not covered. Also, it is the FBSC that deals primarily with ICANN Strategic issues, so having a mixed committee from both groups is a good idea. That said, I also understand that there may be some people who are both members of the FBSC *and* the Outreach SC. In such a case, they could be covering both positions... but I do have concerns about 1 person missing a call thus their region missing out.
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
I suggest that we make aware all RAOS about CROPP sooner than later. We are getting close to the of the year. For January 2014 events (if there are any) people will have to submit the paperwork by mid November 2013.
Absolutely agreed - hence the 2 calls next week, one for the Outreach SC and one for the FBSC. I hope that they will be short, that we will find consensus quickly and that the CROPP program can start immediately afterwards. Members of the WG will need to immediately relate back to their region & get their region to identify good opportunities. I am hoping that this will be catalysed by meeting in BA shortly.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
These fees should be included in the reimbursement otherwise we may be limiting the type of events that the region can go to.
On this one, unfortunately we do not set the rules. We'll be able to relate this to ICANN Staff when we see them in BA.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented.
I am troubled by this. For example: The main thrust behind this pilot is to Outreach. So, I presume that one of the deliverables will be to provide Outreach results and I am not sure how you can measure and document that. It will be a good idea to create a template for an imaginary event with all blanks filled. The template can help RALOs in preparing the documentation required by CROPP.
Excellent idea! The requisite is set by ICANN in their design for the CROPP program. In making an example template perhaps could we ask ICANN Staff in charge of CROPP to help us out with example potential outcomes. Kind regards, Olivier
Thank you Dev and Olivier for the comments. I am also confused about the framework structure. I am not sure to whom the CROPP RT reports to. Another committee named CROPP? ICANN staff? whom? Thanks in advance. -ed On Thu, Oct 31, 2013 at 4:21 PM, Olivier MJ Crepin-Leblond <ocl@gih.com>wrote:
Eduardo,
please see my comments in-line:
On 31/10/2013 18:15, Eduardo Diaz wrote:
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
This committee is too large and volunteers very scarce. I propose to make it smaller with only Outreach SC members. FBSC members do not have too much relevance in CROPP since budget allocation for this program is almost pre-set at 5 trips per region.
I hear what you're saying, but one member from each region is not enough because what happens when that member cannot make it to a call - their region is not covered. Also, it is the FBSC that deals primarily with ICANN Strategic issues, so having a mixed committee from both groups is a good idea. That said, I also understand that there may be some people who are both members of the FBSC *and* the Outreach SC. In such a case, they could be covering both positions... but I do have concerns about 1 person missing a call thus their region missing out.
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
I suggest that we make aware all RAOS about CROPP sooner than later. We are getting close to the of the year. For January 2014 events (if there are any) people will have to submit the paperwork by mid November 2013.
Absolutely agreed - hence the 2 calls next week, one for the Outreach SC and one for the FBSC. I hope that they will be short, that we will find consensus quickly and that the CROPP program can start immediately afterwards. Members of the WG will need to immediately relate back to their region & get their region to identify good opportunities. I am hoping that this will be catalysed by meeting in BA shortly.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
These fees should be included in the reimbursement otherwise we may be limiting the type of events that the region can go to.
On this one, unfortunately we do not set the rules. We'll be able to relate this to ICANN Staff when we see them in BA.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented.
I am troubled by this. For example: The main thrust behind this pilot is to Outreach. So, I presume that one of the deliverables will be to provide Outreach results and I am not sure how you can measure and document that. It will be a good idea to create a template for an imaginary event with all blanks filled. The template can help RALOs in preparing the documentation required by CROPP.
Excellent idea! The requisite is set by ICANN in their design for the CROPP program. In making an example template perhaps could we ask ICANN Staff in charge of CROPP to help us out with example potential outcomes.
Kind regards,
Olivier
-- *NOTICE:* This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately.
Dear Dev and all, thanks for this detailed summary on the new CROPP, composition and framework what sounds promising. Hopefully, this will strengthen various RALO ideas and projects for regional outreach initiatives -- with institutional support from ICANN for the first time. Kind regards, Wolf Dev Anand Teelucksingh wrote Thu, 31 Oct 2013 02:03:
Dear All,
As we discussed on the last Outreach call, there was discussion about the CROPP program and how this would work in At-Large with the CROPP Review Team.
Below is the text which sets to explain how this will be done. Comments, suggestions appreciated.
Dev Anand
---------------
ICANN has launched a Community Regional Outreach Pilot Program (CROPP) for ICANN Fiscal Year 2014 (FY14). The CROPP provides a framework in which each of the 5 At Large RALOS will have available 5 "regional" (three-day) outreach trips funded in FY14.
More information about the CROPP can be found at https://community.icann.org/x/QVp-Ag
Similar to how RALO budget requests were reviewed by the At-Large Finance and Budget Sub-committee (FBSC) before submitting to ICANN Finance, a CROPP Review Team (CROPP RT) will be established to:
- review and approve RALO travel requests to the CROPP to ensure that the objectives of the travel requests are in line with ICANN’s strategic and regional engagement strategy.
- confirm with the relevant regional Stakeholder Engagement VP that the purpose/goals of the travel request are consistent with ICANN’s strategic and regional engagement strategy.
- submit the requests to ICANN after approval by the CROPP RT.
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
RALOs and members of the Outreach SC should note the following before submitting travel requests :
- Each RALO has up to five (5) regional outreach travel allocations available before the end of ICANN Fiscal Year 2014 which runs between July 2013 and June 30 2014.
- Proposed Trips must originate and conclude within the same region and should, wherever practicable, be taken by someone working in or proximate to that territory.
- Travel requests must be submitted 8 weeks before any such travel to an event takes place.
- Any single outreach event may be attended by multiple persons; however, each traveler is counted as utilizing one (1) of the RALO's allocated trips.
- Travel requests must include an alternate traveler that would able to go in case of the proposed traveler is unable to go at the last minute.
- The CROPP funding for any outreach travel allocation is limited to transportation, lodging and a per diem for up to three (3) days, two (2) nights ONLY per traveler.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
- Travel requests cannot be used for travel to a regularly scheduled ICANN Meeting.
- If approved, travelers must prepare an complete post-event Trip Assessment within three weeks after the return date which describes how the original purpose(s) and outcome(s) of the Trip were realized. This would be filed with ICANN by the CROPP RT as part of the CROPP program.
Proposed Criterion ----------------------------
The RALO Outreach Travel Request must include the following information about the travel request :
- Traveler’s name and email address - Alternate Traveler’s name and email address (in the event that the Traveler is unable at the last moment, the alternate would travel in his/her stead) - Departure Date of Requested Travel - Return Date of Requested Travel - Travel Itinerary From City, Country - Travel Itinerary To Destination City and Country - Event/Conference Name, Title or Description - Event/Conference Website - Primary Event/Conference Location - ICANN Geographic Region - Activity Sponsors (the event sponsors must be identified to comply with ICANN Travel Guidelines)
- the purpose and goals of the travel request. The purpose and goal should be consistent with any established ICANN regional engagement strategy and/or ICANN's overall mission.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented. _______________________________________________ Alac-sc-outreach mailing list Alac-sc-outreach@atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/alac-sc-outreach
EuroDIG Secretariat http://www.eurodig.org/ mobile +41 79 204 83 87 Skype: Wolf-Ludwig EURALO - ICANN's Regional At-Large Organisation http://euralo.org Profile on LinkedIn http://ch.linkedin.com/in/wolfludwig
+1 2013/11/1, Wolf Ludwig <wolf.ludwig@comunica-ch.net>:
Dear Dev and all,
thanks for this detailed summary on the new CROPP, composition and framework what sounds promising. Hopefully, this will strengthen various RALO ideas and projects for regional outreach initiatives -- with institutional support from ICANN for the first time.
Kind regards, Wolf
Dev Anand Teelucksingh wrote Thu, 31 Oct 2013 02:03:
Dear All,
As we discussed on the last Outreach call, there was discussion about the CROPP program and how this would work in At-Large with the CROPP Review Team.
Below is the text which sets to explain how this will be done. Comments, suggestions appreciated.
Dev Anand
---------------
ICANN has launched a Community Regional Outreach Pilot Program (CROPP) for ICANN Fiscal Year 2014 (FY14). The CROPP provides a framework in which each of the 5 At Large RALOS will have available 5 "regional" (three-day) outreach trips funded in FY14.
More information about the CROPP can be found at https://community.icann.org/x/QVp-Ag
Similar to how RALO budget requests were reviewed by the At-Large Finance and Budget Sub-committee (FBSC) before submitting to ICANN Finance, a CROPP Review Team (CROPP RT) will be established to:
- review and approve RALO travel requests to the CROPP to ensure that the objectives of the travel requests are in line with ICANN’s strategic and regional engagement strategy.
- confirm with the relevant regional Stakeholder Engagement VP that the purpose/goals of the travel request are consistent with ICANN’s strategic and regional engagement strategy.
- submit the requests to ICANN after approval by the CROPP RT.
The CROPP RT will comprise two members from each region, one member being from the:
* ICANN At-Large Outreach Sub-committee (Outreach SC); and one from the: * ICANN At-Large Finance and Budget Sub-committee (FBSC).
The CROPP RT will therefore have 10 members.
Given that travel requests needs a minimum of two (2) weeks to be processed by the CROPP RT plus six (6) weeks for the requests to be processed by ICANN, RALO leaders in coordination with their members on the Outreach SC should submit their outreach travel requests to the CROPP RT eight (8) weeks before any such travel to an event for outreach purposes.
RALOs and members of the Outreach SC should note the following before submitting travel requests :
- Each RALO has up to five (5) regional outreach travel allocations available before the end of ICANN Fiscal Year 2014 which runs between July 2013 and June 30 2014.
- Proposed Trips must originate and conclude within the same region and should, wherever practicable, be taken by someone working in or proximate to that territory.
- Travel requests must be submitted 8 weeks before any such travel to an event takes place.
- Any single outreach event may be attended by multiple persons; however, each traveler is counted as utilizing one (1) of the RALO's allocated trips.
- Travel requests must include an alternate traveler that would able to go in case of the proposed traveler is unable to go at the last minute.
- The CROPP funding for any outreach travel allocation is limited to transportation, lodging and a per diem for up to three (3) days, two (2) nights ONLY per traveler.
- The CROPP does NOT fund items such as conference fees or visa fees for any traveler.
- Travel requests cannot be used for travel to a regularly scheduled ICANN Meeting.
- If approved, travelers must prepare an complete post-event Trip Assessment within three weeks after the return date which describes how the original purpose(s) and outcome(s) of the Trip were realized. This would be filed with ICANN by the CROPP RT as part of the CROPP program.
Proposed Criterion ----------------------------
The RALO Outreach Travel Request must include the following information about the travel request :
- Traveler’s name and email address - Alternate Traveler’s name and email address (in the event that the Traveler is unable at the last moment, the alternate would travel in his/her stead) - Departure Date of Requested Travel - Return Date of Requested Travel - Travel Itinerary From City, Country - Travel Itinerary To Destination City and Country - Event/Conference Name, Title or Description - Event/Conference Website - Primary Event/Conference Location - ICANN Geographic Region - Activity Sponsors (the event sponsors must be identified to comply with ICANN Travel Guidelines)
- the purpose and goals of the travel request. The purpose and goal should be consistent with any established ICANN regional engagement strategy and/or ICANN's overall mission.
- the Proposed Outcomes. The Proposed Outcomes should be a clear, deliverable that can be measured and documented. _______________________________________________ Alac-sc-outreach mailing list Alac-sc-outreach@atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/alac-sc-outreach
EuroDIG Secretariat http://www.eurodig.org/ mobile +41 79 204 83 87 Skype: Wolf-Ludwig
EURALO - ICANN's Regional At-Large Organisation http://euralo.org
Profile on LinkedIn http://ch.linkedin.com/in/wolfludwig _______________________________________________ Alac-sc-outreach mailing list Alac-sc-outreach@atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/alac-sc-outreach
participants (6)
-
Dev Anand Teelucksingh -
Eduardo Diaz -
Fatimata -
Olivier MJ Crepin-Leblond -
Pascal Bekono -
Wolf Ludwig