FY17 AC/SO Special Requests
Proposed Requests:
ALAC:
| Request | Description |
|---|---|
At-Large FY16 Special Community Request for a Strategic Working Session for ALAC and RALO Leaders at ICANN Public Meetings 57 and 58. | Given the increased workload of the ALAC and RALO leadership, including the current At-Large Review focusing on the nearly 200 At-Large Structures, the ALAC is again requesting Strategic Working Sessions for the ALAC and RALO Leaders to take place on the Saturday at the start of ICANN 57 and 58.
In particular, this request is for the necessary elements of these ALAC Strategy Sessions, including an external facilitator to lead the ALAC in the prioritizing their workload, facilitation skills and a working lunch. At ICANN 57, both current and incoming ALAC Members, RALO Leaders and Liaisons would be included. . |
| At-Large FY16 Special Community Request for an ALAC Development Session at ICANN 57. | Based on the success of the ALAC Development Session at ICANN 54, the ALAC is again requesting a one day ALAC Development Session for the 15 members of the ALAC, both continuing and incoming members, as well as ccNSO, GNSO and SSAC Liaisons on the last day of the ICANN 57 Meeting to be held in Puerto Rico. This ALAC Development Session, will foster co-operation within the ALAC as well as planning for ongoing and upcoming projects and activities within the ALAC. The Development Session will serve as a team-building exercise to increase collaboration and to work more effectively as a virtual global team inter-sessionally. The Session will also include a session on professional skills development. This latter activity will increase the ability of all ALAC members to develop critical skills needed to more effectively participate in meetings and work in a multi-cultural environment. An external facilitator will lead the session. The requested day for the ALAC Development Session is Friday, 4 November between 12:00 and 18:00. |
This is a continuation of our current pilot program of captioning for 3 RALO and/or ALAC monthly meetings, and/or 3 Working Group meetings or webinars over a 4 month period in FY16. Our goal in this continuation of the pilot is to provide real-time captioning for either 3 RALO meetings a month or 2 RALO and 1 ALAC meeting, and/or 3 working group meetings or webinars a month to enable full participation of all At-Large Users within ICANN. We also want to raise awareness of the importance of including captioning whenever language support is offered. We are targeting RALO meetings since our goal is to increase engagement in ICANN within each of the respective regions. We are also targeting the working groups and webinars for the same reason as well as to promote more engagement from RALOs in these working groups. We think this will lead to more effective participation and engagement within ICANN. This is especially the case for people who are coming from bandwidth challenged countries where lack of bandwidth has limited their participation within ICANN. Adobe Connect is a large user of bandwidth and as such makes it difficult for those with limited bandwidth to fully participate. Adigo calls are helpful in that regard, but often in many places cell coverage is sparse and calls often drop or use up too much of a person’s quota. The goal of the pilot is to gather the necessary metrics to illustrate the need for captioning not only for accessibility reasons but also for those with limited bandwidth. The data gained from this second phase of the pilot should help us meet these goals and show the need for captioning ICANN wide. In the original phase of the pilot we restricted ourselves to only providing English Language captions, but in this second phase we want to add support for Spanish and/or French as we have gotten requests for captioning in this language. | |
RALOs:
Cross-RALO: Development Session for RALO Chairs and Secretaries at the 2016 AGM (TBC)
AFRALO
APRALO
EURALO
LACRALO
NARALO
NARALO - General Assembly at ICANN 57
- Draft NARALO GA submission - Authors Eduardo, Judith and Glenn This is an update of last years' submission for the GA @Arin
- Project Management Tool Trello
https://trello.com/b/mwvu440a/naralo-general-assembly
| RALO | Request | Description |
|---|---|---|
| AFRALO | ||
| AFRALO |
| |
| AFRALO | ||
| AFRALO | ||
| APRALO | ||
| APRALO | ||
| APRALO | ||
| APRALO | ||
| APRALO | ||
FY17 ALAC Criteria for Special Requests:
- Outreach should not be a major focus. Activities to improve engagement with existing members is encouraged.
- If any request is made on outreach, it should probably go through the CROPP program and not this special request process.
- Proposals should include ways in which will make the ALAC and/or the At-Large community more effective and develop the At-Large community.
- RALO requests must go through a bottom up process within their RALO prior to being submitted for consideration by the FBSC.
- RALOs should consider the General Assembly/Summit timeline (NARALO and AFRALO are scheduled for requesting General Assemblies during FY17)
- They must be explicitly supported by the RALO representative on the FBSC.
- Staff is currently expecting that basic resources for community communications/printing will be supported through the core ICANN budget, but that community proposals for printing , etc. will be accepted as a back-up in case expectations change. Specific proposals for communications resources beyond simple printing and editing functions should be prepared and submitted.
FY17 Community Special Budget Request Timeline
FY17 Community Special Budget Request Timeline | Start | End |
Kick off and Submission Period | 15 December 2015 | 15 February 2016 |
| FBSC representatives and/or staff to send notice of opening of FY17 special request process to RALOs | 21 December 2015 | 24 January 2016 |
| RALOs to review any ALS request or complete a template on behalf of the RALO and send requests to | 4 January 2016 | 22 January 2016 |
| Discussion of Proposals with Finance Staff and FBSC | 25 January 2016 | 29 January 2016 |
| Revised proposals to be sent to the FBSC for final review. | 5 February 2016 | 5 February 2016 |
| The FBSC to review all the RALO requests. | 8 February 2016 | 12 February 2016 |
| Submission Deadline (Staff will send the FBSC approved requests to Finance on 15 February 2015.) | 15 February 2016 | 15 February 2016 |
| Preliminary review of requests by ICANN staff | 16 February 2016 | 4 March 2016 |
| SO/AC consultations at ICANN 55 (by request, during Constituents’ Day) | 5 March 2016 | 10 March 2016 |
| Final assessments and recommendations by ICANN staff | 15 March 2016 | 31 March 2016 |
| ICANN Board Review and approval at April Board meeting | 1 April 2016 |
15 December 2015 marks the launch of the FY17 SO-AC Community Additional Budget Request process. As you know, this process pertains to a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities that are not already included in the recurring ICANN budget.
Important Documents and Resources
FY17 SO/AC Additional Budget Requests - Finance wikipage (Please note what is new to the process)
In preparation for the submission, please review the following documents:
- FY17 Community Special Budget requests process description and timeline FY17 Community Additional Budget Request Process.pdf
- Principles that govern ICANN’s request assessment work Principles of SO-AC Additional Budget Requests (vFY17-2015).pdf
- FY17 template request form FY17 Community Requests Template.docx
