RE: [gnso-wpm-dt] WPM: Draft Council Resolution and Timeline--REVISED

["Gomes, Chuck" <cgomes@xxxxxxxxxxxx>]

Thanks Ken.  Please see my responses below.
 
Chuck


________________________________

        From: owner-gnso-wpm-dt@xxxxxxxxx
[mailto:owner-gnso-wpm-dt@xxxxxxxxx] On Behalf Of Ken Bour
        Sent: Friday, April 09, 2010 10:19 AM
        To: gnso-wpm-dt@xxxxxxxxx
        Subject: [gnso-wpm-dt] WPM: Draft Council Resolution and
Timeline--REVISED
        
        

        WPM Team Members:

         

        The DRAFT Resolution, below, now incorporates the suggestions
made by Chuck and a few additional tweaks of my own after a few
additional rereads.   The timeline is the same as my first version.  
        [Gomes, Chuck] It looks fine to me. 

         

        Concerning format, how should we connect the Timeline to the
Resolution?    Can it be tacked to the bottom of the resolution as I am
showing with an embedded reference "(see below)"?  
        [Gomes, Chuck] What you did seems okay to me.  Another way to do
it is to provide a link in the motion but I think the timeline is brief
enough that that is not necessary. 

         

        Any thoughts about having our teleconference on Monday, as
scheduled, to finalize the resolution and timeline? 
        [Gomes, Chuck] Does anyone think we need a meeting to discuss
the motion or anything else?  If so, we should have it.  If we are able
to agree on the motion on the list and there are no other specific
reasons to have a meeting, then I suggest we cancel it.  Maybe we should
wait until 3 hours before the scheduled meeting time on Monday and make
a decision then; if no one has identified a need for the meeting, then
cancel it at that time.  That should also allow enough time for meeting
details to be sent out at that time (correct me if I am wrong on that
Glen).

         

        Thanks,

         

        Ken

        ===

         

        RESOLUTION:

         

        WHEREAS, the ICANN Policy Staff prepared and delivered to the
GNSO Council a 2008-2009 Work Team Attendance Study which confirmed that
volunteer participation has been suffering and languishing; 

         

        WHEREAS, the GNSO Council, considering the advice of Staff,
organized a Drafting Team at the Seoul ICANN meeting for the purpose of
developing a GNSO Work Prioritization model and procedure; 

         

        WHEREAS, the Work Prioritization Model Drafting Team (WPM-DT)
has completed its deliberations and developed a written procedure
recommended for inclusion in the GNSO Operating Procedures as Section 6
plus an accompanying ANNEX (link TBD); 

         

        WHEREAS, the WPM-DT has developed a timeline of activities (see
below) that it recommends be adopted in order that the first Work
Prioritization effort can be completed by the ICANN Brussels meeting; 

         

        NOW THEREFORE, BE IT:

         

        RESOLVED, that the GNSO Council accepts the deliverable of the
WPM-DT, thanks the team for its efforts, and approves the use of Section
6 and the ANNEX (link TBD) for conducting its first Work Prioritization
effort.  

         

        RESOLVED FURTHER, that the GNSO Council directs Staff to
commence a twenty-one (21) day public comment period on this amendment
to the GNSO Operating Procedures and reserves the right to modify the
procedures described in Section 6 and the ANNEX after the conclusion of
both the public comment period and the first Work Prioritization effort.


         

        RESOLVED FURTHER, that the GNSO Council supports the recommended
timeline (see below) for conducting the first Work Prioritization effort
and directs the GNSO Secretariat to make arrangements consistent with
its dates and activities.  

         

        RESOLVED FURTHER, that the GNSO Council take action on Section 6
and the ANNEX with regard to the GNSO Operating Procedures as soon as
possible after completion and analysis of the first Work Prioritization
effort. 

         

        TIMELINE FOR FIRST WORK PRIORITIZATION EFFORT

         

Dates

Activities (per proposed ANNEX to Section 6)

26-30 April

ANNEX Step 1:  Staff to prepare recommendations for Eligible and
Non-Eligible Projects and associated classifications

3-12 May

 

Chair asks for Council approval (via email list) to adopt or modify
Staff's recommendations (complete 8 days in advance of Council meeting)

20 May Council Meeting

Eligible Projects List approved by Council

21-31 May

ANNEX Step 2:   Individual Councilor ratings completed (10 calendar
days)

1-11 June

ANNEX Step 2.3:  Staff consolidates ratings and analyzes for
commonality; prepares for Step 3.  

19 June (or 20 June)

ANNEX Step 3:   Group Session (2 hours) to determine Value ratings

Brussels Council Meeting

ANNEX Step 4:   Approve final ratings/priorities and direct that results
be published at gnso.icann.org.