Below, you will find each of the recommendations from the Final Report of the ALAC Review WG on ALAC Improvements that has been assigned to WT B. These are Recs. 3, 4, 7, and 9. And after each recommendation is a table listing the related tasks from the WT B At-Large Simplified Improvements Outline.
Please complete the tables (by first clicking “Edit” above). For each task, you must list either:
- One or more recommendations that WT B would like to propose to the ALAC in order to implement the task; or
- An explanation of why the task no longer requires WT B to make an implementation recommendation to the ALAC.
About your implementation recommendations:
- Include enough relevant information (details, links, etc.) in your recommendations to make them clear to the ALAC.
- For any task, you may enter one or more implementation recommendations (most tasks will likely get one recommendation).
- You may enter the same recommendation under more than one task (enter the recommendation or recommendations that most directly apply to each task).
About your explanations of why tasks no longer require implementation recommendations:
- Include enough relevant information (details, links, etc.) in your explanations to make them clear to the ALAC. These explanations – like the WT’s recommendations themselves – were discussed during the WT meetings.
About the tables themselves:
- Tables can be difficult to use/edit in Confluence. (If you have problems, please let Seth know.)
- Please confirm that links you’d like to embed in the tables’ text are actually active (actually work).
- The column widths should adjust as you type in them.
- Remember to click “Save” after you’ve edited the tables.
Main sources of information for use in filling out these tables:
- WT B San Francisco Presentation (March 2011) A and WT B San Francisco Presentation (March 2011) B
- WT B meeting minutes
- The notes, action items, etc. listed in WT B’s Simplified Improvements Outline.
_________________________________________
REC 3: The ALS-RALO-ALAC structure of At-Large should remain in place for the present.
Task # |
Task |
WT B recommends that the ALAC… |
This task no longer requires a recommendation from WT B because... |
3.1 |
Ensure existing structure does not present obstacles to community operation and development |
|
|
3.1.1 |
Review information flow between three tiers of At-Large structure (ALS-RALO-ALAC) to identify possible improvements to information dissemination |
|
|
3.1.2 |
Review information flow between the At-Large structure (ALS-RALO-ALAC) and individual Internet users/members of the ALSes to identify possible improvements to information dissemination |
|
|
3.1.3 |
Given results of 3.1.1 and 3.1.2, implement any useful improvements |
|
|
REC 4: Educating and engaging the ALSes should be an immediate priority; compliance should be a longer-term goal.
Task # |
Task |
WT B recommends that the ALAC… |
This task no longer requires a recommendation from WT B because... |
4.1 |
Education |
|
|
4.1.1 |
Develop high-level principles to guide development of an external education campaign |
|
|
4.1.2 |
After 4.1.1 principles are approved, daw up plan with specific deliverables consistent with these principles |
|
|
4.1.3 |
Once 4.1.2 plan is approved, implement plan |
|
|
4.1.4 |
Use any appropriate educational resources developed by Policy staff or elsewhere in ICANN to supplement At-Large plan |
|
|
4.2 |
Engagement |
|
|
4.2.1 |
Develop high-level principles to guide development of an internal engagement campaign |
|
|
4.2.2 |
Once 4.2.1 principles are approved, draw up plan with specific deliverables consistent with these principles |
|
|
4.2.3 |
Once 4.2.2 plan is approved, implement plan |
|
|
4.3 |
Outreach and recruitment |
|
|
4.3.1 |
Outreach and recruitment to increase At-Large community size and diversity |
|
|
4.3.1.1 |
Design an outreach and recruitment strategy for At-Large |
|
|
4.3.2 |
Outreach messaging about ICANN's activities to individual Internet users |
|
|
4.3.3 |
Design a process that ensures information about issues being dealt with by the ICANN community can be easily understood by individual Internet users. |
|
|
4.3.4 |
Recommend to RALOs that they formalize outreach/“inreach” role within their structures however each finds appropriate (e.g., by including the role in the RALO’s rules of procedure). |
|
|
4.4 |
Explore whether additional measures need be taken to involve individual Internet users in At-Large work, where they wish to contribute in their personal capacities |
|
|
4.5 |
Leadership engagement and development |
|
|
4.5.1 |
Create job descriptions for ALAC members, liaisons, and other leaders that include qualification requirements, responsibilities, and objective criteria to evaluate performance |
|
|
4.5.2 |
Create and implement a sanctions process for nonperformance |
|
|
4.5.3 |
4.5.2 sanctions process should make travel support unavailable to nonperforming ALAC leaders |
|
|
4.5.4 |
ALAC and the NomCom jointly to decide on process(es) for midterm replacement both of NomCom appointments to ALAC and of ALAC appointments to the NomCom, where required |
|
|
4.5.4.1 |
Implementation of 4.5.4 agreed-upon process(es) |
|
|
4.5.5 |
Present finalized results from 4.5.2, 4.5.3, and 4.5.4 for Board approval |
|
|
4.6 |
Compliance |
|
|
REC 7: 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.
Task # |
Task |
WT B recommends that the ALAC… |
This task no longer requires a recommendation from WT B because... |
7.1 |
Review of communication and collaboration needs considered unmet by ALSes and RALOs globally |
|
|
7.2 |
Review of technologies already 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.1 |
Consideration of effects of technologies identified in 7.2 on accessibility issues |
|
|
7.2.2 |
Cost/benefit analysis of expanding the use of the technologies identified in 7.2 to fill all or some of the needs of the ALSes and RALOs |
|
|
7.2.3 |
Create implementation plan for the expanded use, as needed, of certain technologies identified in 7.2 that meet ICANN's budgetary requirements |
|
|
7.2.4 |
Implement 7.2.3 plan |
|
|
7.3 |
Review of currently 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.3.1 |
Consideration of effects of technologies identified in 7.2 on accessibility issues |
|
|
7.3.2 |
Cost/benefit analysis of using the new technologies identified in 7.3 to fill all or some of the needs of the ALSes and RALOs |
|
|
7.3.3 |
Create implementation plan for use, as needed, of certain technologies identified in 7.2 that meet ICANN's budgetary requirements |
|
|
7.3.4 |
Implement 7.3.3 plan |
|
|
7.4 |
Create implementation plan for training ICANN's IT Support in the 7.3.2 technologies (and, as needed, in keeping IT Support current in 7.2.2 and 7.3.2 technologies) |
|
|
7.4.1 |
Implement 7.4 plan |
|
|
7.5 |
Based on At-Large's choice of communication and collaboration tools to best fill its needs, make recommendations for use, or not, of these tools across ICANN |
|
|
7.6 |
Create 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 |
|
|
7.6.1 |
Implement 7.6 plan |
|
|
REC 9: ICANN should strengthen its translation and interpretation processes.
Task # |
Task |
WT B recommends that the ALAC… |
This task no longer requires a recommendation from WT B because... |
9.1 |
Interim measures (near term) |
|
|
9.1.1 |
Propose any near-term modifications to processes necessary for increased policy engagement dependent upon availability of translations |
|
|
9.2 |
Adoption of Translation Policy |
|
|
9.2.1 |
Staff to review draft document and determine if additional modifications are necessary and if Board approval is necessary (versus implementation done directly as administrative matter) |
|
|
9.3 |
Implementation of Translation Policy |
|
|
