Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloak

NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG

Issue #5

Lead: Tijani Ben Jemaa


Uneven contribution of At-Large to a coordinated ICANN strategy for ‘Outreach and Engagement’. Missed opportunities for coordination with other constituencies and ICANN staff.
Final Proposal as approved by the Board

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.

Prioritization2.2.1 (Medium needs; medium risk; #1 priority group)
ARIWG comments

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

(MH) before we go further with our current O&E and capacity building programmes, have we really assessed the effectiveness of our current approaches to ensure that our programmes are actually achieving the proposed objectives and impacting the target groups that we want them to reach?

(AC) Agree with Maureen’s comment on metrics. A detailed rubric should be in place.

(AC) What is the objective of the Capacity Building Program?

What metrics are we using to ensure this.. therefore this item has to be linked to the Metrics item #16 as well

Status of improvement effort / staff lead
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation


Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?
Anticipated resource requirements (FTEs, tools)
Expected budget implications

Proposed implementation steps:


Continuous Improvement(s)
Metrics
How long will it take to implement this plan?

...

Cloak

NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG

Issue #10

Lead: Dev Anand Teelucksingh


There are a multitude of communications channels used by At Large. This has led to fractured and undocumented communications.
Final Proposal as approved by the Board

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.

Prioritization3.3.1. (High resource needs; High risk; #1 priority)
ARIWG comments

(MH) This item also highlights how we can use what communication channels are available to disseminate important messages out to the wider public as well as the At-Large Community.

Some collaboration with the social media items (#8 & #9) but also with the task teams working on areas #5, #12. #13 and #15 would be appropriate, to enhance the work that is being done in O&E

As well as some metrics to assess the effectiveness of any communication channels that we implement.

(Satish) Some RALOs bring out their periodic newsletters, which are useful in providing information (including policy updates and progress of initiatives) to their community. I'd like to suggest an At-Large-wide newsletter that can periodically update the At-Large community as a whole, besides also informing other AC/SOs on the activities of ALAC.

(AC) A trimester newsletter (depending on resources) could be used as an O&E tool, as well as inform the At-Large community.

Status of improvement effort / staff lead
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation
Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?
Anticipated resource requirements (FTEs, tools)
Expected budget implications

Proposed implementation steps:


Continuous Improvement(s)
Metrics
How long will it take to implement this plan?

...