Independent Examiner’s Final Recommendation | ALAC should consider the adoption and use of a single Slack-like online communication platform. An instant messaging-cum-team workspace (FOSS) alternative to replace Skype/Wiki/website/mailing list. |
Issue Identified | There are a multitude of communications channels used by At Large. This has led to fractured and undocumented communications. |
Does ALAC Support Recommendation? | Support with reservations The ALAC supports the intent of this recommendation to ensure that we use appropriate communications tools within At-Large. The ALAC the support of IT-based tools for ICANN typically requires the support of ICANN IT staff and the selection of products and whether they are FOSS or proprietary is not the sole choice of the ALAC. |
If Not, Please Provide Reasoning. | Parts of the At-Large community, particularly those who primarily use mobile access, believe that the continued use of e-mail is essential. |
If ALAC Does Not Support Recommendation, Does It Suggest an Alternative Recommendation? If so, please provide a suggested alternative Recommendation. | Not Applicable |
Prioritization | Low Priority |
At-Large Comments | The ALAC has a WG which looks at how technology can enhance its effectiveness. Examples are the use of machine translation to address communications in one of its regions with significant language barriers, and the Captioning project that has just been integrated into the core ICANN budget and has been very well received by other parts of the ICANN community. |
Possible Dependencies | We note however that we are subject to a number of constraints. The ALAC notes that it cannot simply adopt a new communications vehicle without the support (both budget and technical) of ICANN IT Services, and At-Large cannot unilaterally start using tools that are not supported by ICANN. We cannot depend on volunteer technical support and so must rely on ICANN IT, which adds an additional level of vetting and bureaucracy. The ALAC also notes that in parts of its communities, cost and availability of bandwidth is problematic as is local government restrictions on the uses of certain platforms. We have community members all around the world, some with very low and/or very expensive bandwidth (and ICANN will not subsidize such access for volunteers). Often ONLY the older tools such as e-mail and Skype chat will function effectively or cost-effectively. Furthermore, we have community members in locations where their national governments block access to certain services and tools. |
Who Will Implement? | ICANN IT |
Resource Requirements | Budget and technical support from ICANN IT |
Budget Effects impact? | |
Implementation Timeline | |
Proposed Implementation Steps |
AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
4 Comments
Alan Greenberg
My thoughts
Status: Accept with reservations
Comment: The ALAC has a WG which looks at how technology can enhance its effectiveness. Examples are the use of machine translation to address communications in one of its regions with significant language barriers, and the Captioning project that has just been integrated into the core ICANN budget and has been very well received by other parts of the ICANN community.
The ALAC notes that it cannot simply adopt a new communications vehicle without the support (both budget and technical) of ICANN IT Services, and also notes that in parts of its communities, cost and availability of bandwidth is problematic as is local government restrictions on the uses of certain platforms. Moreover parts of the At-Large community, particularly those who primarily use mobile access, beleive that the continued use of e-mail is essential.
Glenn McKnight
Status Accept
Comment
SLACK has two versions. The paid version retains the communication and categories and the free one doesn't , caution on the selection of tools. A group within TTF has expressed interest in creating this Open Source tool contact Billy Einkamerer billy@assemble.co.za
Ariel Liang
ALAC comment in the ALAC Statement on the At-Large Review Draft Report
==
The ALAC supports the intent of this recommendation to ensure that we use appropriate communications tools within At-Large. We note however that we are subject to a number of constraints. At-Large cannot unilaterally start using tools that are not supported by ICANN. We cannot depend on volunteer technical support and so must rely on ICANN IT, which adds an additional level of vetting and bureaucracy.
We have community members all around the world, some with very low and/or very expensive bandwidth (and ICANN will not subsidize such access for volunteers). Often ONLY the older tools such as e-mail and Skype chat will function effectively or cost-effectively.
Furthermore, we have community members in locations where their national governments block access to certain services and tools.
Vanda Scartezini
our technology WG shall help to suggest best tools as has always done. we deal with quite different environments and difficulties for people to reach information and some diversity is demanded to attend regional differences. we also have the Skype group that is "cross ralos" and open to other groups... communications is top priority but I disagree that we shall concentrate everything in "one fits all"
very low priority