Page History

Staff, under the direction of At-Large leadership, has already begun to rework the website and Wiki to ensure that our “Policy Advice” pages are accurate and understandable. This will continue as volunteer and staff resources allow. We will also ensure that as documents are published, the classification of the document is clear.

1. Nov 2018 convene analysis and review of issue and status of improvements to date micro-team with staff allocated, penholders for this issue <insert link to wiki page> and ARIWG member volunteers as desired.
2. Identify the specifics of processes and practices used to date.
3. Identification of opportunities for process improvement or modification
4. Development of proposal for reenvisioning any processes and practices to be discussed by ALAC / At-Large and those utilising ALAC advice.
5. Documentation process renewal proposal as agreed and prioritised developed into a project plan. Noting which milestones are intended to be reached by Dec 2019, and what is to be undertaken under review and continuous improvement planning.

To the extent allowed by ICANN’s mission and available funding, members of At-Large and the At-Large organizations will continue to, and potentially increase, our involvement
with other I* organizations as a method for increasing the visibility of At-Large, exploring areas for mutual collaboration and for attracting additional At-Large volunteers.

At-Large will continue to work closely with GSE Staff to contribute to regional outreach plans and to encourage participation in a cross-community, cross-organizational fashion.

The ALAC Technology Taskforce regularly reviews various communications tools with the aim of improving At-Large participation. The At-Large Community is very diverse and the selection of any new tools must accommodate this diversity. We will also need to continue to investigate how we can overcome the lack of affordable communications for many of our participants and future participants.

The ALAC will proceed with its plans as approved by the Board, pending appropriate funding. As with all At-Large activities, there will be an increased focus on tracking and metrics.

As noted in Issue 5, the ALAC supports such external activity to the extent that funding is available and it coincides with ICANN’s mission. Increases in such funding would be appreciated, but in light of the FY19 draft budget, we are now in a mode of trying to minimize impact of the proposed cuts to such activities.

At-Large Staff working with relevant departments to develop a single location which will point to travel funding opportunities and documentation of what resources were ultimately distributed, to the extent supported by those ICANN entities providing funding and reports.

(MH) Collaboration and coordination with Issue Teams #5, #12,and #15 which are also to do with Outreach, will be required

• The priorities of the CROP funding initiative has direct impact on the number and types of events we are underwritten to participate. Need assurances on the quantity of sponsored trips to properly plan the year events
• Approval of RALO strategic plans and the subsequent waiting period for staff approval directly impacts some trips that could occur shortly after approval
• Clear and open communication on the GSE activities so that RALO's can participate

• Secure and adequate ICANN funding for Outreach and Engagement
• An integrated calendar of ICANN events and meetings to coincide with RALO activities

It is the understanding of the ALAC that At-Large may only be funded from ICANN operational funds.

As noted previously, subject to available funding, we do look for opportunities to explain At-Large and attract new participants at non-ICANN events. When opportunities have arisen where funds are available to bring a targeted group to an ICANN meeting with a good potential for future involvement, we have done so.

(MH) Collaboration and coordination with Issue Teams #5, #12,and #13 which are also to do with Outreach, will be required