Actions: 

• 16 Sep 2015: 
  
  • ATLAS II IT to identify the recommendations that require ongoing efforts (i.e. the recommendations that cannot have the 'completed' status, per se) and single them out in a separate category 

Notes: 

Input from Technology Taskforce: 

Evaluated Caption First which offers an Adobe Connect plugin for live scribing on the Joint Accessibility WG/ Technology Taskforce meeting 2014-09-08. See ATLAS II 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, French and Portuguese for LACRALO monthly calls
  • English, French for AFRALO calls.
  • English, French for NARALO calls. 
  • English, Chinese for APRALO 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 which At-Large staff posts on the meeting's wiki page.
• 23 May 2016 
  
  • Captioning pilot project has been ongoing, providing services in calls in FY16 and will continue in FY17 
  • The turnaround of translation deliverables from language service has been very fast 
  • RALO calls provide interpretations (e.g. LACRALO call has FR, ES, and PT; APRALO has ZH; AFRALO has FR) 
  • Providing language capability has become a core in ICANN engagement and reflected in the budget allocation 

Input from Accessibility: 

• 16 Sep 2015 
  
  • There has been serious efforts across ICANN to improve accessibly
  • It is not At-Large's call to complete this recommendation; the completion of this recommendation depends on ICANN Staff's efforts in following this recommendation in improving accessibility  
  • There has been a short-term pilot program for captioning/live transcribing. It is part of the ICANN wide cross community activity (not a CCWG) and has its workspace to provide updates: Cross Community Committee on Accessibility Home. The At-Large Captioning Pilot Project has been working with ICANN IT and language services to implement this pilot program; the completion of this program also largely depends on ICANN Staff's efforts. If this pilot succeeds, captioning and live transcribing shall be provided in ICANN on an ongoing basis. There are many items to be done for this program and the work is far from completion. More information about the project: https://community.icann.org/x/rgAnAw 
  • Some of the ATLAS II recommendations require ongoing efforts (cannot have the 'completed' status, per se) and should be singled out in a separate category 

Actions: 

• 02 Sep 2015: 
  • Olivier Crepin-Leblond to send the ICANN Board Chairman and ask whether they require any further info on REC 11 and how ICANN has been acting on this recommendation. Olivier Crepin-Leblond will ask ALAC Chair's permission first. 
    
• 19 Oct 2015: 
  
  • At-Large Staff to ask Chris Gift's team re the implementation of this rec 

Notes:

• ICANN can meet it's strategic goals for inclusion and diversity through the implementation of services that embraces the various communities which have historically suffered from barriers of access.

• ICANN should use caption technology for all its calls, meetings and presentations. This tool not only makes all ICANN activities and programs accessible to Deaf, blind and low vision consumers, but also the English only calls to be translated into multiple languages courtesy of Google translate. Having the captions available in English also helps people in the ICANN community whose first language is not English as most people can read English even if they can not speak or understand it.

• Captioning technology review for conference calls (joint work between the two taskforces): https://community.icann.org/x/8xvxAg
• Prioritization from the primary objectives for the taskforce – including an identification of the key short, medium and long term opportunities: https://community.icann.org/x/EcXhAg

• The discussion has been furthered with key ICANN staff during the Accessibility Working Group meeting during ICANN 51: https://community.icann.org/x/kxvxAg

• 02 Sep 2015: From At-Large side, this recommendation has been completed. Its status depends on the progress on the ICANN Staff side. 

Input from Technology Taskforce: 

• (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 which was approved by ICANN.
• 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. The TTF has reviewed and documented these applications at the Translation Tools wiki page.
• 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.
• 23 May 2016 
  
  • Corresponds to Rec 10 

Actions: 

• 24 Sep 2015: 
  
  • Social Media WG assignees of this Rec to do the reporting 
• 23 May 2016 
  
  • Dev Anand Teelucksingh to work with Ariel Liang to install twitter integration in SLACK and to document how it was done 

Notes: 

• 05 Oct 2015: 
  • The objective of social media is to share information about At-Large and encourage target audience to engage with the community 
  • Slack can be a better alternative tool for group chat
• 18 Oct 2015 (update from the GSE, slides)
  
  • Note on slide:  ICANN is sensitive to this issue but this topic could be considered outside of ICANN’s technical remit. It would be helpful to hear more from At-Large on this recommendation.
• 19 May 2016
  
  • TTF has looked into various tools as alternatives to mainstream social media tools. For example, slack can be used to curate/publish social media content blocked in certain regions. Testing of slack is yet to be done. 

Input from Social Media Working Group: 

• Review the social media platforms blocked in certain countries/regions (e.g.http://citizenlab.org/) & alternative platforms local to those countries/regions 
• Assignees (Beran Dondeh Gillen, Bukola Fawole, Murray McKercher, Glenn McKnight) to research alternative social media platforms in countries that block Facebook, Twitter, and/or YouTube & report back to the group via mailing list and future WG call
• Assignees to to contact the citizen lab and find out previous research on this subject
• Glenn McKnight to follow up with the other assignees on this Rec 
• Ariel Liang & Murray McKercherto explore ICANN's Wechat account 
• 24 Sep 2015: 
  
  • ICANN has launched Wechat and YouKu accounts to reach audience in mainland China 
  • Slack can separate conversations based on topics via hashtags and do search of the messages globally. Slack is a good alternative tool for internal communications of the community, especially At-Large. Skype has various challenges, as it can easily loose chat history. Slack has a great mechanism for retaining chat history. It also has various add-ons/integration with other tools. 
    
    

Input from Technology Taskforce: 

• 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.
• 10 Dec 2015:
  • TTF has a meeting with David Goulet, Tor developer, and explored social media/communications channels used in regions that block certain mainstream platforms 
• 23 May 2016:
  
  • ICANN has implemented alternative chat services, such as SLACK, which has the capability to curate tweets and feeds from various social media channels 
  • ICANN Comms has developed Wechat, Weibo, YouKu to reach the Chinese public that cannot access Facebook, Twitter, etc. 

Actions: 

05 Oct 2015:

• Capacity Building WG and Technology Taskforce to work with ICANN IT to make the webinar recordings easy to replay and share 

Notes: 

30 Sep 2015: 

• There are a number of existing capacity building webinars, both At-Large wide and RALO specific 
• Outreach & Engagement SC has been looking into such activities and efforts for engagement; Ideas for Engagement Strategies wiki page has been set up; the SC will discuss this issue in ICANN 54 
• Capacity building should be more than online webinars. We should access RALOs and human capital for doing policy work and outreach. We should have some tools to engage membership and help them get involved. Staff should help hold more sessions to get more information about the inactive ALSes and learn about their interests. We need to adopt a gradual and systematic approach to engage the new and inactive ALSes. 
• Judith Hellerstein and Glenn McKnight have identified a large group of ALSes who haven't attended any NARALO calls. They will reach out to them and conduct easy-flowing sessions to find out why they are inactive and give them an opportunity to ask questions. 
• ALSes are often overwhelmed by emails and don't understand how to navigate the information and ways to get involved. To help ALSes understand ways to navigate through the overwhelming amount of information in At-Large can be one of the capacity building topics. 

05 Oct 2015:

• It has been recognized that mentorship of new ALS representatives and the development of short tutorials (e.g. How to use Adobe Connect) can help dress he on-boarding challenges
• Capacity building webinars can be leveraged to develop those tutorial/mentoring initiatives and educate newcomers and inactive At-Large members 
• Pre-training of ALSes is important, including how to use Adobe Connect, etc., and they need to know that participate in teleconferences and webinars via AC is part of the ALS participation expectation 

18 Oct 2015 ( update from the GSE, slides) 

• Note on Slide: The work of the Stakeholder Journey sub team within the CEP team can help address this recommendation.
• Chris Mondini on the Stakeholder Journey program: 
  • It looks at the challenge of getting more volunteers, but also more active volunteers 
  • At a very high-level, GSE has looked at some data, to look at where people come from, where they may get stuck, what some of their challenges are. They looked at the structures across ICANN, because each structure approaches this question slightly differently, and each structure and constituency has slightly different needs. They have made some high-level observations about how we might attract people, by looking first at what their question areas are, what their issue areas are. 
  • They have looked at some tools that they can provide to help community volunteers be partners in doing that outreach. GSE will solicit feedback from the community, especially the volunteers who have a passion for bringing on the next generation to having a succession plan, so that the sustainability of ICANN in this community is assured. 
• Sally Costerton on the work of Community Engagement:
  • There has been coordination team inside the ICANN, co-chaired by Sally Costerton and David Olive, composed of senior staff that face the ICANN community. The team includes the Policy Team, the Engagement Team, the Communications Team, which is led by Duncan Burns, the Digital Engagement Team, led by Chris Gift, and the Meetings Team, led by Nick Tomasso. There are two frequent guests, which is DPRD, led by Nora Abusitta, and she has the Fellows Program under her remit in DPRD, which is a very important element of the Stakeholder Journey Program. Another guest is Cyrus Namazi, who leads engagement for the GDD Team. The goal is to try to make sure we have a much more holistic view about how ICANN, as a staffing organization, can maximize the resources at our disposal. 
  • This team is to tackle some of these difficult challenges that the community faces as it matures and grows, such as the great deal of exhaustion in the volunteer community. You see a lot of the same faces popping up in different Working Groups, and while that’s great in some ways, but it’s also not sustainable. 
  • It is also about providing people with tools, it’s translations – it’s access questions, generally, whether that be money to get on a plane, or stay in a hotel, whether it’s language tools that allow you to participate in an even way, whether it’s improving the search on the website so that it’s a more friendly environment. 
  • how do we take a holistic look, as staff, at all of the money that ICANN spends on volunteer support, community participation? Whichever word you want to use. Because we tend to view it in quite narrow pockets. There are particulate processes to apply for travel funding or special support work and so forth. 
  • but we will be able to do so in due course – it’s getting a real sense of, “How much in total, out of the overall ICANN Budget, do we have at our disposal? And how can we make sure that we match that, as effectively as possible, to this goal?”
  •  we’re trying to take what you’re talking about, as a more strategic view of it, to say, “Are there other ways we could do things differently that would make it easier for unpaid participants in the community to have a more equal participation?” 
• Siranush Vardanyan: GSE team should be connected to the Outreach calendars used in RALOs to see At-Large activities and explore collaboration opportunities.
• Rafid Fatani: How do we maintain the old, but also bring in the new and keep them in? One of that is actually maintaining and allowing them to grow within various leadership positions. I, in the ALAC, think personally that we have a problem with this. 
• Sebastien Bachollet: I think it’s good to have new people come in, but they need to be received, they need to be accompanied, they need to be sustained, supported, received in good conditions. Because if that’s not the case, they are going to leave and go somewhere else.
  
• Sally Costerton: GSE will have regular calls with the ALAC Outreach & Engagement Sub-Committee.  I’d be very happy to make myself and some of my team available, once, or regularly, to join that call. This may give us more time to get into more detail about some of the tactical things we need to do. 

23 May 2016:

• There have been efforts to make conference recordings more accessible, such as MP4 conversion of meeting recordings to be uploaded to YouTube 
• There has been significant progress in this recommendation, such as the revamp of At-Large website, implementation of captioning services, additional interpretation, LACRALO mailing lists, etc. 

Actions:  

• Chairs of these 3 WGs (Dev Anand Teelucksingh, Tijani Ben Jemaa, Leon Sanchez, Glenn McKnight, Judith Hellerstein) to discuss how to tackle this task

• Capacity Building Working Group to work with Social Media Working Group & Technology Taskforce to assess the knowledge management and the policy development system

• ALAC to follow-up depending on the status update on the SOs/ACs Chairs & ICANN Leadership Meeting on Friday 6 Feb 2015 
• Social Media WG to help generate the taxonomy of the policy categories and make sure the taxonomy are more accessible to newcomers/curious outsiders
• ICANN Board to help make the policy development process easily shareable via social media
• 24 Sep 2015: 
  
  • After the ICANN 54 meeting, SMWG to hold a call and review the taxonomy used on the new At-Large website and help review and revise the topic/organization tags on statements and news articles 
• 05 Oct 2015: 
  
  • Ariel Liang to circulate the taxonomy list on the SMWG mailing list 
• 23 May 2016:
  
  • Mark Segall to explore eXo platform and report back to TTF in terms of testing results

Notes: 

• A project that overhauls ICANN’s information management system
• The Technology Taskforce Chair is following up with relevant ICANN Staff 
• 09 Sep 2015: 

  • Technology Taskforce has discussed the tool Kavi with ICANN IT, as Kavi was tried out in GNSO. ICANN IT is unlikely to continue promoting or implementing Kavi as it does not appear to sustain the needs of GNSO (e.g. not mobile friendly, do not support multilingual work). Nonetheless, the discussion on Kavi is still useful for At-Large to understand the user profile of policy management process tools and to guide At-Large on understanding what users want/don't want. 

  • Technology Taskforce has recommended a few other solutions to IT that can be considered as alternative tools, and will explore other tools in the future. 
• 05 Oct 2015: 
  
  • Knowledge management is still a challenge in the community. Keeping track of action items and what is happening in the Working Group is difficult.  
  • Confluence has capability to include consolidated task lists for certain wiki parent pages and their respective child pages. 
  • To keep a concise summary / table of hot topics and key activities in working groups may help address knowledge management issue 
  • Staff-created weekly policy update (that includes the activities and topics in the working groups) can serve as a template for such summary/table - explore potential to publish them on the new At-Large website? 
  • Need to build an one-stop shop of working group/RALO/liaison reports: https://community.icann.org/x/XwCB 

Input from Social Media: 

• 24 Sep 2015: SMWG to give feedback on the taxonomy used on the new At-Large website (tagging of news articles and policy advice Statements). 
• 19 May 2016: TTF has tested an open source software *** (Dev to provide the link)

Input from Technology Taskforce: 

• The At-Large Website Redesign has been completed - 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. The new website can be viewed at https://atlarge.icann.org/. The website redesign effort has significantly reduced the manual work in publicizing public comment work in At-Large, and this has been demonstrated during ICANN 53. 
• 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; conference call will likely happen in the end of September 2015. 

• Suggested Implementation Strategy

  • Assemble cross sectoral technology team to determine the full scope of the project 
  • Allocate adequate budget for completion
  • Create realistic timelines
  • Roll out a beta test with assigned volunteers in each sector to test and provide feedback 
  • Need to provide a recommendation of best practices
• 21 Sep 2015: 
  

  • Reviewed and evaluated LACNIC's customized policy development process and web tools in the teleconference: https://community.icann.org/display/atlarge/At-Large+Technology+Taskforce+2015-09-21

• 23 May 2016:

  • TTF will investigate eXo Platform: https://www.exoplatform.com/. It can create different work rooms to facilitate policy discussions and communications, etc. Learn more about eXo here: 

  • Comment from Carlton Samuels: what we need is a competent librarian to do the curating.  THis morning for example there was a call on the Subsequent Procedures WG for output from all communities that pronounced on the new GTLD process.
  • A librarian has been hired in ICANN to look into issues mentioned in the recommendation. So far the librarian has been working on the taxonomy and search strategy with the language service team. 
• 12 Sep 2016:
  
  • A team to test the eXo platform has been formed: https://community.icann.org/x/pAC4Aw 

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?

Notes: 

• 30 Sep 2015: 
  
  • TTF has worked on a template on Confluence for RALO Secretariat Report 
  • The news page in the revamped At-Large website will incorporate template that can be potentially used for reporting purposes; login for community members will be worked on after the Beta site launch 
• 05 Oct 2015: 
  • RALO secretariats may be able to use a form-based template to provide updates via the new At-Large website 
    
    

Input from Social Media Working Group: 

• RALO and Liaison reports seem to fulfill the request of this recommendation
• Explore options of generating a template (e.g. online form, google doc) for RALOs, Liaisons, and Working Groups so that they can file reports in an efficient manner
• Follow up with RALO secretariats on the status of the RALO report templates
• 24 Sep 2015: 
  
  • RALO Secretariat reports should use a template that is easy for social media sharing. 
  • Community members have made an effort to create that template. 
  • New At-Large website redesign will also incorporate that Secretariat Report template design in the future; the reports can be tagged in order to show in the news feed of future RALO pages. 

Input from Technology Taskforce: 

• 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
• 23 May 2016
  • A template has been created in wiki for RALO secretariats to fill out and track topics of interest. The template is not viewable to the public at the moment 
  • The new At-Large website has features to automatically organize public comment proceedings and news articles based on policy topics, but this only partially satisfies the recommendation 
    
    

Actions:

• 24 Nov 2015
  
  • Social Media WG and Technology Taskforce to continue their investigation of better tools 
• 09 Mar 2016
  
  • RALO leaders to use the policy section on the new website and provide feedback on how it could help ALSes to participate in the policy advice development process 
• 18 Feb 2016
  
  • Technology Taskforce to discuss Rec 31 during its next teleconference 
• 20 May 2016 
  
  • After social media WG and TTF complete testing of lumio, liquidfeedback, trello, and other tools, report on the testing results and mark this recommendation complete 
• 23 May 2016 
  
  • Jimmy Schulz and Dev Anand Teelucksingh to organize a special purpose session to demo/test kialo.com; Jimmy will invite a rep from kialo.com to do the demo. 

Notes: 

• Fatima Cambronero to email Dev Anand Teelucksingh about the tool for Statement drafting collaboration
• 24 Nov 2015 (secretariat meeting) 
  • SLACK is one of the tools for investigation 
  • Technology Taskforce will provide a summary of their investigation so far and what does and what does to be published on a wiki
• 21 Jan 2016 (secretariat meeting)
  
  • Potential public comment period needs to be made aware to RALOs, as public comment period may be brief and RALO members cannot engage in time; ALAC members need to closely collaborate with RALO members with regard to this process; capacity building of public comment proceedings is also needed 
  • ALS Criteria and Expectations Taskforce has been working on figuring out a suitable way that ALAC and Staff to feed ALSes information of policy. RALOs need to take the initiative to confirm interests in obtaining such information. 
  • It may be useful for subject matter experts to provide an overview of public comment, instead of just stating the procedure related matters, during RALO calls. 
  • LACRALO has worked with GSE and ALAC members and invited speakers to educate ALSes about certain public comment topics during teleconferences. 
• 09 Mar 2016  (secretariat meeting - ICANN55) 
  
  • Siranush Vardanyan: The Document Development Program may encourage ALSes to participate in policy development and to participate in public comment process and comment on those policy developments we need. Whenever there is a policy up for comment, we would need some one-page, simple language, non-technical, just explanation – what is this policy, how it can influence to end users – to be sent to us and to share with our ALSs and encourage them to come and comment. 
  • Glenn McKnight: TTF has been testing different tools, such as SLACK and Buffer. Besides these, TTF is addressing accessibility issues concerning people who are using Linux or people who have problems using Flash; Judith Hellerstein: TTF also works to make sure which tools meet the standards of W3C on web accessibility.
  • Ariel Liang: the new At-Large website includes beginner-friendly information about public comment and ALAC advice development process; this may be helpful for the ALS to participate in the policy activities 
  • Alberto Soto: Short public comment period is a challenge. Longer public comment period, such as the one on the Final Report Recommendations of the Geographic Regions Review Working Group, allows RALOs to identify penholders and draft response, as well as to invite subject matter expert to provide further information on the topic. 
• 12 May 2016
  
  • Technology Taskforce has been exploring different tools (e.g. Lumio) and will continue this ongoing effort, as the mandate of the TTF is to evaluate and review Information and Communication Technologies that can help the ICANN At-Large Community (including the At-Large Advisory Committee (ALAC)) better able to accomplish their role in ICANN activities.
  • Crowdsourcing is a non-starter as it is not the way that At-Large works. 
• 23 May 2016: 
  
  • Lumio has been tested but it does not satisfy this recommendation 
  • Several discussion tools need to be tested, such as Liquid Feedback, Trello, SLACK, etc. 
  • Jimmy Schulz has recommended kialo.com and he has been using it for discussions. He has also used Liquid Feedback and Ahocracy (https://adhocracy.de/) but they are not very intuitive compared to kialo and have a lot more features than needed. 

Input from Social Media Working Group: 

• Dev Anand Teelucksingh to list the tools investigated:https://community.icann.org/x/QaM0Aw
• 24 Sep 2015: 
  
  • The challenge for social media is that can we have a conversation on policy via social media? Current policy conversation is taking place on Skype, mailing list, and calls/meetings. 
  • It would be useful to monitor different social networks to see what has been said about certain policy topics/reports. 
  • ICANN should task certain staff members in following social media conversations about policy topics. 
  • This recommendation is also related to Outreach & Engagement Subcommittee. It talks how to get people engaged in public comment periods, etc. 
  • Social Media Working Group can ask question to get people involved in public comment. 
  • Break down the questions and encourage people to answer questions in small bits. 
  • Use particular hashtag to group the conversations around certain policy topic. 
  • Task an At-Large Working Group to experiment with this method and ask/answer questions about policy topics. 

Input from Technology Taskforce: 

• 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
• 08 Aug 2016: A guest speaker demonstrated Kialo (https://www.kialo.com/) to the TTF and showcased its capability that allows a group of people to discuss and debate on various issues. TTF has concluded that Kialo may be good for the Community to form broader positions on potential Statements in response to ICANN public comment proceedings than doing detailed document editing work. TTF would suggest the ALAC to trial this tool and see how it would be used to form the arguments in ALAC Statements. 

Action Items:

23 May 2016:  

• Ariel Liang to follow up with Chris Gift on this recommendation 

Input from Chris Gift on 08 Aug 2016 :

• There are two work efforts, not mutually exclusive, working on open data. 
• The first is an effort by David Conrad to examine what DNS data we have available for public sharing. This would include data from our Registry Service Level Monitoring system (our DNS-wide SLA monitoring) as well as authoritative machine readable gTLD lists (from IANA).
• The second effort is led by Ashwin Rangan, who’s looking at operational data that can be shared. This would included KPI, but also IT server up time data (that is safe to share). 
• Both efforts are in their infancy and no dates or status are ready to share yet. However, there is a growing recognition that Open Data is an important part of transparency and as an organization we think it behoves us to move in that direction

Input from Technology Taskforce: 

• 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 Handbookhttp://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