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 #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. For example is there any way we can check how often Capacity building webinars are being accessed after their real-time presentation? Also if transcripts or recordings are being accessed by participants who cannot attend the meetings in real-time. Are their current formats relevant to what our target audiences need in order to be informed?

(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.


(NA) At-Large various communications tools are evolving and improving, but it is not about the different tools as much as how to activate a bottom-up community driven updates.  Giving the voice of the at-large community and interacting with them that what makes the platforms/tool a success.  

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 #11

Lead: Olivier Crepin Leblond


While broadly popular, Global ATLAS meetings every 5 years have been difficult to organize and short on effective results. More frequent regional meetings would be more effective in encouraging both policy input and outreach while familiarizing more of At Large with workings of ICANN.
Final Proposal as approved by the Board

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.

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

(MH) ATLASIII, ICANN66 Montreal, Canada in November 2019 will be dependent on the outcomes of this implementation plan. The Metrics Issue #16 also relates to this task.


(NA) For the approved Global ATLAS, make sure to have a tangible measurable objectives, that help recruit well engaged community members to potential newcomers who have the time to volunteer to at-large policy work.  To provide justifications to ATLAS meetings, is to have those attended the meeting did actually engaged.  Adding to avoid having ATLAS to be a replica of a talk show conference.

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?

...