Post ATLAS II items for TTF

No.	Recommendation	Recipient 1	Recipient 2	Recipient 3	Thematic Group Source	Assignees	Notes	Status
10	The next evolution of language services must adopt further extension of live scribing for all meetings and generally extend the current interpretation and translation processes and make translation available in a timely manner.						Evaluated Caption First which offers an Adobe Connect plugin for live scribing on the Joint Accessibility WG/ Technology Taskforce meeting 2014-09-08. See ATLAS2 Recommendation 11 for screenshots and overview. ICANN Language Services provides interpretation for At-Large F2F meetings in English, Spanish and French English, Spanish, French and Russian for ALAC monthly conference calls. English, Spanish and Portuguese for LACRALO monthly calls English, French for AFRALO calls For At-Large WGs, interpretation is provided on request from more than 3 persons attending a call. ICANN Language Services transcribes audio recordings of ALAC/At-Large meetings and provides a transcript in less than a week.
11	ICANN must implement a range of services to facilitate access according to various criteria (gender; cultural diversity) and user needs (disabilities, etc…).	ICANN Board	ICANN Staff		TG2	Accessibility Technology Task Force	See ATLAS2 Recommendation 11 (As per Rec 10) ICANN Language Services provides interpretation for for ALAC/At-Large F2F meetings and ALAC and for some RALO conference calls. However, they do not as of yet provide support for people with disabilities and special needs during working groups or conference calls. Evaluated Caption First which offers an Adobe Connect plugin for live scribing on two calls (as per Rec 10) A special budget request to conduct a pilot program to live caption 6 meetings/calls a month has been submitted to the FBSC The TTF also evaluated “Craptions to Captions”, an open source tool for captioning videos. See Technology Taskforce meeting 2015-01-26 Also, the TTF looked at Amara, www.amara.org , a subtitle editor that makes it easy to caption and translate videos. Amara also hosts volunteer localization & accessibility communities. The TTF notes the progress of machine translation tools such as Skype Translator Preview and the already available Google Translate mobile app. (added May 18) Skype Translator Preview for Windows 8/Phone (which allows for machine transcribing of voice and IM) will be reviewed by the TTF on Technology Taskforce meeting 2015-05-18 The TTF is working with ICANN IT staff to have a new version of the machine translation tools used for the LACRALO English and Spanish mailing lists. See https://community.icann.org/x/z4VZAg Also beginning the process for testing captioning of all videos. Glenn McKnight will be demoing some of these at the next TTF call. )
26	Current policy management processes within ICANN are insufficient. ICANN must implement a workable Policy Management Process System, available for use across the SO/ACs, in order to: enhance Knowledge Management, improve the effectiveness of all ICANN volunteer communities, improve cross-community policy-specific activity, enhance policy development metrics, facilitate multilingual engagement, create a taxonomy of policy categories, provide policy development history as an aid for newcomers.	ICANN Board	ICANN Staff (Policy)		TG5	Social Media, Technology Task Force Capacity Building	What do we want in a Policy Management Process System? To quickly find historical information on a policy issue For example, find policy history on “new gTLDs” and get a report in chronological order. Such searches could be further refined (e.g show history in past 4 years) or show the submissions made by a particular AC/SO on a policy issue. Such searches could be visualized using a timeline (e.g http://codyhouse.co/gem/vertical-timeline/). A system would have the policy history stored in a manner to allow for such queries. *To subscribe to policy updates/notifications by interest* For a person who has a keen interest in certain policy issues (e.g IDNs), persons should be able to subscribe to receive updates on specific policy issues with links to where the discussions are happening for that AC/SO. This is where a taxonomy of policy categories to be defined for past, current and future/upcoming policies. Furthermore, a policy system could track past user interactions, so that if a person commented on a particular policy issue (e.g WHOIS), they could be notified of new, related policy issues for their review. Track deadlines for responding to policy comments With multiple policy comment periods happening simultaneously at different stages, a system should update a calendar or other system for the AC/SO to track and manage deadlines. The ability to read policy issues and updates in your language Comment Periods on Policies posted for review are posted in English with translated policy documents being uploaded at a later time. Persons should be able to subscribe to notifications when policies are available in their language to review. Having the policy review process more accessible to mobile users. With more and more users using mobile devices, the policy review process should be made accessible to such users to engage in the policy process. Reduce the manual duplication to disseminate information. AC/SOs expend a lot of effort to manually copying and pasting text in order to disseminate policy information to the communities and to the wider public (wiki pages, emails, sharing on social media). A system should offer sharing mechanisms so that persons wanting to get the word out can do so more easily. What do you want in a Policy Management Process System? ---------------------------------------------- The At-Large Website Redesign is underway - part of the website design attempts to provide a policy background on policy issues as well as to create a taxonomy of policy categories and highlight policy metrics. A mockup of the Website can be viewed at https://new-atlarge.herokuapp.com/ The TTF will be reviewing the Policy Development Processes at the Regional Internet Registries (RIRs) to see what could be adapted for At-Large Policy Development Chairs of these 3 WGs to discuss how to tackle this task. See Post ATLAS II Implementation - Recommendation 26	Follow-up, depending on the status update on the SOs/ACs Chairs & ICANN Leadership Meeting on Friday 6 Feb
17	ICANN needs to be sensitive to the fact that social media are blocked in certain countries and, in conjunction with technical bodies, promote credible alternatives	ICANN GSE Staff	ICANN CIIO		TG2	Technology Task Force ; Social Media	At-Large Workshop on “TOR and alternative naming mechanisms to the DNS” held at ICANN Singapore 2014 https://community.icann.org/x/7CPRAg TTF has looked at Group Chat services (https://community.icann.org/x/Hr3hAg) such as Slack, HipChat and Hall. At-Large Social Media WG is researching alternative social media platforms where traditional ones are blocked. While the TTF considered listing several platforms/services that allow access to blocked services, it was felt that even listing such services could be construed as endorsing breaking of national laws, irrespective of whether we (global At-Large) think such laws/restrictions are unjust.
29	The ALAC should implement an automated system for tracking topics of interest currently being discussed among the various RALOs, and accessible by everyone.	ALAC			TG5	Capacity Building Technology Task Force Social Media	The TTF looking to syndicate RALO topics across all RALO wiki pages using the Confluence’s wiki capabilities. Wiki addons such as Confluence Questions (http://bit.ly/1EUah6O) & group chat applications may allow for such crowdsourcing of topic discussions ; TTF to continue evaluation To ensure regular updates from RALO chairs and secretariats in a form suitable for sharing, a template to standardise the information collected from RALOs is being developed
31	ICANN and the ALAC should investigate the use of simple tools and methods to facilitate participation in public comments, and the use of crowdsourcing.	ALAC;	ICANN GSE Staff		TG5	Social Media Technology Task Force RALO Chairs: Aziz Hilali, Siranush Vardanyan, Wolf Ludwig, Alberto Soto, Garth Bruen , @evan Leibovtich	The TTF is to review tools such as Liquid Feedback ( http://liquidfeedback.org/ ) The TTF is currently evaluating Loomio (https://www.loomio.org/) an online tool for collaborative decision-making
39	ICANN should encourage “open data” best practices that foster re-use of the information by any third party.	ICANN Staff			TG5	Technology Task Force	A significant amount of information produced by ICANN and At-Large over the years is already public however, its not stored in an organised way, (wikis, websites) making information hard to locate and to re-use. The TTF is reviewing how best to implement open data standards. Some of the resources on Open Data include: The Open Data Handbook http://opendatahandbook.org/ Open Data Guide (http://opendata.guide/) Open Data Foundation (http://opendatafoundation.org/) (older notes - To the extent that ICANN has data sets that do not contain personal identifying information these should be open and we can work with those groups to advise them on best practices. Most examples focus on Open Government and much of the data of businesses and non profits are not Open or accessible. Research on similar examples did to be done so we can assess whether ICANN is typical or laggards to the access to information http://gcn.com/articles/2014/02/07/open-data-best-practices.aspx Abide to the Digital Accountability and Transparency Act Resource http://opendatafoundation.org )

Note: The recommendations highlighted in yellow target the ICANN Board.

Content

Space Tools