Issue 7 Dashboard and Progress Chart

Final Proposal as approved by the Board

The ALAC has begun to review our WGs, ensuring that the ones we have are active and relevant. We have also started the process to revamp our WG web and Wiki presence to ensure that all WGs are properly represented and documented. Groups no longer active will be segregated, but still documented for historical purposes

Prioritization

1:1:1 (Low resource needs : Low risk : 1st priority)

ARIWG comments

Comments relating to this issue focused on the  website listing Working Groups that had been retired and were no longer active due to their irrelevance to what was important to At-Large, thus giving outsiders a false impression of what was happening within At-Large.  A recommendation was made for a one-stop shop or dashboard to direct potential participants to active working groups within one of the three work streams, through a link which would indicate the purpose of the working group and some brief context, its intended timeframe, and information about how to join up.

Status of improvement effort. / Staff lead

Staff Leads: Heidi Ullrich with Evin Erdoğdu.

To date, changes have already been initiated, through the  development of the Organigram where the CPWG (Consolidated Policy Working Group) provides an overarching umbrella group for discussing ICANN policies that impact Internet end-users. The CPWG involves a growing number of committed Policy contributors who work together on the preparation of ALAC policy advice.  The only Working Group that reports to the CPWG and seeks guidance on inputs to the discussion, is the EPDP. Outreach and Engagement, on the other hand has a specific set of working groups that prepare capacity building and outreach activities for both within and outside of ICANN. The Organisational stream works similarly with its ARIWG and ATLASIII working groups.

Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation

The At-Large Leadership Team must establish goals and objectives for each of the three streams of At-Large activity, so that there is direction and opportunity for member participation, engagement and leadership..

Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?

The staff will be required to address website and wiki space issues and to  provide appropriate support for the Workstream teams to carry out their roles effectively. The ALAC Chair and the Leadership team will ensure that goals and objectives are established and will add their support for the workstreams to achieve their goals.

Anticipated resource requirements (FTEs, tools)

Current At-Large staff support is anticipated to be able to work with community leaders to implement this issue.

Expected budget implications

No additional resource requirements are expected.

Proposed implementation steps:

1. Staff, with input from At-Large leadership, will ensure that the At-Large website clearly identifies classes of workgroups and specifically identifies those for which general community participation is encouraged.

2. Membership of WGs will be reviewed annually, and the wiki and web pages updated.

Metrics

Resolution of perception issues with existing Web site(s) and Wiki within a 6 month time frame.

How long will it take to implement this plan?

6 months*

*Variation here may be required to fit with IT Program of changes to Web site schedule.

Report due to the Board - 23 June

Report drafts should be ready by May 23 with sub-tasks completed

2 May - meeting of Working Group team (Ricardo, Maureen, Heidi)

• WGs to be reorganised according to their association with one of the 3 Organigram groups (Policy, O&E and Org)
• MH to provide list of groups under each umbrella group and send to Evin to reorganise accordingly on the WG home page
• Non-operational WGs will be added to the Mailing List Only list
• Each working group to be updated with purpose, guidelines for involvement and membership
• Working Group Members to be reconfirmed annually after the AGM - leadership of the WG to be selected by the members at the first meeting -
• (for O&E and Organisational WGs) Presentation of the annual report of the previous WG Leadership at this first meeting
• Any changes to the WG processes are to be reflected in the Rules of Procedure - Alan to be consulted to ensure that changes are recorded appropriately 

• Staff to work with Maureen to reorgnise the WGs under the three priority areas - Policy, Org and O&E
• Staff to work with Maureen and Ricardo to review RoPs on closure of WGs.
• Priority WGs: Policy, O&E, finance, tech
• Discussion of dropping “C” in “CPWG”, will remain CPWG for time being. CPWG description should mention that the “consolidated” nature of CPWG means that it’s ALL policy, in addition to new gTLDs from the legacy WGs.
• Each year at AGM - update WGs, all WGs review their chairs.
• WGs to have an Annual Report.

• RH, MH, HU & EE met during ICANN64 to discuss WG updates.