Following is a summary of the major initiatives and proposals under consideration by WT B.
This list is not necessarily exhaustive. WT members should add additional proposals.
__________________________________
•Regional Liaisons •RALO Comparison Page •Migration to Confluence •Translation and Interpretation processes. •Technology Review Schedule
ALS Confluence Pages can be their own web presence and act as a nexus for information exchange. Posterous - Diplo Foundation -- is an excellent educational opportunity – I know Wolf has more information about this, including a wonderful book that he brought with him to Cartegena to share. Multilingual orientation – Thank you Sebastien for recommending to list tools for orientation in regional languages. We ask our community (not just ICANN IT) to provide information and tools in their languages New Members – We are looking forward to welcoming new members with new ideas. Our regional liaisons will be happy to speak with you.
Established Regional Liaisons: “Comparison of RALO Participation/Membership Rules” – available as a wiki document AND a Google document Rec. 3: Ensuring unimpeded flow of information between the ALS-RALO-ALAC structure is vital for the success of education (task 4.1), engagement (task 4.2), and outreach, (task.4.3) as well as recruitment. Rec. 4: Educating and engaging the ALSes should be an immediate priority; compliance should be a longer-term goal. Rec. 7: Collaborative Tools; Alac should be allowed to make its own choices of communication and other collaborative tools to best meet its needs. – In choosing these tools, ALAC should take into account budgetary constraints and the technologies already used in other parts of the ICANN Community. Note: The implementation of all or most tasks under Recommendation 7 need to be a joint effort between At-Large and ICANN Rec. 9: ICANN should strengthen its translation and interpretation processes. --------------------------------------------- Accomplishments •Regional Liaisons have been elected to bring information to and from the RALOS •Comparison Page of RALO Participation Membership Rules has been established •Migration to Confluence •Recommendations to ICANN have been made re: strengthening its translation and interpretation processes. •Set a technology review schedule: We agreed that under rec 7. it makes sense to review available technologies on a set-18-month schedule
At-Large ImprovementsWT B - OverviewR3, R4, R7 & R9
Thursday, December 9, 2010Co-chairs: Annalisa Roger, NARALO
Fouad Bajwa, APRALOWT B
Accomplishments (partial list)R3, R4, R7 & R9•Regional Liaisons
•RALO Comparison Page
•Migration to Confluence
•Translation and Interpretation processes.
•Technology Review ScheduleEducation and Outreach-
learningDiplo Foundation and EUROSSIG style workshops and
-
GuidesPodcasts and Continued development of Introductory
-Suggest ICANN Orientation Course and Prototype
-ALS Confluence Pages for all ALS’s
-Multi-lingual orientation
Outreach --multiple mechanisms-Regional Showcases at ICANN
-
ICANN support (Adobe Room +) to ALAC – then to RALO’s
ALS Incubation Idea for individual members – NARALO ModelMeeting Support
Permanent Technology Orientation Task Force- Mobile device compatibility- Web 2.0 integration e.g, Posterous & Twitter on ConfluenceWT B __________________________________
Rec 3: Remove any obstacles in ALS-RALO-ALAC structure
•ALS Survey identified relevant obstacles, such as in information flow •WT recommending new communication/collaboration tools, incl. Confluence (ALAC rollout complete), Posterous, & iEtherPad •Own Confluence page for each ALS as two-way means of information exchange •Improved ALS Representative Starter Kit soon to be available
•Instruction package for ALSes on communication/collaboration tools WT is recommending
Rec 4: ALS education and engagement
•ICANN’s E-Learning Web Page up & running •Series of At-Large and RALO Brochures completed •Partnerships with outside education groups, incl. DiploFoundation
Make existing material easier to locate; form partnerships with identified educational groups
Rec 7: ALAC should choose its own communication/collaboration tools
•Selection and review processplanned and being implemented •Periodic review on 18-month cycle under consideration
•Review further tools; decide on appropriate review cycle; create training materials for ALSes; involve ICANN IT
Rec 9: ICANN should strengthen its translation/interpretation tools
•New Translation Policy to be introduced in 2-3 months •New translation tools being reviewed
•Identify improved translation tools; encourage RALOs to develop own translation policies
