Page History

...

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.

...

• 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

...

...

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

...

Also beginning the process for testing captioning of all videos. Glenn McKnight will be demoing some of these at the next TTF call.  )

...

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.

...

Social Media,

Technology Task Force

Capacity Building

What do we want in a Policy Management Process System?

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

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

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

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

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

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

7. What do you want in a Policy Management Process System?

    

----------------------------------------------

...

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

...

...

Technology Task Force ;
Social Media

...

Some platforms/services that allow access to blocked services include

• The Freenet Project
• Psiphon
• Lantern
• I2P Anonymous Network
• TorProject

...

...

• Capacity Building
• Technology Task Force
• Social Media

...

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

...

...

• 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

...

...

• Technology Task Force

...

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.  

...