Page History
...
| Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date |
|---|---|---|---|---|---|
| 50 | #60 |
| Rec. 15: ICANN org/NomCom Support Staff to specifically reach out to ALAC, ccNSO, to help on building a job description. | ICANN org/ NomCom Support Staff |
|
| 49 | #60 |
| Rec. 15: Jay Sudowski to take the lead on seeing whether GNSO could provide an outline | Jay Sudowski (Team Member) |
|
| 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 |
|
| 47 | #60 |
| 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. | NomCom Support Staff |
|
| 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 |
|
| 44 | #59 |
| Rec. 21 – 26 – update dates to 2021 | Jean-Baptiste |
|
| 43 | #59 |
| Rec. 20 – update dates to 2021 | Jean-Baptiste |
|
| 42 | #59 |
| Rec. 19 – create link for timeline for group to access offline | ICANN Staff |
|
| 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 |
|
| 39 | #59 |
| Rec. 18 – publish detailed timeline – change dates to 2021 | ICANN Staff |
|
| 38 | #59 |
| Rec. 16 – publish timeline and input for receiving bodies | ICANN Staff | ??? |
| 37 | #59 |
| Rec. 6 – update due dates to Q1 – 2021 | Jean-Baptiste |
|
| 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 |
|
| 35 | #59 |
| Rec. 12 – change dates to 2021
| Jean-Baptiste |
|
| 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 activities | NomComRIWG |
|
| 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/ACs | NomComRIWG |
|
| 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 Hoffmann | To be resolved during Implementation |
| 9 | #6 |
| HR for review of professional services hired to design recruiting materials | RT/Lars Hoffmann | To be resolved during Implementation |
...
