ALAC Improvements Taskforce Proposal Tables: ABRIDGED VERSION
The following items have been removed from these abridged tables but can still be found in the full versions (located at https://community.icann.org/x/HgTPAQ):
- “WT proposal details”: Supporting details pertaining to some WT proposals in the main tables; where such details have been removed, a “See details” link has been placed.
- Tasks addressed”: Column listing specific tasks addressed by each WT proposal in the main tables.
- “Tasks not addressed”: Separate tables showing tasks not addressed by the WTs for various reasons.
Recommendation 1: The section of the ICANN Bylaws that deals with the ALAC should be changed to reflect its continuing purpose within the ICANN structure. This continuing purpose has four key elements:
- Providing advice on policy;
- Providing input into ICANN operations and structure;
- As part of ICANN’s accountability mechanisms; and
- As an organizing mechanism for some of ICANN’s outreach.
| The WTs propose that the ALAC… | Recs addressed | Status |Submit to the Board the following revision to ICANN Bylaws XI.2.4.a, drafted in collaboration with Legal:
See details in Full Version of table at https://community.icann.org/x/HgTPAQ.
1,10, 11
Completed
Submit to the Board the following revisions to ICANN Bylaws XI.2.4.j, drafted in collaboration with Legal:
See details in Full Version of table at https://community.icann.org/x/HgTPAQ.
1, 11
Completed
Form a Working Group (WG) to conduct a complete review of the ALAC’s Rules of Procedure.
See details in Full Version of table at https://community.icann.org/x/HgTPAQ.
1
In progress
Recommendation 3: The ALS-RALO-ALAC structure of At-Large should remain in place for now.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Establish a Working Group (WG) to ensure that the At-Large information already available is organized properly and easily accessible by end users. |
3 |
Establishment of WG to be put on hold pending completion of ICANN website revamp and At-Large wiki portal for outreach |
Introduce to the ALSes selected information-dissemination, communication and collaboration tools (such as Posterous, Twitter Twibes, mobile-device compatibility) and provide training. |
3, 7 |
In progress |
Promote further use of the At-Large Calendar to the ALSes. |
3 |
In progress |
Create and distribute a brief orientation/instruction package about the information-dissemination, communication and collaboration tools introduced to the ALSes. (TheALS Starter Kit already includes some of this information.) |
3 |
ALS Starter Kits is completed. Beginner's Guide on Participating in At-Large to be completed by CR Meeting) |
Recommendation 4: Educating and engaging the ALSes should be an immediate priority; compliance should be a longer-term goal.
The WTs propose that the ALAC… |
Recs addressed |
Status |
|
Establish the ICANN Academy, an annual training program for new At-Large ALS members, modeled after aspects of the ICANN Fellowship and Diplo Foundation. |
4 |
In progress |
|
Establish an engagement program for existing At-Large ALS members, to be conducted year-round and modeled after certain aspects of the Diplo Foundation (specifically, this is the At-Large Capacity Building Program to begin in Dakar in Oct 2011). |
4 |
In progress |
|
Make available to each ALS a Confluence page for two-way communication with ICANN (for example, see AFRALO ALS Confluence pages). |
4 |
Completed |
|
Make available to each ALS the use of an Adobe Connect Room for meetings, etc. (for example, see AFRALO ALS Adobe Connect Room). |
4 |
Completed |
|
Request that selected At-Large members be funded to attend non-ICANN meetings (e.g., the IGF, the Consumer Electronics Show (CES), etc.). |
4 |
In progress |
|
Request that the ALAC be invited and funded to participate in all outreach programs launched by ICANN (including the New gTLD Program outreach road show). |
4 |
Must begin |
|
Invite potential At-Large members from countries currently without any ALS to a series of outreach teleconferences aimed at reaching the goal of having at least one ALS in every country. |
4 |
Must begin |
|
Recommend that each RALO start an individual member program. |
4 |
In progress |
|
Continue collaborating with ICANN Communications on Beginner’s Guides devoted to topics relevant to At-Large. |
4 |
In progress |
|
Recommend to the RALOs that they formalize their outreach/“inreach” role in whatever way each finds appropriate (e.g., by including in their Rules of Procedure). |
4 |
In progress |
|
Increase significantly the ALAC’s creation of “inreach” materials aimed at leadership engagement and development throughout At-Large (including brochures, radio programs, podcasts, webinars, and online videos). |
4 |
In progress |
|
Create job descriptions for ALAC members, liaisons and other At-Large leaders that include qualification requirements, responsibilities and objective criteria for performance evaluation. |
4 |
In progress |
|
Create and implement a transparent sanctions process for nonperformance of ALAC, RALO and ALS members. |
4 |
In progress |
|
Create, in collaboration with ICANN’s Nominating Committee (NomCom), a process for the midterm replacement both of NomCom appointments to the ALAC and of ALAC appointments to the NomCom. |
4 |
Must begin |
Recommendation 5: The ALAC should develop strategic and operational planning processes (including performance criteria and cost information) as part of ICANN’s planning process.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Ratify the strategic planning process reflected in the flowchart titled “Figure C-1: Proposed At-Large Strategic Planning Process” (see Appendix 2), by which the ALAC could contribute to ICANN’s strategic planning. |
5 |
Must begin |
Ratify the operational and financial planning process reflected in the flowchart titled “Figure C-3: Proposed At-Large Operational and Financial Planning Process” (see Appendix 2), by which the ALAC could contribute to ICANN’s operational and financial planning. |
5 |
Must begin |
Review and amend the ALAC’s strategic planning process yearly, in line with annual amendments to ICANN’s overall strategic planning process. |
5 |
In progress |
Conduct periodic “SWOT” (strengths, weaknesses, opportunities and threats) analyses of the At-Large strategic planning process, in conjunction with the RALOs (as WT C did), and compare the results of these analyses to identify areas that have improved or deteriorated. |
5 |
In progress |
Articulate ALAC’s and At-Large’s vision and mission. |
5 |
In progress |
Use appropriate metrics to ensure that the ALSes are diverse, effective and well-informed. |
5 |
In progress |
Initiate, develop and maintain an institutional knowledge management and retention system for At-Large. |
5 |
In progress |
Encourage the five RALOs to coordinate their outreach and “inreach” policies in order to facilitate the search for new skill sets needed within At-Large. |
5 |
In progress |
Continue actively pursuing At-Large growth, for the overall benefit of ICANN. |
5 |
In progress |
In attempting to get the ALAC’s outreach projects funded, emphasize their role not only as a strategic resource benefiting the ALAC and RALOs but also as part of a wider ICANN legitimacy process. |
5 |
In progress |
Acknowledge and encourage a continuation of the better collaboration between the ALAC and ICANN’s Finance staff seen in preparing the FY2012 Budget. |
5 |
Completed |
Conduct periodic “SWOT” (strengths, weaknesses, opportunities and threats) analyses of the At-Large operational and financial planning process, in conjunction with the RALOs (as WT C did), and compare the results of these analyses to identify areas that have improved or deteriorated. |
5 |
In progress |
Formalize the process by which the ALAC collects operational demands from the RALOs and includes them in its operational plans. |
5 |
In progress |
Clearly estimate and document the time required for the ALAC’s operational processes (e.g., responding to a call for Public Comments) and use these estimates to formalize its operational processes. |
5 |
In progress |
Continue requesting face-to-face funded general assemblies (GAs) for each RALO every three years and an At-Large Summit. |
5 |
In progress |
Continue to monitor its level of needed staff support and ICANN’s commitment to and progress in filling open staff positions. |
5 |
In progress |
Continue to encourage ICANN to prioritize and increase funding for outreach activities. |
5 |
In progress |
Continue to assist the RALOs in completing their annual ICANN requests for funding, as needed, in terms of writing, packaging and advocacy. |
5, 6 |
In progress |
Recommendation 6: More effort needs to be put into developing accurate cost models for At-Large activities.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Encourage the same high level of input into ICANN’s annual financial planning from the ALSes and RALOs as was demonstrated in the planning for FY2012. |
6 |
In progress |
Continue to encourage ICANN to increase its level of detailed disclosure regarding the process of financing the ALAC and At-Large. |
6 |
In progress |
Continue to monitor the accommodations given to At-Large representatives at ICANN Meetings to ensure they are equal to those of other funded communities. |
6 |
In progress |
Continue to assist the RALOs in completing their annual ICANN requests for funding, as needed, in terms of writing, packaging and advocacy. |
5, 6 |
In progress |
Recommendation 7: The ALAC should be allowed to make its own choices of communication and other collaborative tools to best meet its needs – taking into account budgetary constraints and the technologies already used in other parts of the ICANN community.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Introduce to the ALSes selected information-dissemination, communication and collaboration tools (such as Posterous, Twitter Twibes, mobile-device compatibility) and provide training. |
3, 7 |
In progress |
Conduct a survey of ALSes regarding communication & collaboration tools |
7 |
Completed |
Establish a Technology Task Force (TTF) of community members that would periodically review the appropriateness of available technology, help train RALOs/ALSes in new technologies introduced and possibly staff a help desk. |
7 |
Must begin |
Recommendation 8: The Public Comment period should remain 30 days, except in the case of special circumstances, for which ALAC may request an extension to 45 days.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Ratify the process reflected in the flowchart titled “Figure D-1: How the ALAC Should Request an Extension to a Public Comment Period” (see Appendix 2), by which the ALAC could request that a Public Comment period be extended. |
8, 13 |
In progress |
Request that extensions to Public Comment periods be allowed of any length up to 30 additional days (see “A” on Figure D-1 in Appendix 2). |
8, 13 |
In progress |
Request that any extension request to a Public Comment period be granted or denied within 24 hours (see “B” on Figure D-1 in Appendix 2). |
8, 13 |
In progress |
Recommend the establishment of a Policy Scheduling Team (PST), consisting of ICANN staff, to coordinate the opening of Public Comment periods. |
8, 13 |
Must begin |
Establish a standing committee, the ALAC/At-Large Policy Review Committee (PRC), responsible for advising the ALAC of actions needed regarding upcoming PCS policy issues, as well as policy issues not on the PCS but of At-Large interest. |
8, 13 |
Must begin |
Recommendation 9: ICANN should strengthen its translation and interpretation processes.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Build into At-Large’s consideration of ICANN policy issues (open Policy Forums) more and earlier translation of relevant materials. |
9 |
In progress |
Review ICANN’s new Language Services Policy (once available) and request that At-Large staff do the same, focusing on At-Large needs, particularly related to ICANN policy issues. |
9 |
Must begin |
*Recommendation 10: *The ALAC, as the representative body for At-Large, is the primary organizational home for the voice and concerns of the individual Internet user in ICANN processes (although ICANN's multi-stakeholder model provides the opportunity for individual users to choose to participate in many other ways in the ICANN process).
The WTs propose that the ALAC… |
Recs addressed |
Status |
Submit to the Board the following revision to ICANN Bylaws XI.2.4.a, drafted in collaboration with Legal: |
1,10, 11 |
Completed |
Recommendation 11: A clear statement is needed from the Board that recognizes the place of At-Large as the primary organizational home for individual Internet users and that clarifies the relationship between the ALAC and the User Home currently being developed within the GNSO.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Submit to the Board the following revision to ICANN Bylaws XI.2.4.a, drafted in collaboration with Legal: |
1,10, 11 |
Completed |
Submit to the Board the following revisions to ICANN Bylaws XI.2.4.j, drafted in collaboration with Legal: |
1, 11 |
Completed |
Recommendation 12: ICANN should develop a mechanism that allows bodies recognized as representing consumer interests to be heard at critical points in key decisions and to provide input into policy processes. (As this recommendation affects recruitment across two communities, development of an integrated outreach program for this stakeholder group will be developed centrally. Upon completion, it will be provided to At-Large for review and comment.)
The WTs propose that the ALAC… |
Recs addressed |
Status |
Create and maintain a consumer outreach document for use by At-Large in its outreach efforts aimed at getting consumer organizations involved in ICANN. |
12 |
In progress |
Recommendation 13: The ALAC should strive to provide policy advice on any issues that affect individual Internet users. To this end, the following should be strengthened:
- The processes within ALAC for developing and providing policy advice;
- The processes within the SOs for requesting input from the ALAC on policy issues; and
- The processes within the SOs, ACs, and Board for providing ALAC with feedback about how its policy advice has been used.
The WTs propose that the ALAC… |
Recs addressed |
Status |
Ratify the process reflected in the flowchart titled “Figure D-1: How the ALAC Should Request an Extension to a Public Comment Period” (see Appendix 2), by which the ALAC could request that a Public Comment period be extended. |
8, 13 |
In progress |
Request that extensions to Public Comment periods be allowed of any length up to 30 additional days (see “A” on Figure D-1 in Appendix 2). |
8, 13 |
In progress |
Request that any extension request to a Public Comment period be granted or denied within 24 hours (see “B” on Figure D-1 in Appendix 2). |
8, 13 |
In progress |
Recommend the establishment of a Policy Scheduling Team (PST), consisting of ICANN staff, to coordinate the opening of Public Comment periods. |
8, 13 |
Must begin |
Establish a standing committee, the ALAC/At-Large Policy Review Committee (PRC), responsible for advising the ALAC of actions needed regarding upcoming PCS policy issues, as well as policy issues not on the PCS but of At-Large interest. |
8, 13 |
Must begin |
Ratify the process reflected in the flowchart titled “ALAC/At-Large Policy Advice Development (PAD) Process” (shown in Figures D-3, D-4 and D-5 in Appendix 2), by which the ALAC could systematically respond to Public Comment periods. |
13 |
In progress |
Request that all Public Comment period Web listings and related documentation be required to be available in at least English, French and Spanish from the start of every Public Comment period. |
13 |
Must begin |
Strongly encourage the RALOs and ALSes to give increased input into the ASO’s Policy Development Process (PDP), via the ASO’s Regional Internet Registries (RIRs). |
13 |
In progress |
