Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloak

NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG

Issue #7

Lead: Javier Rua-Jovet


Excessive amounts of At-Large Community time spent on process and procedure at expense of ALAC’s mandated responsibilities to produce policy advice and coordinate outreach and engagement activities. Too many internal working groups are a distraction.
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
Prioritization1:1:1 (Low resource needs : Low risk ; 1st priority group)
ARIWG comments

(MH) Collaboration advised due to relationship of this issue with Item issue #1 - Quality vs quantity of policy advice

(NA) Would be handy to have a one stop shop document  as a wiki page that serve as tool to document all the working groups and their members and process used. This page, will be also good for branching out to the working space or the different resources. 

Status of improvement effort / staff lead
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation
  1. That the ALAC has developed goals and objectives for 2019
  2. That there is a staff member designated to regularly update Working group wikis and the Working Group Website page
  3. That the CPWG wiki page regularly updates issues discussed and progress statements
Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?As mentioned above in the general comments, this should be lead by ALAC, and there is also a carpentry work that must be done by staff.  
Anticipated resource requirements (FTEs, tools)

The expected amount of carpentry by staff is very low, just maintain the groups up to date, We should expect less than 10% of one person per month, or 0,1 FTE, if any.

Expected budget implicationsSo far, this 0,1 FTE, no need for additional software, since it is on the wiki site,

Proposed implementation steps:

  1. Clarify ALAC focus areas and objectives for 2019
  2. Establish or re-establish working groups that will deal with specific time-framed issues as required (under the management of key stream leaders of Organisation, Policy and O&E streams.
  3. Ensure that staff establish appropriate and updated wiki pages to record WG objectives as well as details or meetings and outcomes of each WG meeting
  4. Ensure that staff record the Working Groups that are currently active on the At-Large website with links to each WG wiki page
  5. Establish a wiki page for the Consolidated Policy Group, to record topics covered at each meeting and a progress statement on each (including the EPDP WG)
  6. Establish a wiki page for the O&E WG and the outcomes of their monthly meetings (including ATLASIII WGs)
  7. Establish a wiki page for the Organisational WGs, and any relevant updates (including ARIWG).

  8. An annual review of the groups and participants should be taken. A half session at the AGM should be dedicated to evaluate the current groups, and its participants. Also, 30 days prior to this date an email should be sent to all At-Large to join this working groups. At this time any “no longer needed” group should be stopped, and just kept the records.

  9. Change the RoP 14.3.2 to include clear rules of termination of the working groups

  10. A person from staff should be clearly indicated as the one in charge to maintain the groups up to date in the wiki site

Continuous Improvement(s)
Metrics
How long will it take to implement this plan?

...