You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 84 Next »

OPEN ACTIONS/REQUESTS

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

 

Rec. 23: Consult with the wider ICANN community what additional metrics they might want to collect. (questionnaire, poll on wiki)NomComRIWG
62#67

 

Rec. 21: Schedule a discussion with HR to find out if they could suggest some assessment toolsICANN org
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

 

40#59

 

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

ICANN Staff

 

23#34

 

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

 

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

COMPLETED ACTIONS/REQUESTS

Item #

Source of Request

Date of RequestAction Item RequestAction OwnerAnticipated Completion DateCompleted ResponseCompletion Date
61#63

 

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

 

updated version shared with ICANN legal

60#63

 

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

 

email

59#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 

 

Sent internally to both recipients.

58#62

 

Rec. 11, 12: ICANN org to circulate the google doc once more.ICANN Staff

 

email

57#62

 

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

 

email & charter updated on plenary call #63

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 

 

Updated on Plenary call #64

55#61

 

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

ICANN Staff

 

added prior to plenary call #61

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

 

Reviewed on Plenary call #64

53#61

 

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

NomComRIWG/ ICANN Staff

 

questions finalized on plenary call #63

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

 

Input from Legal incorporated into progress report, not yet shared with OEC.

51#61

 

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

NomComRIWG/ ICANN Staff

 

NomComRIWG will be hosting an outreach session during the ICANN70 prep week.

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

 

NomCom support staff reached out to receiving bodies.

49#60

 

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

Jay Sudowski (Team Member)

 

NomCom support staff reached out to GNSO

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

 

NomCom support staff confirmed Goran Marby, CEO of ICANN.org or representatives would be answering NomComRIWG questions

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

 

Draft of the second progress and implementation report shared on plenary call #62.

45#59

 

Update all dates to 2021 throughout the document

Jean-Baptiste

 

Draft of the second progress and implementation report shared on plenary call #62.

44#59

 

Rec. 21 – 26 – update dates to 2021

Jean-Baptiste

 

Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

43#59

 

Rec. 20 – update dates to 2021

Jean-Baptiste

 

Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

42#59

 

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

ICANN Staff

 

Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

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.

Jean-Baptiste

 

Overdue. No input received

 

39#59

 

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

ICANN Staff

 

Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

38#59

 

Rec. 16 – publish timeline and input for receiving bodies

ICANN Staff


Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

 

37#59

 

Rec. 6 – update due dates to Q1 – 2021

Jean-Baptiste

 

Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

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

 

Draft of the second progress and implementation report shared on plenary call #62.

35#59

 

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
Jean-Baptiste

 

Updates were made on NomComRIWG Progress and Implementation Status Report #2 draft 

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

 

NomCom support staff looking into including these trainings into the current NomCom budget..

33#57

 

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

NomComRIWG

 

Shared with ICANN Legal, together with Bylaws suggested amendments.

32#57

 

Circulate charter with Legal

NomComRIWG

 

Shared with ICANN Legal, together with Bylaws suggested amendments.

31#57

 

Send out letter to GNSO SGs/Cs chairs.

NomComRIWG

 

email

30#55

 

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

NomComRIWG

 

Draft suggested reply: email.

29#55

 

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

NomComRIWG

 

First review completed on plenary call #56

28#52

 

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

    

Complete

 

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

 

Proposed rewrite submitted on plenary call #51

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

 

Proposed rewrite submitted on plenary call #51

26#47

 

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

ICANN org
email

 

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

 

New process maps shared on plenary call #60

24#34

 

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

 

final ICANN Legal review provided.

22#34

 

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

 

Sent to ICANN Legal Department on March 23, 2020.

21#33

 

Reach out to ICANN Org - Legal  Department to provide feedback on rec.7 Bylaws Update Principles.ICANN org
Principles sent to ICANN Legal.

 

20#33

 

Reach out to ICANN Org - HR Department to provide feedback on rec.1 job description.ICANN org
Response provided on call #35, only diversity section was updated.

 

19#24

 

Reach out to Finance on what happens if the budget request is accepted but NomComRIWG planning does not allow to spend the budget in the respective year.ICANN org
Question submitted to FInance.

 

18#24

 

Share session description for ICANN67 session request.ICANN org
Shared on call #25

 

17#24

 

Prepare EMS request for single community meeting at ICANN67ICANN org
Drafted and submitted.

 

16#24

 

Draft a budget request for trainings, and draft a budget request for travel support for the standing committee (3-4 people)ICANN orgJanuary 2020Submitted

 

15#24

 

NomComRIWG to follow-up with their constituency on questions submitted as part of the implementation outreach. NomComRIWG
Complete

 

14#911 July 2019Change all calls going forward to 90 minutesYG11 July 2019Invites updated & sent for 90 minute time slots following an email sent by Jean-Baptiste to inform the NomComRIWG list of the change

 

13#813 June 2019Re-work recommendations / task lists - flagged items on recommendations #6 - 17 (see recommendations doc for details)RTTBDRe-worked recommendations / task lists - flagged items on recommendations #6 - 17 (see recommendations doc for details)

 

12 #76 June 2019Take a look at other comments - see if they can be moved to task listRT13 June 2019RT reviewed other comments - moved various ones to task list

 

11#76 June 2019Refine scope to include job descriptionsRTTBDRT refined scope to include job descriptions

 

8#623 May 2019Dependencies - include the statement ‘timely feedback’ RTTBDStatement included

 

7#49 May 2019Identify which ICANN department Subject Matter Experts (SME’s) can identify cost on implementation and then produce a follow-up reportRT/ICANN StaffTBDSMEs have been identified and questions have been sent out

 

6#32 May 2019NomCom Recommendations Overview - post to the wikiLars Hoffmann/Yvette Guigneaux8 May 2019Posted to Meeting #4 wiki page to be accessible for the call.

 

5#32 May 2019What should the question be in helping us in the planning phrase as pertains to Recommendations? RT8 May 2019 RT discussion ensued creating the question above - Item #7 re: identifying SME's and following up with a report.

 

4#32 May 2019What Recommendations need community input?RT8 May 2019Community input obtained during the 2 May 2019 call and noted - latest version to be posted to the background/wiki meeting pages.

 

3#224 April 2019Announce Doodle Poll results for weekly callsLars Hoffmann26 April 2019Doodle poll results announced via email to the list:  weekly calls to alternate timeslots of Thursdays 1300 UTC and 1900 UTC 

 

2#2 24 April 2019Announce Chair Election resultsLars Hoffmann26 April 2019Voting results announced via email to the list:  Tom Barrett (Chair), Cheryl Langdon-Orr and Zahid Jamil-IG (Vice-Chairs) 

 

1#224 April 2019Complete strawman outreach documentLars Hoffmann26 April 2019Strawman/Outreach document filled in with proposals regarding NomComRIWG outreach to the community on the process of implementation - emailed to list

 

  • No labels