SCOPE  

At-Large Technology Taskforce Working Group


OBSERVATIONS AND ISSUES 

  • Despite 60 members we don't have good cross RALO participation
  • Lack of Vice-Chair for missing RALO locations
  • Lack of clear strategic plan for the working group
  • Lack of acknowledgement by ALAC and ATLARGE of the reports and achievements

RECOMMENDATIONS For  Website 

Move the recommendations section out of the main page and just have a link

Add a link to our achievements over time

Add a link to our Strategic Plan

ACHIEVEMENTS

  • List of achievements
  • A  visual timeline
  • Include  infographics 
    • history
    • achievements
    • vetting processes
  • same  https://www.easel.ly/

Example  of  a infographic



Social Media  Strategy 

Do we have one?  Provide links

Facebook

Twitter 


PROMOTION




RECOMMENDATIONS

  • Make Intro paragraph simple and engaging
  • Put the "Work & Projects" at the forefront and provide some of the featured projects in list form with links to that project, if possible. 
  • Incorporate the "Achievements" section mentioned above after this. 
  • Have a "Get involved" section, include the contact details in this section, maybe Social Media as well?
  • Consolidate the Meetings, Monthly Reports, and maybe Action Items. Perhaps, that section could have three columns, with one column for each. 
  • Move "About" section to the bottom, right above members. If there are key points within the ALAC/At-Large Improvements Project Final Report that should be featured prominently, feature them in the intro paragraph. 

Below is a very rough reorganization of the current homepage, without incorporating all of the new elements suggested above. 

At-Large Technology Taskforce Working Group

The At-Large Technology Taskforce (TTF) evaluates and reviews different technologies and tools that can help the ICANN At-Large Community (including the At-Large Advisory Committee (ALAC) communicate, collaborate and accomplish their goals and objectives for ICANN activities. These tools range from chat tools, web conferencing tools, captioning to anything that will help Individual Internet users become active in the At-Large Community. Technology provides the tools that enable people to connect, collaborate, and work towards making the world more accessible, enabling the benefits of the Internet to be available to all.

Work & Projects



Some of our recent projects are:

See all TTF Projects

Get Involved


We welcome anyone who is interested in collaborating to find out how we can better meet the needs of ICANN At-Large to participate, suggest ideas, and be active members. We have recently opened up the group to other ICANN constituencies and look forward to working with all ICANN communities to solve common problems. 

To get involved please email ICANN At-Large Staff at staff@atlarge.icann.org or the current chairs of the TTF: Dev Anand Teelucksingh or Judith Hellerstein directly and join the mailing list

Contact


Staff Support Lead: Mario Aleman


Mail list: ttf@atlarge-lists.icann.org


To Subscribe to the mail list for this WG (or read the archives / manage your subscription) please visit https://mm.icann.org/mailman/listinfo/ttf

Meetings and Monthly Reports

Previous call: May 8, 2017

Meeting Archives - Monthly Reports


Action Items



About

The TTF was established as part of the recommendations coming from the ALAC/At-Large Improvements Project Final Report in June 2012. These recommendations include:

  • Under Recommendation 3 "ALS-RALO-ALAC structure to remain"
    • 3.1 - Introduce to the ALSes selected information, dissemination, communication and collaboration tools and provide training.
  • Under Recommendation 7 "Choice of communication and collaborative tools"
    • 7.1 Review of communication and collaboration needs considered unmet by ALSes and RALOs globally.

    • 7.1(a) - Introduce to the ALSes selected information, dissemination, communication and collaboration tools(such as Posterous, Twitter Twibes, mobile-device compatibility) and provide training.
    • 7.2 - Review of technologies used by At‐Large and across ICANN that could fill all or some of the 7.1 needs of the ALSes and RALOs
    • 7.2(a) - Establish a Technology Task Force (TTF) of community members that will periodically review the appropriateness of available technology, train RALOs/ALSes in new technologies, and possibly staff a help desk.
    • 7.3 - Review of available technologies not already used by At‐Large or elsewhere in ICANN that could fill the 7.1 needs of the ALSes and RALOs.

    • 7.4 - Create and conduct implementation plan for training ICANN's IT Support in the 7.3 technologies (and, as needed, in keeping IT Support current in 7.2 technologies).
    • 7.5 - Based on At‐Large's choice of the communication and collaboration tools to best fill its needs, make needed recommendations for use, or not, of these tools across ICANN.
    • 7.6 - Create and conduct implementation plan for the periodic identification of technologies, either newly introduced to the market or updated, that can better fill the 7.1 needs of the ALSes and RALOs than those technologies currently being used.


  • No labels

1 Comment

  1. Thanks for this, some thoughts:

    • Rather than one long table of the TTF members, making it difficult to sort, we should separate the table by RALO which should be easier to read.
    • In terms of promotion, we have the latest TTF presentation from ICANN59 which could showcase our current activities
    • A lot of confluence macros show a "content not rendered" when viewed on mobile devices, requiring a reload of the page, which is cumbersome. A redesign objective should be to make this load on mobile devices without having to reload. So we should test if using complex layouts using confluence's sections and columns would work, and if not, avoid. We can enclose content in divs and use css to style so perhaps this is an option. I note also that PDF embedded with the confluence macro would also give a "content not rendered" so a workaround would be to use an image which is linked to the PDF