RE: [nc-budget] RE: Chuck's Detailed Job Description for DNSO Sec retariat

[Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>]

Chuck,

Your approach to my comments is on target, they clarify also
one complete misunderstunding -- the consultant cannot be managed 
by the NC consensus process -- sound like an ICANN joke,
you must have laugh heartilly !
Rather, I wanted to say that because the NC Chair will change
rather frequently, it has impact on consultant profile, and
consultant obligations should be defined carrefully (to avoid
the work with the direction choosen by consultant).

Under Objective #1
Ff it is only "it might happen", may I suggest therefore you suppress it ?

Thank you a lot for a smile this morning,
Elisabeth


> Elisabeth,
> 
> Thanks for your contributions to the job description.
> 
> paragraph.  I fully agree with you that the DNSO is not an executive body,
> is not supposed to operate in a hierarchical but rather in a bottoms up
> structure and  that the NC Chair does not have executive powers.  But I
> would also suggest that it would not be possible for the NC to hire a
> consultant or consultants to perform the secretariat functions and then
> manage the day-to-day responsibilities of the consultant(s) using a
> consensus process.  The consensus in terms of secretariat responsibilities
> needs to happen in the DNSO and the NC and then the NC needs to assign those
> responsibilities to the consultants via someone in the NC.  Whether that is
> the NC Chair or someone else is not the issue.  The consultants need to have
> someone to whom they report.  It would be nonfunctional for them to report
> to the whole NC or to the whole DNSO.  Therefore, it doesn't make sense to
> me to change the wording of the first paragraph unless it is simply a matter
> of assigning the day-to-day management responsibility of the consultant(s)
> to someone other than the Chair.  It is not as if the consultant(s) will be
> working on their own without direction.  It will be important that we hire
> people who are able to work independently but their work should be in
> response to direction given by the NC through the Chair or someone else in
> the NC.
> 
> With regard to the "many activities of the DNSO Secretariat which are
> related simultaneously to various components of the DNSO,"  the specific job
> responsibilities you list would come under both Objectives #1 and #3.  What
> I will do if the nc-budget group agrees is make some modifications to the
> current job description to make that clearer.  And my approach would be to
> reference the more detailed descriptions you give of past and current tasks
> and would attach those following the main job description, with the
> understanding that we will continue to improve the way those tasks are
> performed.
> 
> Under Objective #1, you asked what I meant by "Coordinate with ICANN to
> ensure ongoing support of the NC email list."  In one of our budget meetings
> we had talked about transitioning this function to ICANN, so I was assuming
> this might happen.  If it does, we would need to coordinate with ICANN in
> this regard.
> 
> Regarding your suggestion to include David Johnson's contribution in
> Objective #4, I would think that the job description would not be the best
> place for that.  Once we select someone to fill the Secretariat position, we
> should then give David's contribution to that person as a resource in
> fulfilling Objective #4.  Does that make sense or did I misunderstand your
> suggestion?
> 
> In addition to Elisabeth's response, I would appreciate hearing from others
> regarding the above before I make any changes.  Is my approach to
> Elisabeth's recommendations on target?
> 
> Chuck
> 
>  -----Original Message-----
> From: 	Elisabeth.Porteneuve@cetp.ipsl.fr
> [mailto:Elisabeth.Porteneuve@cetp.ipsl.fr] 
> Sent:	Friday, September 01, 2000 9:10 AM
> To:	nc-budget@dnso.org
> Subject:	[nc-budget] RE: Chuck's Detailed Job Description for DNSO
> Secretariat
> 
>  << File: chuck-elisa-detailsprofiles.doc >> Please find Chuck's Word file
> with my update added.
> I apologize it took a longer time than foreseen.
> 
> Elisabeth
>