Decisions Reached | Action Items: Tracking Tool

ICANN org to propose a meeting cadence, to take place once every two weeks, aiming to avoid conflicts on Thursdays @19:00 UTC with other community calls (i.e. GNSO Council, etc.)

NomComRIWG and ICANN CEO will finish their discussion on transparency of ICANN org support of the NomCom; also address Recommendation 11 on line of responsibility and Recommendation 12 on Budgeting for the NomCom.

Rec 27:  Considering the discussion and the takeaways, ICANN Legal will review the proposed definition and engage with the NomComRIWG to discuss a way forward.

Rec 24:  ICANN org to provide to the RIWG consolidated feedback from the OEC and org on the Draft Standing Committee Charter for RIWG consideration.

Rec 10:  ICANN org to assist with gathering NomComRIWG documentation on: a) options/principles considered for rebalancing;  b) community consultation and input on the RIWG proposal for addressing Rec. 10.

75

RIWG will draft Operating Standards for the Standing Committee to complement the draft charter. 

RIWG will consider adding language to the Standing Committee draft charter to convey "guard rails" for the work of the Standing Committee, and to add language regarding its accountability and transparency. 

Rec. 12: find out from ICANN finance department what process they follow to alert community chairs that it’s time to start the new budget cycle. 

Inquire about the contracting/procurement of recruitment consultants.

Recs. 11, 12: Send questions as an email request to office of the CEO and Finance Department, and ask for a meeting in January, potentially during one of the NomComRIWG meetings

NomCom Standing Committee Charter:

• III. 1. Tom to add more sentences to this.

• VI. ICANN org to follow-up with ICANN org legal department on question on “the members of the Standing Committee will select a conveyor at the Annual Meeting to lead the committee, rotating every year.

• VI. NomComRIWG to define somewhere the role of the Convenor, add a footnote

• VIII. Tom to wordsmith text.

Tom Barrett/ NomComRIWG/ ICANN Staff

NomComRIWG to review of all the recommendations to see if we have to adjust any dates or metrics for the year-end report.

ICANN org to add metrics from the detailed implementation plan to the Progress and Implementation status report

Rec. 10: NomComRIWG to review narrative and make sure it explains why doing a holistic review prior to this bylaw update is not the right approach

Recs. 11, 12: NomComRIWG to prepare questions for two future calls – one with Göran, one with Finance Department.

Bylaws update: Section 8.3: NomComRIWG to include transition article (section 27 of the Bylaws) as part of the redline they give to the OEC.

Plan an outreach effort to the community for January 2021, including recommendation 27.

Rec. 15: ICANN org/NomCom Support Staff to specifically reach out to ALAC, ccNSO, to help on building a job description. 

Rec. 15: Jay Sudowski to take the lead on seeing whether GNSO could provide an outline 

Rec. 11: NomCom Support Staff reach out and find out who are the appropriate parties that the NomCom should contact or address your communication to, to schedule a meeting. Potentially identify whether they would be happy to participate in one of the upcoming plenary calls. 

ICANN org to submit draft of the second progress and implementation progress report by December 1 , incorporating today’s updates on completion dates

Update all dates to 2021 throughout the document

Rec. 21 – 26 – update dates to 2021

Rec. 20 – update dates to 2021

Rec. 19 – create link for timeline for group to access offline

Rec. 18 – publish detailed timeline – change dates to 2021

Rec. 16 – publish timeline and input for receiving bodies

Rec. 6 – update due dates to Q1 – 2021

ICANN org to submit draft of the second progress and implementation progress report by December 1 , incorporating today’s updates on completion dates

Rec. 12 – change dates to 2021

1. Change first item to Q1 – 2021
2. Quarters stay the same for the rest – change year to 2021

Look at the 3 recommendations (2, 3, and 4) – ICANN Org - provide a suggested list of courses for onboarding, pertinent to the recommendations 2, 3, 4

Invite Legal to provide input on bylaws update and charter for our next meeting

Circulate charter with Legal

Send out letter to GNSO SGs/Cs chairs.

Review and provide input on the draft replies to the IPC, BC, ISPCP, RySG: GDOC [docs.google.com]

Review all the roles and responsibilities listed for the standing committee:  GSHEET [docs.google.com]

Rec. 27: ICANN org to check with Legal whether updating the operating procedures would also mean updating the ICANN Bylaws considering “the Nominating Committee shall adopt such operating procedures as it deems necessary, which shall be published on the website”

Rec. 27: Wordsmith "Should strongly consider" in “ During each NomCom appointment cycle, the NomCom should strongly consider nominating at least one director to the ICANN Board who has no or very limited prior involvement with ICANN and who would have no or very limited chances of being appointed to the Board through any of the SO/AC-appointed seats. The goal of this stipulation is that the NomCom’s goal appoints at least one director each year who brings an outside perspective to ICANN and who provides loyalty to ICANN as a whole with limited or no prior loyalty to one or more of ICANN’s SO/ACs.”

Question from Raoul:

“In the NomCom review assessment report that was published in 2018, it says that "traditionally the GAC has not appointed a person to the NomCom. A GAC working group is currently evaluating if, and how, the GAC can participate in the NomCom."