At-Large Technology Taskforce 2014 -01-07

At-Large Technology Taskforce 07 January 2014

Date: Tuesday, 07 January 2014

Time: 1500 - 1600 UTC (for the time in various timezones click here)

Meeting Number: AL.TTF/MT.1014/1

How do I participate in this meeting? Please join the LUCID meeting room (url in email) for this meeting

Action Items: EN

Recording: EN

Transcript: EN

AC Chat Transcript : EN

Adobe Connect Meeting Room: http://icann.adobeconnect.com/atlargetechtaskforce/ (will not be used for this meeting)

To connect to the LUCID meeting room, please click on the following link and log in: https://icann.lucidmeetings.com/meetings

Participants: Dev Anand Teelucksingh, Bill Thanis, Gordon Chillcott

Guest speaker: David Closson, Josh Baulch, Reed Quinn

Apologies: Olivier Crépin-Leblond

Staff: Silvia Vivanco, Nathalie Peregrine

Call management: Nathalie Peregrine

Meeting Agenda

1.0 WELCOME AND ROLL CALL

Presenter: Nathalie Peregrine

Duration: 3 minutes

2.0 REVIEW OF ACTION ITEMS

https://community.icann.org/display/atlarge/At-Large+Technology+Taskforce+14+October+2013+-+Action+Items

Presenter: Dev Anand Teelucksingh

Duration: 5 minutes

3.0 COLLOBORATING WITH ICANN IT STAFF REGARDING ADOBE CONNECT

work with ICANN IT staff to troubleshoot reports made by several At-Large users that Adobe Connect on Linux doesn't work.
collaborating on documenting key Adobe Connect features that many users may not be aware of.

Duration: 15 minutes

4.0 IDEAS FOR IMPROVING THE ORGANISATION OF AT-LARGE CONTENT (AT-LARGE WORKING GROUPS)

https://community.icann.org/display/atlarge/Tools+used+to+organise+content+created+by+At-Large+Working+Groups

https://community.icann.org/display/atlarge/Issues+noted+regarding+content+of+At-Large+Working+Groups+and+recommendations

Next steps:

having a separate installation of Confluence to experiment with and test ideas

Scope of Confluence installation:

Given the ongoing and extensive use of the wiki by At-Large, testing different approaches to how the content is organised is difficult. For example, trying new themes or trying plugins without fear of "breaking" the existing wiki. So the scope would be

for a separate confluence instance, completely independent of the confluence installation in use by ICANN At-Large (and other ICANN communities)
having a copy of the ALAC space (everything under https://community.icann.org/pages/viewpage.action?pageId=2265510 ) to be able to manipulate and reorganise
having admin access to be able to install (and uninstall) plugins and/or themes

Some Confluence plugins of interest:

Transform Confluence into a blog platform - there is a space called At-Large Social Media Posts https://community.icann.org/display/alsocialmedia/At-Large+Social+Media+Posts where the RSS from the blog feed (a challenge to get working) is autoposted to At-Large Social Media accounts : this looks much more refined http://www.refinedwiki.com/en/display/products/blog-plugin-confluence.aspx
Send email to page: https://marketplace.atlassian.com/plugins/biz.artemissoftware.plugins.confluence.send-email-to-page - since the emails from ALAC announce are currently re-posted manually on the At-Large Social Media Posts space, emails from At-Large Staff could be bcced to this blog to remove this manual step. Also easier to copy emails from the various mailing lists to wiki comments in order to group the discussion on one page, rather than manually copy/paste
Zen Foundation: can we create great looking landing pages to make content enticing for non-active and members of the public finding the page? https://marketplace.atlassian.com/plugins/com.zenfoundation
Table Filter: - the ability to filter tables as you type looks promising. https://marketplace.atlassian.com/plugins/com.stiltsoft.confluence.plugin.tablefilter.tablefilter

Duration: 10 minutes

5.0 MACHINE TRANSLATION

5.1 MACHINE TRANSLATION OF WEBSITE TOOLS

Duration: 8 minutes

5.2 MACHINE TRANSLATION OF MAILING LISTS

See https://dl.dropboxusercontent.com/u/877052/LACRALO-translation-email-issues/discussion-of-LACRALO-mailing-list-issues.txt for a recap of issues to be resolved