Versions Compared

Key

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

...

Item #Source of RequestDate of RequestAction Item RequestAction OwnerAnticipated Completion Date
59#63

 

Progress and Implementation Status Report #2: Tom/Support Staff to update report, incorporating the OEC noteTom Barrett/ NomComRIWG ICANN Staff

 

58#63

 

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

NomComRIWG/ ICANN Staff 

 

57#63

 

Standing Committee Charter: Accept all suggested edits on the Standing Committee CharterNomComRIWG 

 

56#61

 

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

NomComRIWG 

 

54#61

 

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

NomComRIWG

 

52#61

 

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.

NomComRIWG/ ICANN Staff

 

51#61

 

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

NomComRIWG/ ICANN Staff

 

48#60

 

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. 

Teresa Elias

 

46#59

 

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

ICANN Staff

 

45#59

 

Update all dates to 2021 throughout the document

Jean-Baptiste

 

41#59

 

Rec. 18: Share information on the timeline we were working on with the group to think offline about how to present the candidate communications schedule (Resolved - click here for details)

Jean-Baptiste

 

40#59

 

Rec. 18: NomCom Support Staff to provide candidates survey results data

ICANN Staff

 

36#59

 

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

ICANN Staff

 

34#59

 

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

ICANN Staff

 

33#57

 

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

NomComRIWG

 

32#57

 

Circulate charter with Legal

NomComRIWG

 

31#57

 

Send out letter to GNSO SGs/Cs chairs.

NomComRIWG

 

30#55

 

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

NomComRIWG

 

29#55

 

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

NomComRIWG

 

28#52

 

Rec. 24: Proceed with sanity check of Operating Procedures to see whether they have a section that includes all Standing Committee activitiesNomComRIWG

    

27#51

 

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”

ICANN org

 

26#51

 

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.”

Zahid

 

25#46

 

Rec. 13: Build a brand new strawman focussing on deadlines of certain things that have to happen and not worry about the process that people need to follow to get to that deadline. Tom/ICANN org

 

24#34

 

Rec.7 & 9: Make sure ICANN Legal also agrees to the language that is inserted into all these operational procedures.NomComRIWG

 

23#34

 

Rec.1: Wait before sending out job description to SOs/ACsNomComRIWG

 

22#34

 

Share language to rec. 27 and ask for input from Legal.ICANN org

 

10#6

 

Inquire about the contracting/procurement of recruitment consultants.

RT/Lars HoffmannTo be resolved during Implementation
9#6

 

HR for review of professional services hired to design recruiting materialsRT/Lars HoffmannTo be resolved during Implementation

...