hi karen,

in addition to all the useful information milton already posted, i
must say mp3 records and transcriptions of the conference calls are
always made available. of course nobody has the time to listen to
that sort of talk more than 2 hours if one doesn't have to; however,
the transcriptions are quite easy to browse with the agenda items as
signposts. often, any of the constituency's representative on the
council will forward the minutes transcription to ncuc-list, and
possibly highlight any point that is of importance to the
constituency.

overall, and from my little experience, one can only learn to tame
the beast in its vicinity. issues always keep poping up, but at the
end, every body understands that you can only devote as much time as
you may have.

mawaki


--- karen banks <[log in to unmask]> wrote:

> hi milton
> 
> >Karen:
> >As Danny explained, the PDP _schedule_ is honored mainly in the
> breach.
> >
> >The "map" however does give you an idea of the process structure;
> e.g.,
> >what does it mean when the secretariat issues a "call for public
> >comment". what is the relationship between the GNSO Council, a
> Task
> >Force, etc.
> 
> obviously policy development is a very fluid process, and difficult
> 
> to descibe excepting as you say - by having the more structural 
> elements described (which i understand then the map does provide)
> and 
> with some (brief) annotation.. along the lines of what you go on to
> say
> 
> >If you want to know what is going on in any specific policy
> development
> >process, the only way is to get people to attend the
> teleconferences and
> >to report to the rest of us on what is really going on.
> 
> i'm interested in this now when thinking about the nomcom process..
> 
> how one would describe the nature of GSNO policy development to 
> potential candidates who aren't necessarily ICANN insiders.. but
> who 
> may bring useful skills, expertise and perspectives to the
> process..
> 
> karen
>